Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.



Page Contents

4true30pxPage Contentsnone

ProductFullName;ProductAbbrevName;ProductAbbrevLowercaseEnterprise Data Governance;EDG;edgINLINE

Search the EDG Customizations

Search the EDG manual configuration has been removed in favor of an automated process. Collections can be included in search upon creation or by selecting this option on the manage tab. Once added all properties are indexed for search as well as applicable facets. Customization of the results page can still be implemented with overrides explained below. The searchconfig.ttl graph will still remain in your workspace which holds the contents of what graphs are searchable, the properties and facets in the config file are now ignored.

Customizations to the number and selection of facets of Search the EDG using TBC-ME

To introduce a custom facet order, you will just need to write a custom SPIN template, and override saf:FacetsListJS to replace the template call to point to this new one.

Here is an example of adding a second rdf:type to the list, and rdfs:label. Changing the filters could, which defaults as 10 can be done here as well.



Overriding Search Results in Search the EDG using TBC-ME

There are several ways to override what is rendered for a search result in Search the EDG. We’ll cover two ways to accomplish such an override using SWP.

Override all search results.

1) Define a new project.
2) Create a new RDF/SWP file.
3) Import saf.ui.ttlx (teamwork/saf/saf.ui.ttlx)
4) Create a new sub-class of ui:ViewElements
5) Set ui:override to saf:SummaryRowItem

edg:SummaryRowItem by default will pass along the rendering responsibility to saf:EDGSummaryRowItem.

By comparison this is what a sample override could look like.

Override a specific class

Perhaps the default layout is sufficient but not enough specific data about a class is visible. To extend result summary for a specific class follow the steps below.

1) Define a new project.
2) Create a new RDF/SWP file (if necessary).
3) Import saf.ui.ttlx (teamwork/saf/saf.ui.ttlx)
4) Import schema definition for the target class.This example uses wgs84_pos.ttl (Topbraid/Common/wgs84_pos.ttl)
5) Find the target class definition (geo:SpatialConcept)
6) Add a new ui:InstanceView
7) The new instance view must have an outer tag that defines a ui:id and ui:priority. The id must be ‘saf-summary’ and the ui:priority must be lower than 10 (the default value is 10).

Default Summary

Overridden geo:SpatialThing Summary

Mixed results: Note only type of geo:SpatialThing is rendered with the new override.

Override both?
Yes, but only if the ui:ViewElement that is overriding swa:SummaryRowItem allows it by including a ui:resourceView that ‘saf-summary’. For example:

The attached file contains the customizations to the results used above.