1 / 13

METS Metadata Encoding and Transmission Standard

METS Metadata Encoding and Transmission Standard. Metadata Working Group Forum April 19, 2002. METS. MOA II project Concerned with the metadata necessary for the management and exchange of digital objects An XML framework or container for metadata

trilby
Download Presentation

METS Metadata Encoding and Transmission Standard

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. METSMetadata Encoding and Transmission Standard Metadata Working Group Forum April 19, 2002

  2. METS • MOA II project • Concerned with the metadata necessary for the management and exchange of digital objects • An XML framework or container for metadata • Applicable to OAIS model, and CUL digital library projects

  3. A METS Object <mets> <metsHdr> File Header <dmdSec> Descriptive <amdSec> Administrative <fileSec> File Inventory <structMap> Structure Map <behaviorSec> Behaviors </mets>

  4. metsHdr <metsHdr> <agent> <name> <note> </agent> </metsHdr> Attributes: ID, CREATEDATE, LASTMODDATE, RECORDSTATUS

  5. dmdSec <dmdSec ID=“1234”> <mdRef /> [and/or] <mdWrap> <binData> [or] <xmlData> </mdWrap> <dmdSec> [examples best viewed with IE5 browser or higher]example #1 example #2

  6. amdSec <amdSec> <techMD> Technical <rightsMD> IP Rights <sourceMD> Original source <digiprovMD> Digital provenance </amdSec> example #3

  7. A METS Object <mets> <metsHdr> File Header <dmdSec> Descriptive <amdSec> Administrative <fileSec> File Inventory <structMap> Structure Map <behaviorSec> Behaviors </mets>

  8. fileSec <fileSec> <fileGrp> <file> <FContent> [and/or] <Flocat /> </file> </fileGrp> <fileSec> example #4

  9. structMap <structMap> <div> <div> <div> <mptr> [external] <fptr> [internal] </div> </div> </div> </structMap> example #5

  10. structMap • Heart of the METS object • Only required element in METS schema • Hierarchy can be represented within a single METS object (fptr) or through a series of related METS objects (mptr) • fptr has child elements for sophisticated linking between structMap and fileSec

  11. METS • Dependence on extension schema • The need for digital standards development • Permissiveness • The need for profiles • Complexity • The need for tools http://www.loc.gov/standards/mets

  12. Advantages • A common metadata format • Flexible, modular, extensible, expressive • Open

  13. Uncertainties • Where should certain data live in METS? • dmdSec vs. amdSec • amdSec vs. fileSec • For text: “page” vs. textual unit conundrum • Relationship with TEI? • Need for timestamps on xxSec and structMap elements

More Related