1 / 11

METS

METS. What is METS ? A schema that provides a flexible mechanism for encoding descriptive, administrative, and structural metadata for a digital library object. The schema is written in xml format. METS Schema. A METS document consists of seven major sections: 1) METS Header

dysis
Download Presentation

METS

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. METS • What is METS ? • A schema that provides a flexible mechanism for encoding descriptive, administrative, and structural metadata for a digital library object. • The schema is written in xml format.

  2. METS Schema • A METS document consists of seven major sections: • 1) METS Header • The METS Header contains metadata describing the METS document itself, including such information as creator, editor, etc. • 2) Descriptive Metadata • The descriptive metadata section may point to descriptive metadata external to the METS document or contain internally embedded descriptive metadata, or both. • 3) Administrative Metadata • The administrative metadata section provides information regarding how the files were created and stored, intellectual property rights, metadata regarding the original source object from which the digital library object derives, and information regarding the provenance of the files comprising the digital library object.

  3. METS Schema • 4) File Section • The file section lists all files containing content which comprise the electronic versions of the digital object.  <file> elements may be grouped within <fileGrp> elements, to provide for subdividing the files by object version. • 5) Structural Map • The structural map is the heart of a METS document. It outlines a hierarchical structure for the digital library object, and links the elements of that structure to content files and metadata that pertain to each element.

  4. METS Schema • 6) Structural Links • The Structural Links section of METS allows METS creators to record the existence of hyperlinks between nodes in the hierarchy outlined in the Structural Map. • 7) Behavior • A behavior section can be used to associate executable behaviors with content in the METS object. Each behavior within a behavior section has an interface definition element that represents an abstract definition of the set of behaviors represented by a particular behavior section. Each behavior also has a mechanism element which identifies a module of executable code that implements and runs the behaviors defined abstractly by the interface definition.

  5. METS Header • The METS xml document that we have received did not have a METS Header. So I got an example from the web. • Example : • <metsHdr CREATEDATE="2003-07-04T15:00:00“ RECORDSTATUS="Complete"> • <agent ROLE="CREATOR" TYPE="INDIVIDUAL"> <name>Jerome McDonough</name> </agent> • <agent ROLE="ARCHIVIST" TYPE="INDIVIDUAL"> <name>Ann Butler</name> </agent> • </metsHdr>

  6. Descriptive Metadata • Example from the xml file : • <mets:dmdSec ID="DMD_OTHER"> • <mets:mdRef ID="D09002ee180b004da" MDTYPE="MODS" MIMETYPE="text/xml" LOCTYPE="URL" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="file:/mods.xml" /> • </mets:dmdSec>

  7. Administrative Metadata • Example from the xml file : • <mets:amdSec ID="AMD_OTHER"> • <mets:techMD ID="D09002ee180affcca-TEC"> • <mets:mdRef ID="M09002ee180affcca-tdiv" MDTYPE="PREMIS" MIMETYPE="text/xml" LOCTYPE="URL" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="file:/premis.xml" /> • </mets:techMD> • </mets:amdSec>

  8. File Section • One of many taken as example from the file: • <mets:fileSec> • - <mets:fileGrp ID="R0b002ee180affc6f"> • - <mets:file GROUPID="pdf-submitted" ID="D09002ee180b00410" MIMETYPE="application/pdf"> • <mets:FLocat LOCTYPE="URL" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="file:/pdf-submitted/S3880IS.pdf" /> • </mets:file> • </mets:fileGrp> • <mets:fileGrp ID="V0b002ee180b003e5" /> • </mets:fileSec>

  9. Structural Map • Example from file (trimmed(mainly from Graphic Support part): • - <mets:structMap> • - <mets:div ID="V0b002ee180b003e5-div" LABEL="BILLS-111s3880is"> • - <mets:div ID="R0b002ee180affc6f-div" LABEL="pdf-submitted"> • <mets:fptr FILEID="D09002ee180b00410" /> • </mets:div> • - <mets:div ID="R0b002ee180b0041d-div" LABEL="postscript"> • <mets:fptr FILEID="D09002ee180b00428" /> • </mets:div> • - <mets:div ID="R0b002ee180b00430-div" LABEL="text"> • <mets:fptr FILEID="D09002ee180b00440" /> • </mets:div> • - <mets:div ID="R0b002ee180b0044c-div" LABEL="xml-submitted"> • <mets:fptr FILEID="D09002ee180b00449" /> • - <mets:div ID="R0b002ee180b00452-div" LABEL="Graphic Support Documents"> • <mets:fptr FILEID="D09002ee180affca3" /> • <mets:fptr FILEID="D09002ee180b004cf" /> • </mets:div> • </mets:div> • </mets:div> • </mets:structMap>

  10. Structural Links • No example in file, example from the web: • <div ID="P1" TYPE="page" LABEL="Page 1"> • <fptr FILEID="HTMLF1"/> <div ID="IMG1" TYPE="image" LABEL="Image Hyperlink to Page 2"> • <fptr FILEID="JPGF1"/> • </div>

  11. Behavior • No example in file, example from the web: • <METS:behavior ID="DISS1.1" STRUCTID="S1.1" BTYPE="uva-bdef:stdImage" CREATED="2002-05-25T08:32:00" LABEL="UVA Std Image Disseminator" GROUPID="DISS1" ADMID="AUDREC1"> • <METS:interfaceDef LABEL="UVA Standard Image Behavior Definition" LOCTYPE="URN" xlink:href="uva-bdef:stdImage"/> • <METS:mechanism LABEL="A NEW AND IMPROVED Image Mechanism" LOCTYPE="URN" xlink:href="uva-bmech:BETTER-imageMech"/> • </METS:behavior>

More Related