Mest
Upcoming SlideShare
Loading in...5
×
 

Mest

on

  • 192 views

 

Statistics

Views

Total Views
192
Views on SlideShare
192
Embed Views
0

Actions

Likes
0
Downloads
1
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Mest Mest Presentation Transcript

  • Manu Kumar K MIInd MLIScDOS in LISManasagangotri, Mysore.
  • ContentIntroductionHistoryCharacteristics of METS.Sections of a METS documentMETS headerDescriptive MetadataAdministrative MetadataFile SectionStructural MapStructural LinksBehavioralConclusion
  • The Metadata Encoding and Transmission Standard (METS) is adata encoding and transmission specification, expressed in XML, thatprovides the means to convey the metadata necessary for both themanagement of digital objects within a repository and the exchangeof such objects between repositories. This common object format wasdesigned to allow the sharing of efforts to develop informationmanagement tools/services and to facilitate the interoperableexchange of digital materials among institutions. The METS XMLschema was created in 2001 under the sponsorship of the DigitalLibrary Federation (DLF), is supported by the Library of Congress as itsmaintenance agency, and is governed by the METS Editorial Board.
  • HistoryAs early as 1996 the University of California, Berkeley beganworking toward the development of a system that combined encoding foran outline of a digital objects structure with metadata for that object. In1998 this work was expanded upon by the Making of America II project(MoAII). An important objective of this project was the creation of astandard for digital objects that would include defined metadata for thedescriptive, administrative, and structural aspects of a digital object. Atype of structural and metadata encoding system using an XML DocumentType Definition (DTD) was the result of these efforts. In 2001, a newversion of the DTD was developed that used namespaces separate fromthe system rather than the vocabulary of the previous DTD. This revisionwas the foundation for the current METS schema, officially named in Aprilof that year.
  • Characteristics of METS.An open standardNon-proprietaryDeveloped by the library communityRelatively simpleExtensibleModular
  • Sections of a METS document• METS header• Descriptive Metadata• Administrative Metadata• File Section• Structural Map• Structural Links• Behavioral
  • Sections of a METS documentMETS header metsHdr: Contains metadatadescribing the METS document itself, such as itscreator, editor, etc.Ex:- <metsHdr CREATEDATE="2006-05-09T15:00:00“ LASTMODDATE=”2006-05-09T21:00:00><mets:agent ROLE="CREATOR" TYPE="INDIVIDUAL"><mets:name>Rick Beaubien</mets:name></mets:agent><mets:altRecordID TYPE=”LCCN”>20022838</mets:altRecordID></metsHdr>
  • Descriptive Metadata dmdSec: May containinternally embedded metadata or point to metadataexternal to the METS document. Multiple instances ofboth internal and external descriptive metadata may beincluded.Ex: <mets:mets><mets:dmdSec ID="DMD1"><mets:mdRef MIMETYPE="application/MODS"MDTYPE="MODS"/><mets:binData>[base 64 encoded data goeshere]</mets:binData></mets:dmdSec></mets:mets>
  • Administrative Metadata amdSec: Providesinformation regarding how files were created andstored, intellectual property rights, metadataregarding the original source object from which thedigital library object derives, and informationregarding the provenance of files comprising thedigital library object (such as master/derivativerelationships, migrations, and transformations). Aswith descriptive metadata, administrative metadatamay be internally encoded or external to the METSdocument.
  • File Section fileSec: Lists all files containing contentwhich comprise the electronic versions of the digitalobject. file elements may be groupedwithin fileGrp elements to subdivide files by object version.Although this section is not required, it is typically includedin most METS documents as it adds a level of functionalityto the structure of the document.<mets:fileSec><mets:fileGrp USE="archive image"></mets:fileGrp><mets:fileGrp USE="reference image"></mets:fileGrp><mets:fileGrp USE="thumbnail image"></mets:fileGrp></mets:fileSec>
  • Structural Map structMap: Outlines a hierarchicalstructure for the digital library object, and links theelements of that structure to associated content filesand metadata. The Structural Map is the only sectionrequired for all METS documents.
  • Structural Links structLink: Allows METS creators torecord the existence of hyperlinks between nodes inthe Structural Map. This is of particular value in usingMETS to archive Websites.Ex:- <mets:structLink><mets:smLink xlink:from="IMG1" xlink:to="P2" xlink:title="Hyperlinkfrom JPEG Image onPage 1 to Page 2" xlink:show="new" xlink:actuate="onRequest"/></structLink>
  • Behavioral behaviorSec: Used to associate executablebehaviors with content in the METS object. Each behaviorhas a mechanism element identifying a module ofexecutable code that implements behaviors definedabstractly by its interface definition.Ex:- <mets:behaviorSec><mets:behavior ID="disp1" STRUCTID="top" BTYPE="display" LABEL="Display Behavior"><mets:interfaceDef LABEL="EAD Display Definition" LOCTYPE="URL"xlink:href=”http://texts.cdlib.org/dynaxml/profiles/display/oacDisplayDef.txt”/>
  • ConclusionThe METS schema provides a flexible mechanism forencoding descriptive, administrative, and structural metadatafor a digital library object, and for expressing the complex linksbetween these various forms of metadata.� It can thereforeprovide a useful standard for the exchange of digital libraryobjects between repositories. In addition, METS provides theability to associate a digital object with behaviors or services.The above discussion highlights the major features of theschema, but a thorough examination of the schema and itsincluded documentation is necessary to understand the fullrange of its capabilities.