Roy Tennant

1
A Metadata Infrastructure for the 21st Century

• Roy Tennant

2
007 cr unu 008 0-5/Date ent
950420 6-14/Pub date s 1995 15-17/Ctry
dcu 18-21/Illus 22/Lvl
23/Repd 24-27/Cont bs 28/Govt f
29/Conf 0 30/Fest 0 31/Index 0 32/ME
33/Fict 0 34/Biog 35-37/Lang
eng 38/ModRec 39/Source d 037
a 803-018-00155-0 b GPO 040 d GPO
d DLC d MvI 043 a n-us--- 074
a 0136 (online) 074 a 0136 086 0
a C 3.24/4MC 92-I-36 D 088 a MC
92-I-36 D 130 0 a Census of manufactures
(1992). p Industry series. 245 10 a 1992
census of manufactures. p Industry series. p
Communication equipment,
including radio and television, industries 3651,
3652, 3661, 3663, and 3669.
246 30 a Industry series. p Communication
equipment, including radio and
television, industries 3651, 3652, 3661, 3663,
and 3669 246 30 a Communication equipment,
including radio and television 260 a
Washington, DC b U.S. Dept. of Commerce,
Economics and Statistics
Administration, Bureau of the Census b For
sale by Supt. of Docs., U.S.
G.P.O., c 1995_ 300 a 1 v. (various
pagings) c 28 cm. 500 a "Issued March
1995." 500 a "MC92-I-36D." 500
a Shipping list no. 95-0134-P. 504 a
Includes bibliographical references. 530
a Also available via Internet from the Census
web site (PDF file only). 650
0 a Telecommunication equipment industry z
United States x Statistics.
651 0 a Manufactures z United States x
Statistics. 710 1 a United States. b
Bureau of the Census. 856 41 3 Connect to
online version. z Adobe Acrobat reader required
to view individual files for each
industry u http//www.census.gov/
ftp/pub/prod/1/manmin/92mmi/92manuff.html 901
a I b 2621963 c RVB 902 a
20010214000000.0 904 a 19980527 b
20010214 c 19980825 910 a 32342089
920 a gsus 920 a n 930 c C
3.24/4MC 92-I-36 D 930 c Electronic
book
3
(No Transcript)
4
Non-ILS Metadata Systems
Electronicresearchdatabases
Institutional Repositories
Silos Everywhere!
Archival Systems
DigitalLibraryCollections
Pathfinders
5
MARC
ONIX
DublinCore
VRACore
6
METS
MARC
ONIX
DublinCore
VRACore
7
Infrastructure Requirements

• Versatility
• Extensibility
• Openness and Transparency
• Low Threshold, High Ceiling
• Cooperative Management

8
Infrastructure Requirements contd

• Modularity
• Hierarchy
• Granularity
• Graceful in failure

9
A Proposal

• Create a new bibliographic metadata
  infrastructure with the following characteristics

10
A Transfer Schema

• An XML schema for ingesting, storing, and
  transferring multiple bibliographic metadata
  packages intact
• A current example the Metadata Encoding and
  Transfer Syntax (METS) demo

11
(No Transcript)
12
(No Transcript)
13
(No Transcript)
14
Bibliographic Schemata

• We must like any metadata we see
• ONIX records from publishers
• MARC records MODS records
• Dublin Core
• RFC 1607
• VRA Core
• etc.

15
Application Rules

• The AACR2 of our new infrastructure
• Rules and guidelines for use
• General application rules
• Schema-specific rules

16
Best Practices

• Implementation practices on the ground rules
  of thumb and procedures
• Because not everything should be codified in
  application rules room should be allowed for
  experimentation
• In these gray areas best practices can suggest
  non-prescriptive and reasonable sets of
  procedures

17
Crosswalks

• Librarians Should be able to walk, talk, eat, and
  drink metadata of all varieties
• Proficiency at this will require crosswalks, or
  algorithms for translating metadata from one
  schema to another
• The same infrastructure could be used to merge
  multiple formats into a searchable index

18
Enrichment Services

• Methods to enrich metadata records with
  additional information
• Examples
• Book cover art
• Tables of contents
• Book reviews
• Robot-collected metadata
• Authority control records

19
Tool Sets

• Tools to help us manage and manipulate metadata
• Examples
• XSLT Stylesheets
• Crosswalking code (e.g., OCLCs Metadata Switch
  service)
• OCLCs FRBR algorithm

20
Relationships to Other Standards and Protocols

• A rich metadata infrastructure will interoperate
  with a wide range of standards and protocols
• Examples
• OAI-PMH
• SOAP (REST)

21
Challenges

• Adapting to a diversity of record formats
• Crosswalking and Merging
• System migration
• Staff retooling
• Your favorite challenge here

22
Why It Matters

• We face many challenges and opportunities
• Events have left our once robust metadata
  infrastructure behind both conceptually and
  technically
• Our users and the services we wish to provide
  them demand a metadata infrastructure equal to
  the tasks before us
• We can and should seize the opportunity to
  recreate our foundational infrastructure