Child pages
  • Crosswalk View or Edit
Skip to end of metadata
Go to start of metadata

Page Contents


View or Edit

If a Crosswalk is associated with a governance area, then every user with a governance role in that same area will be able to view it (at least). For any other user to view or edit assets contained in a Crosswalk, a manager must grant them permissions via the Crosswalk's utilities > Users settings (see documentation).

Instead of making changes directly to an asset collection, you can start a Workflow

Note that different workflows that process changes to a Crosswalk can have their own permission-profile settings (for background, see Workflows: Rights Entailed by Permission Profiles).


Edits made directly in an asset collection are visible to all other collections that include it and to any workflows. In contrast, edits made as part of a workflow are only visible within the working copy managed by the workflow until and unless workflow changes are committed.

The view shown when an asset collection is selected, depends on a type of collection:

  • For taxonomies and ontologies, users will see a hierarchical tree of either concepts or classes
  • For most other asset collections, the primary view is a table, although configurable tree views are available as well
    • In each case, a specific asset type will be pre-selected for display
    • Users can narrow or, sometimes, broaden the selection by using the drop-down Asset Type field or the Asset Type Navigator dialog
  • Crosswalks and Content Tagsets have view and edit pages that have been specialized for these collections

The Crosswalk Editor

The crosswalk editor table 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 other tabular editors, viewers can filter-down the displayed assets by using (a) the Free Text search and/or (b) property-specific constraints, added from the Filters drop-down. Both filter-types apply to the left-side assets only.

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, click the corresponding right-side edit pencil icon  to open the asset-selection widget. To automatically generate potential matches, click the Generate Mappings button. This runs the crosswalks' Reports > Problems and Suggestions, which lists suggested asset mappings between the two collections (see linked item for details).


Crosswalk Operations: Reports, Export

Under Crosswalk Utilities, there are special considerations for reporting and exporting.

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 Reports > Problems and Suggestions report. The Problems and Suggestions report also auto suggests new mappings.

Exporting as a Spreadsheet

In addition to standard graph and search exports, users can also export Crosswalks in a common-separated spreadsheet format. See Export > Crosswalk as a Spreadsheet.

Creating a Crosswalk with EDG Tagger

If you have TopBraid EDG's optional Tagger module, you may find it easier to create crosswalks between hierarchical asset collections (for example, two taxonomies) using Tagger instead of the Crosswalk module.

To do this, configure a new tag set setting one of the hierarchical asset collections as the Concept asset collection as you normally would and then set the other as the Content Graph. Here, after someone has set the IPTC taxonomy to be the Concept asset collection and the Geography one to be the Content Graph, they have tagged "Africa" in the Geography Vocabulary with "Africa" from the IPTC one:

See the Tagger User Guide for further details on configuring Content and Tag Property graphs and Concept asset collection into a tag set.

  • No labels