Difference between revisions of "METS"
|Line 49:||Line 49:|
Revision as of 13:42, 13 October 2011
- The METS file will have a basic generic structure which will be present for all AIPs derived from different kinds of transfers.
- There may be one dmdSec for the AIP as a whole. Each original file may also have a dmdSec.
- The dmdSecs are numbered dmdSec_01, dmdSec_02 etc.
- The dmdSec contains Dublin Core metadata. If the user does not enter any DC metadata during transfer/ingest and no DC metadata was included in the transfer (eg as part of a DSpace export), there will be no dmdSec.
- The dmdSec may contain a reference to metadata in another file, such as a mets.xml file included in a DSpace export.
- There is one amdSec for each object.
- The amdSec is identified by the filename and UUID.
- Each amdSec will include one digiprovMD.
- An amdSec for an original object may also contain one or more rightsMDs. The rightsMD may contain a reference to metadata in another file, such as a mets.xml file included in a DSpace export.
- There is one fileSec listing all files.
- The fileSec is organized into the following fileGrps, only the first of which is required for all METS files:
- There is one structMap showing the physical layout of the files in the objects directory.
The dmdSec consists of simple Dublin Core, except for <isPartOf>, which is a qualification of <Relation>.
The descriptive metadata for DSpace collections are contained in the METS files that come with the DSpace export, so the Archivematica METS file will point to them using mdRef. In this example, dmdSec_01 points to the collection-level mets file; dmdSec_02 and dmdSec_03 point to the mets files for the objects:
The amdSec consists either of PREMIS metadata created by Archivematica or references to external content.