Metadata Templates
March 15, 2017
Metadata Templates Working Group
Chapel Hill, NC
Rick Skarbez
iRODS Consortium
Metadata template use cases
Metadata templates enable users and curators to:
Metadata template JSON Schema
Available in white paper
A Metadata Template contains the following properties:
Metadata Template type
An enum indicating what type of Metadata Template this is
Currently, only FORM_BASED Metadata Templates are supported
We have discussed adding, for example, support for Templates derived from schema.org schema (SCHEMA_REF)
Metadata Template source
An enum indicating where the data to populate the Metadata Template will come from
Currently, the only supported source is USER
We have discussed adding, for example, the ability to populate a Metadata Template with output from an iRODS rule (RULE) or a combination of rule output and user input (MIXED)
Metadata Template destination
An enum indicating how the metadata will actually be stored on disk
Currently, the only supported destination is IRODS, indicating that the metadata will be stored as AVU triples in the iRODS catalog
We have discussed adding, for example, the ability to store metadata in an external Postgres database (POSTGRES), as is done in CyVerse
Metadata element JSON Schema
Available in white paper
A Metadata Template contains the following properties:
Metadata Element validation style
An enum indicating how/if a metadata element will be validated
Supported validation styles are the following:
Metadata Element validation style
An enum indicating how/if a metadata element will be validated
Supported validation styles are the following:
Supported Metadata Element types
Components of the Metadata Template architecture
Parser
Generates MetadataTemplate POJOs from JSON and vice versa
Validator
Validates Metadata Templates and Elements
Resolver
Handles find/list/CRUD operations on template files
Exporter
Saves populated Metadata Templates to permanent metadata store
Metadata Templates + FormBot in use