Metadata schemas

Metadata schemas help us define possible metadata groups with which an object to be preserved is self-defined in a file. These schemas will vary and they will have to be defined in the LIBSAFE implementation project, so that the LIBNOVA consultants may facilitate data configuration in the system.

A file following a metadata schema may be analyzed, and its data may be integrated, through metadata filters. It is recommended to seek the support of the LIBNOVA consultants for these tasks.

A metadata schema is comprised of a set of metadata defined by name, code, unicity and whether it is compulsory or not. Likewise, said metadata are associated to a metadata filter able to process them.

The main screen of Metadata schemas will show the available schemas. By default, the LIBSAFE installation includes the following metadata schemas:

• Empty metadata schema

• Simple metadata schema

• Object name metadata schema

• Marc21 EN metadata schema

• Simple metadata schema plus object name

• EAD3 EN metadata schema.

Normally, metadata schemas will come with associated filters capable of analyzing them, within a METS schema.

One of the essential aspects to keep in mind is the determination of which of their metadata:

• Are mandatory values

• Are unique values (that is, their value cannot be repeated from one object to another)

• Are versioning values

We must keep in mind that the catalog search system is based on data added through these schemas. For this reason, an adequate selection and configuration of the schemas is essential. Fortunately, existing cataloging standards facilitate the task of deciding which schemas to use, and the very same standardization facilitates configuration of the schemas as the base configuration of the tool.

The main screen of metadata schemas lists all metadata schemas available. Of each one, it shows name, user who created it, date and time of creation, its status (active / inactive) and access to metadata schema editing and detail.