Skip to end of metadata
Go to start of metadata

Page Contents

Overview of Crosswalks

Crosswalks let you create connections between the terms in two different vocabularies. 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.

Crosswalks Home

Selecting the Crosswalks link in the left-navigation pane of TopBraid EDG (Home) lists all of the Crosswalk collections currently accessible to the user and, it allows authorized users to create new ones.

Prerequisites: Licensing and Enablement

The availability of any collection type (including Crosswalks and customer-defined types) 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 EDG Configuration Parameters > Configure Asset Collection Types. For general licensing information, see the TopQuadrant website, which describes the TopBraid products and the  data governance packages that determine the available collection types.

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. 

Nobody will have a link for creating any asset collection until an administrator configures EDG's persistence technology as documented in Server Administration: Teamwork Platform Parameters: Application data storage . Additionally, each user will not have a create link unless the user or their role has a Create permission for the EDG Repositories project as documented in  EDG Rights Management .

Required and Permitted Includes

Collections often have natural relationships to other collections (e.g., each reference dataset's main entity class comes from an included ontology). Any collection using outside resources must first include the collections that contain them. Some inclusions might be required while others might merely be permitted. For example, taxonomies always include the SKOS ontology, and they may include other taxonomies. As mentioned, each reference dataset must include at least one ontology to define the dataset's entities. Glossaries always include the pre-defined EDG ontology that describes business glossary terms. Catalogs of data assets always include the pre-defined EDG ontology describing data assets and are expected to include definitions of relevant physical datatypes. These requirements can be further configured.

When creating a collection, any required reference to another type of collection will either be handled automatically or be presented for selection. If any required inclusion is omitted at its creation, then the resulting collection will show red warnings about the missing relationship(s). After creation, included collections can be changed using utilities view: Settings > Includes. When changing collection's includes, selection options are restricted to required and permitted types.

The Create dialog box asks for the Crosswalk's Label (name) and, optionally, a Description.

Create New Crosswalk

This creates a new Crosswalk with yourself as the manager.

For each of the new crosswalk's two models (vocabulary or asset), select the class of mapped terms from the Entity Type drop-down list. For example, a taxonomy typically will choose Concept because the terms in a taxonomy are each stored with an instance of Concept. 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.

Listing of Crosswalks by Manage, Edit, or View

This home view lists all Crosswalks that you can access in some way. Which ones you can see and what you can do with them depend on each Crosswalk's permissions settings for your user identity or security role. The listing groups the Crosswalks according to your assigned permissions as either a manager, an editor, or a viewer:

  • Crosswalks that you manage
  • Crosswalks that you can edit
  • Crosswalks that you can view

You will only see relevant categories. For example, if you do not have manager permissions to any Crosswalks, you will only see "Crosswalks that you can edit" and "Crosswalks that you can view" groupings.

This page provides a focused, permission level oriented view on Crosswalks. To see a view of all asset collections, irrespective of their type, that you have a governance role for click on your User Name in the upper right corner of the page.

If a Crosswalk is either missing or it is lacking expected features in your views, you or your security role(s) may lack proper permissions for the Crosswalk.  A manager of the Crosswalk can give you the needed permissions via its utilities' Users settings. For background information, see Asset Collection Permissions: Viewer, Editor, and Manager.

Another possible cause of a missing feature is that it requires administrative setup to become active. See EDG Administration for relevant within-application settings and/or see other EDG Administrator Guide documents for relevant external installation and integration setup

For each collection on the home page some brief metadata is available including information about workflows available to the user. In the image below the user has an action on the workflow that they have permission for. An action means they are in a role that is allowed to transition the workflow to the next state, such as "committed". If the user does not have an action, but they have permission for the workflow they will be presented a read-only view when accessing that workflow. 

  • No labels