Licensing and Enablement
The availability of any asset collection is determined by what is (a) licensed and (b) configured under Server Administration. To install a license or to view the currently licensed features, see Setup > Product Registration. To configure which licensed collection types are currently enabled or disabled, see Setup - EDG Configuration Parameters.
For general licensing information and available asset collections and packages, see the TopQuadrant website.
Overview of Crosswalks
Crosswalks let you create connections between the assets in two different collections. This is especially useful for defining connections between two different standard vocabularies or between a standard one and a specialized local one. Applications can use saved crosswalk connection data to enhance the use of either vocabulary by taking advantage of the connected data and metadata for search, classification, and other operations.
When creating a new Crosswalk, you will be asked to identify From and To collection.
For each of the two collections connected by a crosswalk (From and To), you will be asked to select the class of assets to be mapped. By default, mappings will use crosswalk:closeMatch predicate. However, a different mapping predicate can be selected on the Manage tab.
Mappings between two asset collections can be auto-generated. This functionality is available in the Crosswalk Editor by clicking on the Generate Mappings button. Mapping functionality is part of the Problems and Suggestions algorithms. Thus, mappings will be generated by running Problems and Suggestions panel.
Crosswalk specific options on the Manage tab, let you plug in custom auto-mapping algorithms and set an option to automatically accept 100% matches.
Please see the Asset Collection Guide for all the general features of asset collections such as import/export, editing, user permissions, reports and settings. Specific crosswalk only information is contained within this page.
Selecting the Crosswalks link in the left-navigation pane of TopBraid EDG lists all of the Crosswalk collections currently available to the user and, it allows authorized users to create new ones.
Create New Crosswalk
The Crosswalks > Create New Crosswalk link opens a form with fields used to define the new Crosswalk. Note that you can also create a Crosswalk by using a Create link in the Governance Areas page or the plus button available in the application header bar.
The Create dialog box asks for the Crosswalk’s Label (name) and, optionally, a Description.
This creates a new Crosswalk with yourself as the manager.
For each of the new crosswalk’s two collections, select the class of mapped terms from the Entity Type drop-down list. For example, for a taxonomy users will choose Concept or one of its subclasses. For code lists, the class name often reflects the code list’s contents more directly, such as a “Market Identifier Code” class in a “Market Identifier Codes” code list.
References to Crosswalks
If an asset collection participates in a crosswalk, you will find references to crosswalk(s) in the editor under the Available Crosswalks panel. You will be able to navigate to the relevant crosswalks.This panel also lets you create a new crosswalk. When you create a new crosswalk using this panel, you do not need to specify “from” asset collection.
From your collection, click the dropdown located on the right upper corner of the page and drag Available Crosswalks somewhere in the page.
If you select an asset and then click on one of the available crosswalks, a crosswalk editor will open up with that asset pre-selected so you see what it has been mapped to in the crosswalk.
The Crosswalk Editor
The crosswalk panel has two main columns, one for each asset collection in the mapping. If the asset-type on the left side has a primary key, then it will also have a column.
Like the Search Panel in other collections, users can filter-down the displayed assets by using (a) the Free Text search, property-specific constraints added from the Filters drop-down, or the filters available in each column.
For each left-side asset, there are zero or more mapped right-side assets. The mapping can be many-to-many, so viewers can swap the left/right collections via the Toggle direction button found in the page header.
To manually add a new mapping from a right-side asset to a left-side one, use the mappings panel as seen below.
First highlight the row you wish to add a mapping in the table panel. This will cause the mapping panel to refresh for that particular row. You can then enter the matches along with comments for that row. Select each match from the dropdown and click the add match button. You will see all of the mappings entered below the add match button. If needed, you can delete a mapping from there.
To automatically generate potential matches, click the Generate Mappings button. This runs the crosswalks’ Problems and Suggestion panel, which lists suggested asset mappings between the two collections.
Export page – Export Crosswalk as a Spreadsheet
Including Crosswalks into Participating Asset Collections
You may want to include a crosswalk into an asset collection involved in a crosswalk, so that when you look at its resources you see matches from the crosswalk.
Note that you will only see matches on the forms and will be able to use them in search if the cross-walked entity type has a property shape for the mapping predicate. If you use a custom mapping predicate, make sure to select one that is defined for the “from” assets.
If you are using the standard mapping predicate, make sure to define it as a property for the “from” assets. EDG can automatically generate the necessary declarations if you do he following:
- Include a crosswalk in the “from” asset collection
- Navigate to an ontology in EDG that contains class and property definitions for the “from” asset collection
- Select your “from” class. Then select Modify>Derive property shapes from instances … .
- In the dialog that will appear, select the “from” asset collection as the place to get instances from.
For more details, see Working with Ontologies. If the same ontology is being used for the “to” graph, generate the inverse shape – to see matches when working with the “to” resources.
After the property has been defined, you will see the matches on the forms for the “from” resources. You will also be able to use the mapping predicate as a search results column. If the inverse was defined, you will also see matches on the forms for the “to” resources. Alternatively, to see matches for the “to” resources, use References panel.
Reporting Crosswalk Errors
Deletions or modifications to asset collections involved in a crosswalk can cause crosswalk relationship errors. Built-in EDG crosswalk constraints identify such occurrences for reporting and maintenance purposes. To use this feature, see the the Problems and Suggestions panel. The Problems and Suggestions panel also auto suggests new mappings.
Creating a Crosswalk with EDG Tagger
If you have TopBraid EDG’s optional Tagger module, you could create mappings using Tagger instead of the Crosswalk module. In this case, mappings will be store in asset collections called Content Tagsets. There are a couple of reasons why you may want to do this:
- When creating a Content Tagset, you can select multiple mapping (tagging) predicates and then decide which to use when creating each connection. In the Crosswalks, you can only use one mapping predicate at a time. To switch to another predicate, you could update the selection on the Manage tab. However, the crosswalk table and the mappings panel will only show connections built using the currently set mapping predicate.
- For building connections manually, if your “to” asset collection is a taxonomy, Tagger lets you select you select related resources by browsing taxonomical tree. You can also use full text and parametric search to find resources to connect to. In the Crosswalks, while you can bring up Taxonomy Concepts or Search panels, manual connections are always built by using the autocomplete.
If you decide to use this approach, configure a new Content Tagset by setting the “from” collection as the Content Graph and “to” collection as the Tagging Vocabulary. In the screenshot below, Geography Taxonomy has been selected as the Content Graph and IPTC Taxonomy as the Tagging Vocabulary. As you can see, “Africa” in the Geography Vocabulary has been connected (tagged) with “Africa” from the IPTC using “has exact match” predicate:
See the Tagger User Guide for further details.