Each collection’s Manage page (tab) is only available to the managers of the asset collection or TopBraid EDG Administrators. It lets you clone, clear and delete the entire asset collection as well as to select various options that control user interface or default behavior of EDG for a specific asset collection.
Create a Cloned Version
This function creates a clone of the asset collection. A new clone will have the same content and user permission settings as the original asset collection. However, neither the change history, saved SPARQL queries, saved searches, working copies, comments or tasks 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.
Note that EDG Basket also offers Clone operation.
Clear deletes all content in the asset collection, including its 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.
Note that Clear operation is not reversible. To recover cleared content, use backups.
Delete removes the asset collection. You will get a message to confirm the deletion. Clicking OK will delete the asset collection including any working copies and history data. This is not recoverable so use caution. To recover cleared content, use backups.
If this asset collection is included in another asset collection, you will not be able to delete it. You must first remove it from the including collection(s).
Main Class of Search Panel
This option is available only if the asset collection editor offers Search panel.
It impacts the Type Selector in the Search panel, determining what will be shown in its drop-down list and what will be the root of the browsable hierarchical navigator listing available asset types. Each asset collection has a default main class. This option lets you modify the default.
Local Search Options
This option is available only if the asset collection editor offers Search panel.
When using Search panel, there is an option, Return local results only, which excludes results that come from included asset collections. (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 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.
Root of Class Hierarchy Panel
This option lets you reset which class will be shown as the root of the Class Hierarchy panel.
The default root is Thing. However, you can use this option to limit the class tree to one of the subclasses of the owl:Thing class. You can also use this option to go “up the tree” by setting the root to rdfs:Resource class or any of its subclasses that are different from owl:Thing.
Root Shape of Asset Hierarchy Panel
When using Asset Hierarchy panel, users can select a shape of resources to be displayed as roots in this panel.
If you select a shape here, it will be used as default for the panel. Users can still switch to another shape.
If nothing is selected here, the panel will be empty until a user explicitly selects a root shape.
For each asset collection, EDG can send notification messages to users in selected roles when certain kinds of changes happen. In order to receive email notifications the SMTP parameters in the Server Configuration must be configured.
Notifications for each type of asset collection can be configured for the EDG server. You can overwrite EDG-wide defaults here.
Clicking on the Configure Notifications link will display 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 a collection is configured via either Governance Areas page or directly for a collection on the Users tab. See Governance Model Overview for more details.
Note that workflows can also produce notifications after each step. This is an alternative to the events-based notification set here. Workflow controlled notifications are specified directly in the workflow templates.
URI Construction Rules
This function lets you modify the default EDG-wide construction rules for the URIs of new resources created in the asset collection.
URI construction rules are first selected when a new asset collection is created. This function lets you change the selection at a later point. However, the change will not modify already created resources. It will only be in effect for the resources created after the change.
EDG offers the following options for the local name part of the URI construction:
- Label – it will create URIs from the labels of resources
- Counter – it will generate a numeric count when a new resource is created. You can set the counter start number.
- UUID – it will generate a unique identifier
Additionally, you can tell EDG to pre-pend class name or class acronym to the local name. Class acronym must be stored using edg:acronym property. All classes in the EDG models already have acronyms.
You can also use specify here whether users can override autogenerated URIs.
Enable Per Asset Governance Roles
This function is available only for asset collections based on EDG ontologies. It is not available for Ontologies, Taxonomies, Crosswalks, Reference Datasets, Content Tagsets or Corpora.
If activated, it will let users define governance roles for each individual asset e.g., Business Application or Glossary Term. You will see on asset forms, a Stewardship view listing available roles and will be able to assign them to users, security groups or organizations.
The roles set for an asset do not control edit permissions. Instead, they will be used to route the workflow actions to the relevant parties. This applies to workflows created for an individual asset whereas workflows created for an entire asset collection use the collection-level role settings.
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.
If this option is on, EDG will only record 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.
Archive Working Copies(Workflows) on Commit
If true, then working copies will be archived automatically when a workflow is committed. Note that the archive will always contain the full history, regardless of the Record Triple Counts only setting.
Changes made in the archived working copies will not show up in the Change History after commit. Archived workflows will continue to be listed in the Completed Workflows table on the Workflow tab.
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. This option can be selected on creation of the asset collection and modified here at a later point.
Turning this option on makes the asset collection read-only for all users. No edits can’t be performed and no workflows can be created.
This function allows managers to selectively remove particular features (functions) from the user interface of the asset collections. Performance-intensive features are indicated. 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.
Note that all function will remain available to EDG Administrators.
S3 bucket configuration is done per collection through the options below.The list of buckets here is determined from the buckets defined using the External System Integration Management in Server Administration.
A global setting in Server Administration can be defined for S3 Export as well, but not for S3 Attachments. The latter must always be selected per collection.
Enable GeoSPARQL and Related Features
Defines whether GeoSPARQL and related features are available for this collection. If enabled then all SPARQL queries issued by the editor use a spatial index for the production collection and its imports.
Building the spatial index may consume time and memory, yet geography-related queries will be significantly faster.
Crosswalk-only Manage Functions
Custom Match Predicate
This option lets you change the default match predicate away from crosswalk:closeMatch. If this is changed, any previously matched entries tied to the old match predicate will no longer appear in the UI.
Problems and Suggestions Generator
Selects the generator to be used for the Problems and Suggestions report. By default, only one generator is available, but customers can plugin their own algorithms for mapping crosswalks.
Ontology-only Manage Functions
Also create global OWL Properties
If activated, EDG will produce an owl:DatatypeProperty or owl:ObjectProperty type statement for a property when a new SHACL property shape is created.