MoReq2, Model requirements for the management of electronic records; Appendix 9 to the Moreq2 specification: Metadata model

The MoReq2 metadata model has two, closely related, purposes:

• to define the metadata needed to allow exchange of records between ERMSs with no loss of MoReq2-related mandatory functionality, subject to the following exclusions below;
• to define such metadata sufficiently to allow the production development and use of a MoReq2 XML schema.

This metadata model includes the metadata necessary to define the user access rights model.
However, this aspect of the metadata model has the following limitations:

• User identities are not generally transportable between systems, and so cannot be meaningfully included here;
• It does not include a scheme to represent the different functions for which access can be granted or denied, as this is not transportable between systems (that is, it does not model the access control matrix in section 13.4);
• It does model the security categories and other requirements of the optional section 10.13.

Due to its focus on records, the metadata model does not include metadata for documents that are not considered records. Metadata for documents can easily be added to this model, preferably by using the records metadata as a basis and supplementing it with document-specific elements (in particular those related to version control and checkout/check/in).

The metadata model is described in terms of a minimum set of metadata  'elements'. These  'elements' are those that the ERMS must be able to export, import, and process. An  'elements', referred to as 'field' in the past, is the variable used to hold a metadata 'value'.