Differences and distinctions: metadata types and their uses Stephen Winch Information Architecture Officer, SLIC

Introduction Why choose a particular format? XML container formats Some common metadata formats: MARC21 MARC21 Dublin Core (DC) Dublin Core (DC) IEEE LOM IEEE LOM METS METS

Why choose any format? Interoperability Share data Share data Cross searching Cross searching Migration Migration Skills are transferable Shared maintenance costs Provides a ready to use structure

Which format to choose? Formats are designed for particular types of material Bibliographic/digital/music/photographs Bibliographic/digital/music/photographs Formats are used for particular purposes Access Access Preservation Preservation Version control Version control

Container formats Metadata formats are containers that allow us to exchange data between systems A system may be able to produce more than one type of metadata (problematic) A Metadata format can itself be held in another container e.g XML e.g XML

XML Not a metadata format itself, but a container language that can be used to express metadata formats Tree structure Like Windows explorer Like Windows explorer Allows people to create their own metadata formats XML Schemas

Marc21 Standard format for libraries bibliographic metadata Maintained by the Library of Congress Machine Readable Cataloguing Detailed format Requires skilled cataloguers

Fields Indicators Subfields OCLC

Controlled input Marc guide What goes in what field and subfield What goes in what field and subfieldAACR2 How text entered should be formatted How text entered should be formatted Range of classification and subject schemes LCSH LCSH Mesh Mesh Dewey Dewey

Name authorities Provide a way of making sure names are entered uniformly Contain alternate forms of name See & see also references See & see also references

100 – Name main entry 400 – See from 670 – source of data 678 – biographical data

MARC21 Mature record format Large number fields Input is controlled AACR2 AACR2 Name authorities Name authorities Semantic interoperability Semantic interoperability Pervasive in the library community Requires experienced cataloguers

Dublin Core Designed for describing internet resources Part of the e-gif Describes the “core” properties of resources DC element set has 15 elements DC element refinements add to this

DC elements TitleCreatorSubjectDescriptionPublisherContributorDateTypeFormatIdentifierSourceLanguageRelationCoverageRights

DC element refinements Refines a DC core element to make it more specific: Abstract – refinement of Description Abstract – refinement of Description Alternative – refinement of title Alternative – refinement of title Date created Date created Date accepted Date accepted Date copyrighted Date copyrighted Date submitted – refinement of date Date submitted – refinement of date

DC encodings DC can be placed in the head of an HTML document

DC encodings DC can be encoded as an xml rdf file:

Dublin Core Simple (not many elements) Easy to implement Lacks strong documentation No guidance on semantic interoperability Required for Government web resources E-gif also specifies the use of Government taxonomies E-gif also specifies the use of Government taxonomies Implementations often add to the core

IEEE LOM Institute of Electrical and Electronics Engineers Learning Objects Metadata Designed for learning objects in Higher and Further Education Learning objects can have many parts that can be split apart and reassembled Schema is designed to record and facilitate the repurposing of Learning objects UK application profile: UKLOM Core

IEEE LOM XML based Contains DC like descriptive elements Educational levels Version control information Most institutions have implemented cut down versions of the standard

Mets Metadata encoding and transmission standard Designed for digital library objects XML based Descriptive metadata can be MARC MARC DC DC IEEE LOM IEEE LOM Contains structural metadata

More information on metadata standards: