Metadata Schema Operations

The metadata schemas describe the metadata set associated with individual entities. The schemas themselves cannot be edited within the AROMA system; they can only be selected for use. The AROMA software component extends the functionality of a Dataverse-based repository, allowing metadata schemas to be assigned to not only entire data packages but also to each individual entity displayed within them. These schemas are derived from public schemas in the schema registry connected to Dataverse. Making a schema public is the responsibility of the schema registry's super admin.

To select a schema, you need to click on the + icon located in the Metadata Schemas panel. This will bring up a navigation panel that contains publicly accessible schemas from the schema registry, organized hierarchically.

Navigating to the specific schema, you can add it to the list of metadata schemas for the edited entity using the ADD button.

If there were no metadata schemas assigned to the entities before, then in the metadata editor, you will find a consolidated list of general file descriptor metadata. When adding a new metadata schema, on the Metadata Editor panel, a new item (the name of the new metadata schema) appears, where metadata specific to that schema is grouped together. In this case, general RO-Crate specific metadata (@id, @type, Name) are placed in the About element list, and Dataverse-specific ones (Size, Type, Description, Hash, ARP PID) are placed in the Other element list.

From the list of metadata schemas, previously added elements can be removed using the trash bin icon next to the list item. The Root dataset has a mandatory metadata schema required by Dataverse, and the user interface does not allow this to be removed. When deleting metadata schemas, any filled-in metadata associated with the schema will also be removed.