Manage Page

 

Each collection’s Manage page (tab) is only available to its managers of the asset collection or an administrator.

 

Create a Cloned Version

 

Managers of a particular asset collection can use the Create a Cloned Version function to create one or more named clones of the asset collection. A new clone will have the same content and user permission settings as the original production instance. However, neither the change history, saved sparql queries nor the working copies will be cloned.

Cloning is often used to “branch off” a version of the asset collection, so that it can be referenced and imported separately from the current version. For example, one could start with an asset collection called “People.” Then, on reaching a milestone, one could create a clone and call it “People 1.0.” Now, any other asset collection that explicitly should only use terms from version 1.0 could change its includes to that version only, while the ongoing work towards version 2.0 will continue on the main “People” asset collection.

 

Clear

 

Managers can Clear a particular asset collection, which deletes all of its content, history, working copies, comments, and tasks. The empty collection itself and its user permission settings will be preserved. This feature can be used prior to file imports, to replace the whole content with an externally generated version.

 

Delete

 

Managers can delete a collection via its Delete link, which raises a message box to confirm the deletion. Clicking OK will delete the Data Assets production instance and any working copies and history data. This is not recoverable so use caution. 

 

Configure Notifications

 

For each asset collection, EDG can send notification messages to users in selected roles when certain kinds of changes happen to it. In order to receive email notifications the SMTP parameters in the Server Configuration must be configured. The Manage > Configure Notifications link provides a page listing all available Notification Events together with check-boxes to select the governance roles that will be notified:

 

 

The association of users with the governance roles for this collection is configured via governance areas. The user settings can be specified directly as individual users or indirectly as either user security roles or job titles. See Governance Model Overview for a discussion.

 

 

JIRA Project Key

 

Note that this item only appears if an administrator has setup the EDG Administration: JIRA Integration Parameters.

 

JIRA is Atlassian’s web application for team issue-tracking. EDG’s JIRA launch-in-context (LiC) feature allows users who are working in both EDG and JIRA to launch from editing particular EDG asset items into related JIRA searches and new items.

 

If the EDG JIRA feature has been administratively setup, then each collection manager can optionally set a JIRA project key string for the asset collection, where the JIRA-key identifies a specific project in the JIRA application. Setting the project key then enables JIRA LiC functions for collection editors. When editing any asset item, editors can use its gear menu to create or search for related JIRA issues.

 

Setting the project key also adds a JIRA link to the collection’s utility view header, which launches into JIRA to show the configured project’s open items.

 

Record Triple Counts only

 

Selecting this option disables retention of change history at the level of individual triples (for production graphs). It records summary counts of changed triples added or deleted. This significantly reduces storage and memory impacts at the cost of losing detailed change information and the ability to undo (revert) the changes. Working copy graphs and existing change histories are not affected by this setting.

 

 

Root Class (of Hierarchy)

 

For a given asset collection, Manage > Root Class of Hierarchy lets one reset which class will be the root of its Class Hierarchy whenever someone edits the asset collection (for example, if the asset collection specializes a standard class, perhaps its custom class’s ancestors should not show).

 

 

Local Search Options

 

When searching a vocabulary or asset model, there is an option, Return local results only, which excludes results that come from other models via include references. (A local search only delivers resources having their rdf:type triple in the base graph.)

 

By default, users can choose for themselves whether to enable or disable this local results option on any particular search. However, managers of a given vocabulary/asset can permanently set this option as either always local or always global for all users. If set by a manager, then users will still see the setting value on their search panes, but they will not be able to change it.

 

Enable Per-Asset Governance Roles

 

If activated then it is possible to define governance roles for each individual asset/resource by switching to Stewardship view on asset forms, where available. When enabled, editing a selected asset shows a section Governance Roles for this Asset (available on the stewardship view on the form panel), which lists available governance roles, each of which is multiply assignable to users and security roles. The roles set on an asset will pertain to any workflows directly spawned from the asset (whereas collection-spawned workflows use the collection-level role settings).

 

 

Archive Working Copies(Workflows) on Commit

 

If true, then working copies (or workflows) will be archived automatically when committed. (Note that the archive will always contain the full history, regardless of the Record Triple Counts only setting.) Archived working copies will not show the history of the working copy in the production asset collection. Archived working copies are still show in the UI workflows table with the metadata about the working copy/workflow.  A special “archive” folder is created where this data is stored. System Administrators can move or permanently delete the archived data so that it isn’t using up storage space when not needed.

 

Include this asset collection in the index for Search the EDG

Enabling this adds the collection content into the Lucene index used by the Search the EDG function. Search the EDG is the entire application based search function. Accessed from the home screen.

 

Enable Simple Search

 

For very large collections, enabling this reduces editor overloading by disabling both: (1) automatic table loading and (2) advanced filters (which can have a large impact). Text filtering, based on Lucene indexing, remains available.

 

Configure Features

This allows managers to selectively remove particular features (functions) from the user interface that will be applicable for the particular asset collections. Performance-intensive features are indicated. Note that all features always remain for administrators. Removal of these features from the UI might be desired to simplify the user experience or prevent accidental long running, high impact functions that are not needed.

Ontologies only – Prefer SHACL over OWL/RDFS

 

When enabled (which it is by default), this automatically applies SHACL constraints, aka Shapes, to classes and properties during editing. SHACL design patterns (such as sh:minCount) will be preferred over OWL axioms (such as owl:minCardinality) or RDFS axioms (such as rdfs:range). The global axioms section will be hidden on property forms. This automatically makes the ontologies compatible with EDG editors. Note that ontologies lacking such shapes can be converted via Transform page.  

This option only applies to the “old” Ontology editor and will be deleted after 6.3.