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.

Licensing

The availability of different collection types, including Crosswalks and customer-defined types, is determined by what you have licensed and configured. The TopQuadrant website describes the TopBraid products and the  data governance packages that determine which collection types are available.

Crosswalks Home

Selecting the Crosswalks link in the left-navigation pane of TopBraid EVN (Home) lists all of the Crosswalk collections currently accessible 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. 

Nobody will have a link for creating any asset collection until an administrator configures EVN's persistence technology as documented in EVN Administration: Configuring the application data storage . Additionally, each user will not have a create link unless the user or their role has a Create permission for the EVN Repositories project as documented in  EVN Permission Group Management: Configure Permissions .

Note: Required and Permitted Includes

Collections often have natural relationships to other collections, e.g., a Reference Dataset references an Ontology class as its main entity. In order to do this, collection with resources to be referenced needs to be included. Some inclusions might be required while others might merely be permitted. For example, Taxonomies always include SKOS ontology and can include other taxonomies. A Reference Dataset is always required to include at least one Ontology as it is needed to define the entities in the dataset. Glossaries with always include pre-defined EDG ontology that describes business glossary terms. Catalogs of Data Assets will always include 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.

Creation Form

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 conner 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 Crosswalk Utilities > User Roles 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 EVN Administration for relevant within-application settings and/or see other EVN Administrator Guide documents for relevant external installation and integration setup.

A Crosswalk's Operations and Viewer/Editor Views

Each Crosswalk has two main views:

  1. utilities, from the name link, provides groups of collection-level functions, and
  2. viewer/editor (depending on user permissions), from the View/Edit link, provides direct access to the Crosswalk content items (e.g., instances, properties, classes, etc.).

These views are documented in the corresponding Crosswalk Operations and Crosswalk View or Edit pages.

  • No labels