Customizing Metadata Tutorial: Metadata Application Profile

Summary: Describes the metadata properties provided in Hyrax upon default installation, and the core properties required for Hyrax to function correctly

The following Metadata Application Profile lists properties provided by Hyrax by default upon installation. Core Metadata are properties required for Hyrax to function correctly. Basic Metadata properties listed as Required are configured for validation. Basic Metadata properties can be modified within Hyrax but Core Metadata properties cannot be modified. This profile also applies to Hyrax v2.0. More details and links to code available below.

A list of fields is provided below for both Basic and Core metadata. An expanded version of this documentation is linked providing more information per field than can be readily shown on this page. Most of the same metadata fields are offered by default for describing Collections, but there are some differences. For more information on how the metadata specification differs between Collections and Works, see the Machine-readable Metadata Modeling (M3) Specification Working Group’s Hyrax Profile.

Namespaces

Distinction: The MUST out of the box is a slightly different set of things from what is in Core.

Reference: Local controlled vocabularies and forms pulled in here: https://github.com/samvera/hyrax/blob/main/lib/generators/hyrax/config_generator.rb

Basic Metadata

Basic metadata properties are defined in app/models/concerns/hyrax/basic_metadata.rb

Expanded documentation for Hyrax Basic Metadata

New fields starting with Hyrax 3 are indicated with italics. Fields are listed in the order they appear in the Hyrax Work form by default.

Asterisks(*) indicate fields that are included as defined metadata properties but are not shown in the Hyrax Work form by default.

Core Metadata

Core metadata properties (that should never be removed) are defined in app/models/concerns/hyrax/core_metadata.rb

Expanded documentation for Hyrax Core Metadata