Cataloging Trends and Challenges

Download Report

Transcript Cataloging Trends and Challenges

Cataloging Trends and
Challenges
Richard Wisneski
August 2008
Kelvin Smith Library
Case Western Reserve University
Current Trends and Challenges:
 Increasing publication costs
 Increasing electronic resources and freely
available resources
 Inflation rate for library materials rising
 Increasing reliance on cooperative ventures
Process of creating MARC records
will evolve over the next 5 years
 Outsourcing the creation of MARC records for
published materials will continue to expand
 Metadata in non-MARC formats from
venders will increasingly be used to populate
fields in MARC records rather than be
entered locally at every institution
 Less emphasis on rigid data formatting; more
emphasis on usefulness of data to patrons.
FRBR (Functional Requirements for
Bibliographic Records)
 Displays existing subject reference structures
in authority files better
 Allows users to better navigate the subject
reference structure, moving from "see
references" to authorized headings.
 Display will make better use of relationships
between bibliographic entities.
FRBR -- Continued
Example: OCLC Fiction Finder
Cataloging Staffs…
 Will apply appropriate metadata format to a
particular situation
 Will know non-MARC standards and
emerging metadata schemes, such as Dublin
Core, VRA, TEI, MODS
 More time devoted to authority control,
subject analysis, resource identification
From "On the record: Report of The Library
of Congress Working Group on the Future of
Bibliographic Control"
5 recommendations:
1. Increase cooperation and sharing of
bibliographic records.
2. Expose users to rare and unique materials
held by libraries
3. Recognize the WWW as the platform for
delivery.
4. Investigate the potential of FRBR
5. Strengthen library and information science
programs
From "Response to 'On the record: Report of the
Library of Congress Working Group on the
Future of Bibliographic Control'"
Supports:
1. Being more flexible in accepting bibliographic data from others
(e.g. publishers) that do not conform precisely to U.S. library
standards
2. Data sharing with publishers and vendor partners
4. Development of mechanisms to use data and metadata from
network resources (e.g. indexing services, Amazon, IMDb)
5. Exploration of tools to share bibliographic data, such as Open
Archive Initiative-Protocol for Metadata Harvesting (OAI-PMH).
6. More cataloging of materials in special collections -- finding aids
accessible vial online catalogs (e.g. EAD)
7. Develop a more flexible, extensible metadata carrier -- recognize
that Z39.2/MARC are no longer fit for the purpose; work to
implement a carrier that is capable of representing the full range
of data of interest to libraries
8. MODS, MARCXML, METS, Dubin Core, and other evolving
standards to enable broader use and maximization of LC data
Metadata Example
 MARC Record:
Umbrellas and their history
Umbrellas and their History
LEADER 00000nam 2200000Ia 4500
001 53177393
003 OCoLC
005 20031010070046.0
008 031010s1871 enka r 000 0 eng d
040 CWR|cCWR
049 CWRR
090 GT2210|b.S3 1871a
100 1 Sangster, William,|d1808-1888
245 10 Umbrellas and their history /|cby William Sangster ; with illustrations by
Bennett
260 London [England] ;|aNew York [N.Y.] :|bCassell, Petter, and Galpin,|c[1871?]
300 80 p. :|bill. ;|c19 cm
533 Photocopy.|bLaCrosse, Wis. :|cBrookhaven Press :|cdigital production by
Northern Micrographics, Inc.,|d2001.|e29 cm
650 0 Umbrellas
776 1 |cOriginal|w(DLC) 14016385
MARC XML
 MARC XML
 <record>
<leader>01177nam a2200313Ia 4500</leader>
<controlfield tag="001">2407600</controlfield>
<controlfield tag="005">19890803132127.0</controlfield>
<controlfield tag="008">760901s1871 enka 000 0 engm </controlfield>
<datafield tag="010" ind1=" " ind2=" ">
<subfield code="a">14016385</subfield>
</datafield>
<datafield tag="035" ind1=" " ind2=" ">
<subfield code="a">.b16932407</subfield>
<subfield code="b">ux </subfield>
<subfield code="c">-</subfield>
</datafield>
Metadata Encoding and
Transmission Standard (METS)
Used for:
 Encoding administrative, structural, and descriptive
metadata about objects within a digital library
 Providing a useful standard for the exchange of
digital library objects between repositories
 Providing a coherent means for archiving digital
objects and their metadata
 Standardizing the containers for digital library
metadata (similar to MARC) and the rules for the
metadata content itself (similar to AACR).
Metadata Encoding and Transmission
Standard (METS) -- Continued
Used by
 Mark Twain Project
 California Digital Library, Escholarship
 University of Michigan, Mbooks
 Etc.
METS RECORD SAMPLE:
<mets:dmdSec ID="DID001" CREATED="2006-0822T15:56:00">
<mets:mdWrap MDTYPE="MODS">
<mets:xmlData>
<mods:mods version="3.0">
<mods:titleInfo>
<mods:title>Umbrellas and their history</mods:title>
</mods:titleInfo>
<mods:name type="personal">
<mods:namePart>Sangster, William</mods:namePart>
<mods:namePart type="date">18081888</mods:namePart>
<mods:role>
<mods:roleTerm authority="marcrelator"
type="text">creator</mods:roleTerm>
</mods:role>
Metadata Object Description
Schema (MODS)
Used for…
 Representing metadata for harvesting
 Representing a simplified MARC record in
XML
 Simplifying the full MARC format, yet being
richer than Dublin Core
 Being more end user oriented than the full
MARCXML
Metadata Object Description
Schema (MODS) -- Continued
Used By:
 Library of Congress American Memory
Project
 Kelvin Smith Library’s Classics Slide
Collection
 Center for Digital Initiatives, Brown University
 Ethnomusicological Video, Indiana University
 Etc.
MODS Record Sample
<mods version="3.0">
MARC Tags:
• 1XX – author
• 245 – title
• 300 – physical description
• 546 – language
• 6XX – subject headings
• 500 – general note
titleInfo
Note
Name
Subject
typeOfResource
Classification
Genre
relatedItem
originInfo
Identifier
Language
Location
Extent
Access
Condition
Abstract
tableOfContents
targetAudience
Dublin Core (DC)
Used for
 Promoting the widespread adoption of interoperable
metadata standards
 Providing card catalog-like definitions for defining the
properties of objects for Web-based resource
discovery systems
 Representing 15 core elements likely to be useful
across a broad range of disciplines of study.
 Providing a core set of elements that could be shared
across disciplines or within any type of organization
Dublin Core (DC)
Used by
 Kelvin Smith Library Digital Case
 Cleveland State University’s Cleveland
Memory Project
 Ohio’s Heritage Northeast
 Etc. etc.
Dublin Core Record Sample
<dc:title/>
<dc:creator>Sangster, William, 1808-1888</dc:creator>
<dc:publisher>London : Cassell, Petter, and
Galpin</dc:publisher>
<dc:date>1871</dc:date>
<dc:description>by William Sangster.</dc:description>
<dc:subject>Umbrellas </dc:subject>
<dc:type>text</dc:type>
<dc:language>English</dc:language>
<dc:type>80 p. illus. 19 cm.</dctype>
<dc:format>text/xml</dc:format>
<dc:rights>This work is in the public domain and may be freely
downloaded for personal or academic use.</dc:rights>
<dc:identifier>sanumb00</dc:identifier>
Text Encoding Initiative (TEI)
Used for:
 Storing information for the long term
 Analyzing information
 Sharing information
 Digital libraries
 Scholarly editions
 Manuscript collections and descriptions
Text Encoded Initiative (TEI)
Used by
 Brown University, Women Writers Project
 University of Maryland, Dickinson Electronic
Archives
 University of Virginia, Westward Exploration
 Miami University of Ohio, The Poetess
Archive
 Etc., etc.
TEI Record Sample
<teiHeader>
<fileDesc>
<titleStmt>
<title type="m">An electronic version of Umbrellas and their
history</title>
<author>Sangster, William, 1808-1888</author>
<respStmt>
<resp>Creation of TEI.2-conformant electronic version.</resp>
<name>Kelvin Smith Library, Case Western Reserve
University</name>
</respStmt>
</titleStmt>
<extent>115 kb</extent>
<publicationStmt>
<distributor n="collection">KSL Digital Book Collection</distributor>
<publisher>Digital Case, Kelvin Smith Library, Case Western Reserve
University</publisher>
<pubPlace>Cleveland, Ohio</pubPlace>
<date value="2006">2006</date>
Conclusion
Think of history behind MARC
 Transfer data to
catalog cards
 Applicable to today’s
online environment?