Alphabet soup: CDM, VRA, CCO, METS, MODS, RDF - Why Metadata Matters

Alphabet Soup: CDM, VRA, CCO, METS,
MODS, RDF – Why Metadata Matters
Amanda Xu
Candidate for Metadata Analyst at
Iowa University Libraries

What is CDM (1)
• CDM = OCLC CONTENTdm Digital Collection Management
Software
• CONTENTdm 6.8 was released on June 16, 2014 with
improvements to Website configuration tool, XML
sitemaps, and expanded range of available image download
sizes
• CDM collection metadata fields compatible to qualified
Dublin Core, VRA, OAI-PMH, etc.
• 125 fields per collection
• 128,000 characters per field
• Initiatives in 1) leveraging linked data in WorldCat via
WorldCat Digital Collection Gateway or 2) transforming
CONTENTdm metadata into linked open data

What is CDM (2)
SOURCE: Ingram, G. (2014, August). OCLC CONTENTdm and the WorldCat Digital
Collection Gateway. Available: http://www.contentdm.org/USC/training/CONTENTdm-DCG-Overview-20140812.pdf

Sample CDM Metadata Field Properties
SOURCE: Best Practices for CONTENTdm and other OAI-PMH Compliant Repositories;
Creating Shareable Metadata (version 3.1)

Sample CDM OAI-PMH Record Using Qualified
Dublin Core from Iowa Digital Library (1)
related collections

Sample CDM OAI-PMH Record Using Qualified
Dublin Core from Iowa Digital Library (2)
sound
SOURCE: Univ. of Iowa Libraries. Digital Research and Publishing (2014).
Metadata extracted from OAI feed of records for materials in the Iowa Digital Library
Available: http://www.lib.uiowa.edu/drp/technology/

Sample CDM Compound Object Record Display
from Iowa Digital Library (1)
Audio player
SOURCE: Iowa Digital Library. Oral history interview with Dora Martin Berry, August 14, 1997 [excepts]
Available: http://digital.lib.uiowa.edu/cdm/ref/collection/aawiowa/id/2102

Sound

Page not found

from Libraries’ Smart Search (1)
SOURCE: University of Iowa Libraries Smart Search.
Available: http://smartsearch.uiowa.edu/
Page not found

Regroup related collections into one field

Refine search result by genre type “sound”

Initiatives in leveraging linked data in WorldCat
via WorldCat Digital Collection Gateway
SOURCE: Sarason, C. (2014, May). CONTENTdm update. CONTENTdm Users Group Meeting at
University of South Carolina.
Available: http://scholarcommons.sc.edu/cgi/viewcontent.cgi?article=1015&context=cdmusers

Initiative in Transforming CONTENTdm Metadata
into Linked Open Data
SOURCE: Lampert, C.K. & Southwick, S.B. (2013). Transforming CONTENTdm metadata into linked open data.
CONTENTdm Virtual Conference, December 5, 2013.
Available: http://www.contentdm.org/USC/training/2013/Lampert-Southwick-20131205.pdf

What is VRA Core
• “A data standard for the description of works of visual
culture as well as the images that document them”
• Developed and maintained by the VRA Core Oversight
Committee
• Current version VRA 4.0 in compliance to XML schema,
released 4/9/2007
• VRA Core implementation from ARTstor
• In 2013, Linked Data in VRA 4.0 project converting VRA
xml records into RDF/XML was completed by Jeff
Mixter as his master thesis submitted to the College of
Communication and Information of Kent State

Changes to Elements Between VRA 3.0 and 4.0
SOURCE: VRA Core 4.0 introduction. Available: http://www.loc.gov/standards/vracore/VRA_Core4_Intro.pdf

Outline of VRA Core 4.0 Elements
SOURCE: Eklund, J. “Got metadata?” VRA Core XML SEI 2007. Available:
http://core.vraweb.org/pdfs/core4_xml.pdf

VRA Core 4.0 XML Schema
• “A schema is simply an XML file that contains the rules for what can and
cannot reside in an XML data file.”
• “Specifying the valid elements, sub-elements, and attributes as well as
the values they can contain (either by data type or by providing a list of
values)”
• “Specifying which elements are required and/or are repeatable”
• “Controlling the structure by specifying which elements can be nested”
• Having two versions of the VRA Core 4.0 schema: unrestricted imposing no
restrictions on the values entered, and restricted imposing restrictions on
the data values entered into the type attributes
• Enabling the export of information from relational or proprietary database
to XML for the purposes of sharing that data beyond local system
SOURCE: VRA Core 4.0 introduction. Available:
http://www.loc.gov/standards/vracore/VRA_Core4_Intro.pdf

Screenshot of VRA Core 4.0 Restricted Schema
Type Values
SOURCE: http://www.loc.gov/standards/vracore/VRA_Core4_Restricted_schema_type_values.pdf

VRA Core 4.0 Example from
http://aal.ucsd.edu/vracore4/example001.html (1)

http://aal.ucsd.edu/vracore4/example001.html (2)

http://aal.ucsd.edu/vracore4/example001.xml (3)
Work
Image

VRA Core Implementation from ARTstor (1)
SOURCE: ARTstor Digital Library. Available: http://www.artstor.org/index.shtml

VRA Core Implementation from ARTstor (2)
Create image group in user preferred work folder
SOURCE: ARTstor Digital Library. Available: http://www.artstor.org/index.shtml

Screenshot of Linked Data in VRA Core 4.0
Project
SOURCE: Mixter, J. (2013). Linked data in VRA Core 4.0: Converting VRA XML records
into RDF/XML. Available: http://jmixter.s3-website-us-east-1.amazonaws.com/thesis/

What is CCO (1)
• CCO = Cataloging Cultural Objects: A Guide to Describing Cultural
Works and Their Images for Cultural Heritage Community, including
Museums, Libraries, Image Collections and Archives
• Provides a set of cataloging rules and syntax conventions
surrounding various elements from CDWA (Categories for
Description of Works of Art) (which contains elements and rules)
and VRA Core (which contains elements); it is more directly
analogous to AACR and DACS (Describing Archives: A Content
Standard)
• Promotes cataloging best practice for creating sharable metadata,
building common practice, complementing diverse data structure,
and improving discovery and access of cultural works
• Sponsored by the Visual Resources Association Foundation
• Published by the American Library Association (ALA) in June 2006

What is CCO (2)
SOURCE: CCO Commons. Available from
http://cco.vrafoundation.org/index.php/toolkit/cco_pdf_version/

VRA Core 4.0 and CCO
SOURCE: VRA Core 4.0 introduction.
Available: http://www.loc.gov/standards/vracore/VRA_Core4_Intro.pdf

A Sample CCO Record from CCO Commons
SOURCE: CCO Commons. Category examples: 4 paintings.
http://cco.vrafoundation.org/index.php/toolkit/index_of_examples/category_examples_4_paintings/example_1_predella_panel_named_artist

Screenshot of Metadata Standards Crosswalk
from Getty Research Institute
SOURCE: Getty Research Institute (2009). Metadata standards crosswalk. Available:
http://www.getty.edu/research/publications/electronic_publications/intrometadata/crosswalks.html

What is METS
• METS = Metadata Encoding & Transmission Standard
• Provides a standardized XML format for transmission of complex
digital library objects between systems by representing their
hierarchical structure, the names and locations of the files that
comprise those objects, and the associated metadata in XML
• Current version 1.10, adding International Council of Museums’
LIDO (Lightweight Information Describing Objects) to MDTYPE
enumeration
• In discussion of METS 2.0 data model compatible to Semantic Web
and other technologies
• Maintained by METS Editorial Board, committed to maintaining
editorial control over METS, its XML Schema, METS Profile XML
Schema, and official METS documentation
• Hosted by Library of Congress, and developed as an initiative of the
Digital Library Federation

<mets>
<metsHdr>
<dmdSec>
<amdSec>
<fileSec>
<structMap>
<structLink>
<behaviorSec>
mets Header
descriptive metadata Section
administrative metadata Section
file Section
structural Map section
structural Link section
behavior Section
Seven Major Sections of a METS Document
SOURCE: Bredenberg, K. (2011, June). METS. Communicating Archival
Metadata
conference and workshops in Stockholm 28 - 30 June 2011

<mets> METS root element
• Establishes the container for the information
being stored and /or transmitted by the
standard
• Has optional attributes: ID, OBJID, Label, Type,
Profile

<METS> Example from Hathitrust
Google Book Mets.xml
<METS:mets
xmlns:METS="http://www.loc.gov/METS/"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:gbs="http://books.google.com/gbs"
xmlns:PREMIS="info:lc/xmlns/premis-v2"
xmlns:marc="http://www.loc.gov/MARC21/slim"
xsi:schemaLocation="http://www.loc.gov/METS/
http://www.loc.gov/standards/mets/mets.xsd http://www.loc.gov/MARC21/slim
http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd
info:lc/xmlns/premis-v2 http://www.loc.gov/standards/premis/premis.xsd
OBJID="UOM_39015000024524"
PROFILE="gbs">
SOURCE: HathiTrust Google METS Example
http://www.hathitrust.org/documents/example-source-google-mets.xml

<metsHdr>
• Captures metadata about the METS document itself
• <agent>provides for various parties and their roles with respect to
the METS record to be documented
• <name>record s full name of document agent
• <note>records any additional information regarding the agent's
activities with respect to the METS document
• ROLE (string/R) specifies the function of the agent with respect to
the METS document
• TYPE(string/O) specifies the type of AGENT, e.g. individual or
organization
• <altRecordID>uses alternative record identifier values for the digital
object represented by the METS document
• <metsDocumentID>a unique identifier for the METS document
itself

<metsHdr> Example from Hathitrust Google
Book Mets.xml
<METS:metsHdr ID="UOM_39015000024524" C
REATEDATE="2010-07-
07T05:46:24" RECORDSTATUS="NEW">
<METS:agent ROLE="CREATOR" TYPE="ORGAN
IZATION">
<METS:name>Google</METS:name>
</METS:agent>
</METS:metsHdr>

<dmdSec>
• Records descriptive metadata pertaining to the
METS object as a whole or one of its components
• A descriptive metadata element can either wrap
the metadata (mdWrap) or reference it in an
external location (mdRef) or both
• Descriptive metadata can be expressed according
to many current description standards (i.e.,
MARC, MODS, Dublin Core, TEI Header, EAD, VRA,
FGDC, DDI) or a locally produced XML schema

<dmdSec> Example from Hathitrust Google
Book Mets.xml (1)
<METS:dmdSec xmlns="http://www.loc.gov/MARC21/sli
m" ID="DMDMARC">
<METS:mdWrap MIMETYPE="text/xml" MDTYPE="MA
RC" LABEL="Source MARC record">
<METS:xmlData>
<record>…
</record>
</METS:xmlData>
</METS:mdWrap>
</METS:dmdSec>

<dmdSec> Example from Hathitrust Google
Book Mets.xml (2)
SOURCE: http://www.hathitrust.org/documents/example-source-google-mets.xml

<amdSec>
• Contains the administrative metadata pertaining to the
digital object, its components and any original source
material from which the digital object is derived
• Separated into four sub-sections that accommodate
technical metadata (techMD), intellectual property
rights (rightsMD), analog/digital source metadata
(sourceMD), and digital provenance metadata
(digiprovMD)
• Each of these subsections can either wrap the
metadata (mdWrap) or reference it in an external
location (mdRef) or both

<amdSec> Example from Hathitrust Google Book
Mets.xml
<METS:amdSec>
<METS:techMD ID="TMD1">
<METS:mdWrap LABEL="production
notes" MDTYPE="OTHER" OTHERMDTYPE="Google Production Notes">
<METS:xmlData>
<gbs:productionNotes>
<gbs:badPages>3.05</gbs:badPages>
<gbs:missingPages>0.00</gbs:missingPages>
<gbs:tightBoundPages>0.46</gbs:tightBoundPages>
</gbs:productionNotes>
</METS:xmlData>
</METS:mdWrap>
</METS:techMD>
…

<techMD> Example from Hathitrust Google
Book Mets.xml
<METS:techMD ID="TABLE_OF_CONTENTS">
<METS:mdWrap LABEL="page
tags" MDTYPE="OTHER" OTHERMDTYPE="Google">
<METS:xmlData>
<gbs:pageTag>TABLE_OF_CONTENTS</gbs:pageTag>
</METS:xmlData>
</METS:mdWrap>
</METS:techMD>

<sourceMD> Example from Hathitrust Google
Book Mets.xml
<METS:sourceMD ID="S1">
<METS:mdWrap MDTYPE="OTHER" OTHERMDTYPE="Googl
e" LABEL="DESCMDRecord_Source_Library">
<METS:xmlData>
<gbs:sourceLibrary>UOM</gbs:sourceLibrary>
<gbs:sourceIdentifier>39015000024524</gbs:sourceIdentif
ier>
</METS:xmlData>
</METS:mdWrap>
</METS:sourceMD>

<digiprovMD> Example from Hathitrust Google
Book Mets.xml (1)
<METS:digiprovMD xmlns="info:lc/xmlns/premis-v2" ID="PREMIS1">
<METS:mdWrap MDTYPE="PREMIS">
<METS:xmlData>
<PREMIS:premis version="2.0">
<PREMIS:object xsi:type="representation">
<PREMIS:objectIdentifier>
<PREMIS:objectIdentifierType>barcode</PREMIS:objectIdentifierType>
<PREMIS:objectIdentifierValue>UOM_39015000024524</PREMIS:objectIdentifierValue>
</PREMIS:objectIdentifier>
<PREMIS:significantProperties>
<PREMIS:significantPropertiesType>file count</PREMIS:significantPropertiesType>
<PREMIS:significantPropertiesValue>526</PREMIS:significantPropertiesValue>
</PREMIS:significantProperties>
<PREMIS:significantProperties>
<PREMIS:significantPropertiesType>page count</PREMIS:significantPropertiesType>
<PREMIS:significantPropertiesValue>262</PREMIS:significantPropertiesValue>
</PREMIS:significantProperties>
</PREMIS:object>

<digiprovMD> Example from Hathitrust Google
Book Mets.xml (2)
…
<PREMIS:agent>
<PREMIS:agentIdentifier>
<PREMIS:agentIdentifierType>LCNAF</PREMIS:agentIdentifierType>
<PREMIS:agentIdentifierValue>Google
(Firm)</PREMIS:agentIdentifierValue>
</PREMIS:agentIdentifier>
<PREMIS:agentType>organization</PREMIS:agentType>
</PREMIS:agent>
</PREMIS:premis>
</METS:xmlData>
</METS:mdWrap>
</METS:digiprovMD>
</METS:amdSec>

<fileSec>
• Provides an inventory of and the location for
the content files that comprise the digital
object being described in the METS document
• <fileGrp> grouping the digital files
compromising the content of a METS object
either into a flat file arrangement or into a
nested arrangement

<fileSec> Example from Hathitrust
<METS:fileSec>
<METS:fileGrp ID="FG1" USE="image">
<METS:file ID="IMG00000001" MIMETYPE="image/jp2" SEQ="0000
0001" CREATED="2008-03-
27T00:00:00" SIZE="251854"CHECKSUM="0da406ad7d1957a4d544
648bf504f518" CHECKSUMTYPE="MD5" OWNERID="135107988881
16402-5">
<METS:FLocat xlink:href="00000001.jp2" LOCTYPE="OTHER" OTHER
LOCTYPE="SYSTEM"/>
</METS:file> …
</METS:fileGrp>
</METS:fileSec>

<structMap>
• Provides a means for organizing the digital content
represented by the <file> elements in the <fileSec> of
the METS document into a coherent hierarchical
structure
• Facilitates users’ understanding of structural
relationship of the content files or parts of the content
files
• Encoded as a tree of nested <div>, and child file
pointer <fptr>
• Provides a means for linking content at any hierarchical
level with relative descriptive and administrative
metadata

<structMap> Example from Hathitrust
<METS:structMap ID="SM1" TYPE="physical">
<METS:div TYPE="volume" ADMID="TMD1 PD1 S1">
<METS:div TYPE="page" ORDER="1" ADMID="FRONT_COVER IMAGE_ON_PAGE
IMPLICIT_PAGE_NUMBER">
<METS:fptr FILEID="IMG00000001"/>
<METS:fptr FILEID="TXT00000001"/>
</METS:div>…
<METS:div TYPE="page" ORDER="262" ORDERLABEL="258" ADMID="BACK_COVER
IMAGE_ON_PAGE IMPLICIT_PAGE_NUMBER">
<METS:fptr FILEID="IMG00000262"/>
<METS:fptr FILEID="TXT00000262"/>
</METS:div>
</METS:div>
</METS:structMap>
</METS:mets>

<structLink>
• Allows for the specification of hyperlinks
between the different components of a METS
structure that are delineated in a structural
map
• <smLink> indicating two a hyperlink between
two nodes in the structural map

<behaviorSec>
• Provides a means to link digital content with applications or
computer programming code that can be used in
conjunction with other info in the METS doc to render or
display the digital object or transform one or more of its
component content files
• Associates executable behaviors with content in the METS
document by means of a repeatable behavior <behavior>
element
• <interfaceDef> represents an abstract definition of the set
of behaviors represented by a particular behavior section
• <mechanism> points to a module of executable code that
implements and runs the behavior defined by the interface
definition

Screenshot of Sample Hathitrust
SOURCE: http://catalog.hathitrust.org/Record/001225921

Importance of METS
• Provides the means to specify metadata necessary for both
management of digital objects within a repository and the exchange
of such objects between repositories (or between repositories and
their users)
• Allows the sharing of efforts to develop information management
tools/services and facilitates the interoperable exchange of digital
materials among institutions (including vendors)
• Used in the role of Submission Info Package (SIP), Archival Info
Package (AIP) or Dissemination Info Package (DIP) within Open
Archival Info System (OAIS) Reference Model
SOURCE: METS Primer, available:
http://www.loc.gov/standards/mets/mets-schemadocs.html

What is MODS
• MODS = Metadata Object Description Schema
• Is an XML schema for a bibliographic element set that may be used for a variety of
purposes, and particularly for library applications
• Includes a subset of MARC fields and uses language-based tags rather than numeric
ones
• Regroups elements from MARC 21 bibliographic format
• Current version MODS 3.5 Schema, released July 8, 2013
• MARC 21 to MODS 3.5 mapping, revised October 2014
• MODS XSLT 1.0 Stylesheets for 1) MARCXML to MODS 3.5; 2) MOD 3.5 to DC updated in
August 2014
• Maintained by the MODS Editorial Committee with support from the Network
Development and MARC Standards Office of the LC
• MODS RDF Ontology in draft stage
SOURCES:
1. MODS: Uses and Features. Available: http://www.loc.gov/standards/mods/mods-overview.html
2. MODS: Conversions. Available: http://www.loc.gov/standards/mods/mods-conversions.html
2. MODS RDF Ontology. Available: http://www.loc.gov/standards/mods/modsrdf/

Changes for MODS 3.5
• Add attribute @unit to <physicalDescription><extent>
• Add rfc5646 as value for <language><languageTerm>
• Add @altFormat and @contentType attributes to <titleInfo>, <abstract>,
<tableOfContents> and <accessCondition> (Approved 2012-09-17)
• Add @eventType to <originInfo> to indicate production, publication,
distribution, manufacture
• Add @typeURI to <identifier>, <note>, and <physicalDescripton>/<note>
• Add @generator to <classification>
• Add <etal> element, a subelement of <name>
• Add @otherType to <titleInfo> element
SOURCE: Changes for MODS 3.5. Available: http://www.loc.gov/standards/mods/changes-3-
5.html

MODS Elements
SOURCE: Outline of elements and attributes in MODS version 3.5. Available:
http://www.loc.gov/standards/mods/mods-outline-3-5.html

MODS TitleInfo Element, SubElements, and
Attributes (1)

MODS Name Element, SubElements, and
Attributes (2)

MODS RelatedItem Element, SubElements,
Attributes (3)

Screenshot of “Library of Congress march” using
MODS and METS (1)
SOURCE: http://lcweb2.loc.gov/diglib/ihas/loc.natlib.ihas.100010802/mets.xml

MODS and METS (2)

MODS and METS (3)
SOURCE:
http://lcweb2.loc.gov/diglib/ihas/loc.natlib.ihas.100010802/mets.xml

MODS and METS (4)

MODS and METS (5)

MODS and METS (6)

MODS and METS (7)
Master & Service

MODS and METS (8)
Master & Service

MODS and METS (9)
SOURCE: http://lcweb2.loc.gov/diglib/ihas/loc.natlib.ihas.100010802/default.html

MODS and METS (10)
SOURCE: http://lcweb2.loc.gov/diglib/ihas/loc.natlib.ihas.100010802/default.html

Importance of MODS (1)
• Used as an SRU (Search/Retrieval via URL) specified
format, e.g. MODS 3.3
• Used as an extension schema to METS
• Represents metadata for harvesting
• Provides resource description in XML syntax
• Represents a simplified MARC record in XML
• Bundles metadata in xml with an electronic resources
• Supports discovery and management of resources, and
access to them, as well as exchange and management
of encoded descriptions

Importance of MODS (2)
7
6
5
4
3
2
1
0
Rich Compatible User-oriented Simple
MODS
DC
ONIX
MARC

What is RDF
• RDF = Resource Description Framework
• A standard model for data interchange on the Web through RDF statement in
subject-predicate-object triples, including international resource identifiers (IRIs),
or literals, blank nodes, multiple graphs
• Provides linking through IRIs by setting RDF links between datasets to enable the
discovery of additional data and to support the integration of data from multiple
sources
• Provides semantic info about resources through RDF vocabularies often defined by
RDF schema, e.g. FOAF, Dublin Core, Schema.org, SKOS
• Serialized in various formats, e.g. Turtle, JSON-LD, RDFa, RDF/XML
• Allows systems to make logical inferences by defining a model-theory semantics
for RDF graphs, the RDF, and RDFS vocabularies, e.g. {ex:allen foaf:knows ex:mary
.}(foaf:knows rdfs:domain foaf:person .} ->{ex:allen rdf:type foaf:person .}
• Allows datasets to be published and interlinked on the Web using RDF, e.g. linked
data, queried and manipulated through SPARQL
• Current version RDF 1.1, published in 2014
• Acceptance by libraries, museums and cultural heritage communities for open
linked data initiatives

Importance of RDF
• Adds machine-readable information to web pages using, e.g.
schema.org vocabulary, enabling them to be displayed in an
enhanced format on search engines or to be processed
automatically by third-party applications
• Enriches a dataset by linking it to third-party datasets
• Interlinks API feeds, making sure that clients can easily discover
how to access more information
• Uses the datasets currently published as linked data, and builds
aggregations of data around specific topics
• Builds distributed social networks by interlinking RDF descriptions
of people across multiple web sites
• Provides a standards-compliant way for exchanging data between
databases
• Interlinks various datasets within an organization, enabling cross-dataset
queries to be performed using SPARQL
SOURCE: 1. W3C RDF 1.1 Primer, W3C Working Group note 24 June 2014.
Available: http://www.w3.org/TR/rdf11-primer/
2. Schmachtenberg, M., Bizer, C., & Paulheim, H. (2014). Adoption of the Linked Data best practices in different topic domains. 13th International Semantic Web Conference (ISWC2014) –RDB
Track. Available: http://linkeddatacatalog.dws.informatik.uni-mannheim.de/state/#toc8

Screenshot of LC Linked Data Service (1)
SOURCE: http://id.loc.gov/

SOURCE: LCNAF. Available: http://id.loc.gov/authorities/names/n79041626.html

SOURCE: LC Bib Resources. Available: http://id.loc.gov/resources/bibs/634533

Screenshot of BIBFRAME.org (1)
SOURCE: LC BIBFRAME. Available: http://www.loc.gov/bibframe/

Screenshot of BIBFRAME.org (2)
SOURCE: Available: http://bibframe.org/tools/compare/bibid/634533

Screenshot of WorldCat Linked Data Explorer (1)
SOURCE: Gandi, an autobiography story of my experiments with truth.
Available: http://experiment.worldcat.org/entity/work/data/1151002411

Screenshot of WorldCat Linked Data Explorer (2)
SOURCE: Gandi, an autobiography story of my experiments with truth.
Available: http://experiment.worldcat.org/entity/work/data/1151002411

Screenshot of VIAF (1)
SOURCE: VIAF. Available: http://viaf.org/viaf/14817771/

SOURCE: http://viaf.org/viaf/71391324/rdf.xml

Screenshot of FAST Linked Data
SOURCE: Available: http://experimental.worldcat.org/fast/1354198/

Acceptance by Libraries, Museums and Cultural
Heritage Communities for Open Linked Data Initiatives
SOURCE: Crawlable linked datasets as of April 2014.
Available: http://linkeddatacatalog.dws.informatik.uni-mannheim.de/state/LODCloudDiagram.html

Why Metadata Matters
• Markup different types of digital resources by applying content description
rules and administration best practices, controlled vocabularies, metadata
standards, e.g. Qualified Dublin Core, VRA Core 4.0, CCO, METS, MODS,
RDF, etc.
• Supports intended users, including end users who search and discover the
resources, and stakeholders who develop and manage the resources
• Supports intended uses, e.g. searching, browsing, navigating, discovering,
consuming, publishing, accessing, citing, linking, repurposing,
interchanging, sharing, archiving, preserving, managing, right
management, securing, reporting and analysis, accessibility, etc.
• Indicates how resources get used, e.g. usage analysis by metadata fields
• Enables systems capabilities, e.g. out of box metadata generation and
capture
• Enables integration, analysis, and enhancement of digital resources
despite of systems, disciplines, data types, formats, file sizes, granularity,
etc.
SOURCE: Xu, A. (2014, Feb.) Role of Cataloger in the 21st Century Academic Library.
Available: http://www.slideshare.net/elephantsmith/interview-presentation-roleofcataloger21stcenturyacademiclibrary

Alphabet soup: CDM, VRA, CCO, METS, MODS, RDF - Why Metadata Matters

Alphabet soup: CDM, VRA, CCO, METS, MODS, RDF - Why Metadata Matters

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Alphabet soup: CDM, VRA, CCO, METS, MODS, RDF - Why Metadata Matters

Similar to Alphabet soup: CDM, VRA, CCO, METS, MODS, RDF - Why Metadata Matters (20)

Recently uploaded

Recently uploaded (20)

Alphabet soup: CDM, VRA, CCO, METS, MODS, RDF - Why Metadata Matters

Editor's Notes