About METS

Attrib

utio

n: h

ttp://w

ww

.flickr.com

/ph

oto

s/tom

bo

the

tom

ina

tor/3

04

23

32

01

6/size

s/l/

describe

locate

access

preserve

Attrib

utio

n: h

ttp://w

ww

.flickr.com

/ph

oto

s/sug

ree

/30

24

63

77

89

/sizes/l/

archival

tifflarge jpeg

small jpeg

TEI transcription ?audio ?video ?

PDF ?

complex

METSdocument

access

administration

preservation

location

structure

description

Brown UniversityDigital Collectionshttp://dl.lib.brown.edu/

National Library of WalesDigital Libraryhttp://ohio.llgc.org.uk/dig-lib.php

National Libraryof Portugal

Columbia UniversityDigital Scriptoriumhttp://scriptorium.columbia.edu/

Det KongeligeBibliotek, Denmarke-Manuscriptshttp://www.kb.dk/en/kb/nb/ha/index.html

Others ….

• Oxford University, England• New York University, USA• Harvard University, USA• EU projects ??• University of Gras, Austria• National Library of New Zealand• And others ….

mandatory

physical

logical

<structMap>structural map section

loves structMap

locations

groups

<fileSec>file section

embed (mdWrap)

reference (mdRef)

<dmdSec>descriptive metadata section

rights

source

provenance

technical

<amdSec>administrative metadata section

METS endorses

DescriptiveMARCMODS EADDC VRATEIHDR*DDI*FGDCLOMOTHER/OTHERMDTYPE

AdministrativeNISOIMGLC-AVISO 10115:2003 NAPPREMISPREMIS:OBJECTPREMIS:AGENTPREMIS:RIGHTSPREMIS:EVENTTextMDMETSRIGHTSOTHER/OTHERMDTYPE

METS in detail

• metsHdr ->secondary element• dmdSec ->secondary element• amdSec -> secondary element • fileSec ->primary element• structMap ->primary element• structLink ->secondary element• behaviourSec ->secondary element

<fileSec>

• Usefully groups content files by specifying location and links to pertinent metadata

• <fileGrp>: container element for files sharing something in common

• <file>: element representing a single, typically integral, content file

• Typically <file> elements are referenced from the <structMap>

METS example

<structMap>

• The only required element in METS

• Hierarchically arranges: – content files– parts of files– sequences and/or parallel groups of files into

a coherent whole.

<structMap>• <structMap>: container

element for single, structural arrangement of content

• <div>: a structural division of the content

• <fptr>: points to a single manifestation of the content represented by the parent <div>

• <mptr>: points to content represented by external mets file (to be covered later)

Divs are pages of pdf

Digital Repository Software• A group of services that follow the OAIS

reference model ensuring the long-term storage and preservation of digital objects in a repository.

Digital Repository Software

• Fedora is the repository we ingest to

• Supports METS version 1.1

• Current software supports only Dublin Core descriptive metadata.

• Integration of METS into the workflow has begun

METS + Digital Repository software

METS + Digital Repository software

• A variety of front-ends : some more basic to shield user from METS complexity

• METS File Validation: Use an existing METS toolkit for procedural

construction, validation, marshalling and unmarshalling of METS document

• Factors influencing encoding decisions– For ingest at another institution or into a repository

(DSPACE, Fedora, Greenstone)– For preservation

Software used

• MSSQLServer

• Apache Tomcat

• Java SDK

• Fedora digital repository

• .NET framework

Staff Resources for METS

• Areas of expertise for existing staff, e.g., SW engineers, XML programmers, descriptive cataloging, preservation knowledge

• Skill levels of staff involved in existent or new workflow processes

• What additional or re-training would be needed? For whom? By whom?

Thank you

Gill HamiltonSystems Librarian

g.hamilton@nls.uk

Tarik RahmanRepository Developer

t.rahman@nls.uk

National Library of ScotlandInformation Systems Development Team

Questions?