Skip to end of metadata
Go to start of metadata

Page Contents

Overview of Content Tag Sets

Content Tag Sets are used for tagging content using vocabularies managed in EDG. Users can tag (assign metadata to) content through a visual user interface that displays the context for both the content and the vocabulary. They can also run Tagger's auto-classification capability to automatically assign relevant tags to content and review the results.

Licensing

The availability of different collection types, including Content Tag Sets 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.

Content Tag Sets Home

Selecting the Content Tag Sets link in the left-navigation pane of TopBraid EVN (Home) lists all of the Content Tag Set collections currently accessible to the user and, it allows authorized users to create new ones.

Create New Content Tag Set

The Content Tag Sets > Create New Content Tag Set link opens a form with fields used to define the new Content Tag Set. Note that you can also create a Content Tag Set 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

Whenever a new Content Tag Set is created, the system will by default add an owl:import to a SHACL graph called taggershapes. For implementations done before version 5.2, the only way to add this would be a manual outside procedure. With this import, users can go to the Constraint Violations report and will get a screen as shown in the attachments, with an Apply button to quickly delete the triples. Basically, whenever either the subject or the object of a tag triple is deleted, an entry will be shown.

An EVN administrator sets up the content and property graph choices, as described in Configuring content and property graphs, which describes not only the setup but the information that must be in these graphs for Tagger to display them properly.

After completing this, to create a new tag set, select Content Tag Sets from the main EVN left-navigation menu and then select Create New Content Tag Set, which invokes a wizard for configuring your new tag set. The first step defines the following:

  • Label The name that will appear for this tag set in the list of tag sets on the EVN main screen.

  • Description A description of the tag set to help people understand what it's for.

  • Content Graph The list of content resources to tag. A single content graph might list a set of newspaper articles or a collection of journal articles.

  • Tag Property Graph The list of relationships choices available when tagging content resources with concept terms. For example, when assigning the concept term Business to a news story, a given tag property graph might offer tag property choices such as mainSubject and secondarySubject. Tag properties must be defined with several rules detailed in Tagger User Guide: Configuring content and property graphs.

  • Tagging Vocabulary The concepts used to tag the contents. This can be either a SKOS taxonomy, or an RDFS/OWL ontology, with skos:broader or subclass relationships forming a concept hierarchy. A news story vocabulary would include terms such as Business, Sports, and Weather, while an academic journal vocabulary would typically have technical terms more specific to a particular academic field such as medicine or mathematics.

Content GraphTag Property Graph and Tagging Vocabulary are all drop-down fields that offer you a specific choice to select from. Tagging Vocabulary lists all vocabularies displayed on the system, while the selection listed on the other two drop-downs are configured by your EVN administrator as described in the section Configuring content and property graphs.

Note that there are four graphs defined in a Tag Set:

  • Content Graph: The resources to be tagged.
  • Tag Property Graph: A graph of properties used for tagging. The set of choices includes both administratively enabled graphs and viewable ontologies.
  • Tagging Vocabulary: The controlled vocabulary used for tagging.
  • Content Tag Set graph: This graph, containing all of the {<content> <property> <vocabulary-term>} triples. This is the sole data created in a Content Tag Set, as the three other graphs (content, properties and concepts) can be any other EVN project or arbitrary graph as long as they are selected as such by your EVN administrator.

After you set these values and click the Next button, the second configuration screen lets you customize the Tagger interface for this tag set with the following fields:

  • Default Tag Property If most tagging will be done with the same property, selecting it here can make the tagging go more quickly.

  • Tag Properties This lists all properties in the Tag Property Graph, as selected on the previous screen. Only properties with an rdfs:range value of skos:Concept will appear in this list. Only checked properties and the default tag property will appear as choices to users tagging with this Content Tag Set.

  • Root Content Type The class/subclass structure of an RDFS or OWL model available in the content graph will appear here. One class can be chosen as the root class that will appear along with its subclasses as the Content Types hierarchy of EVN Tagger. Expand the tree to find the content type that you want to serve as the root and select it.

Once you have finished configuring your new Content Tag Set, it will appear as a link on the Content Tag Sets tab.

Listing of Content Tag Sets by Manage, Edit, or View

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

  • Content Tag Sets that you manage
  • Content Tag Sets that you can edit
  • Content Tag Sets that you can view

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

This page provides a focused, permission level oriented view on Content Tag Sets. 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 Content Tag Set is either missing or it is lacking expected features in your views, you or your security role(s) may lack proper permissions for the Content Tag Set. A manager of the Content Tag Set can give you the needed permissions via its Content Tag Set 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 Content Tag Set's Operations and Viewer/Editor Views

Each Content Tag Set 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 Content Tag Set content items (e.g., instances, properties, classes, etc.).

These views are documented in the corresponding Content Tag Set Operations and Content Tag Set View or Edit pages.

  • No labels