- Количество слайдов: 16
Three Years Later: Lessons Learned from Establishing a Metadata Service Marty Kurth PCC Policy Committee Meeting November 5, 2004
Wills and won'ts ©No predictions or prescriptions ©Observations based on experience, e. g. , what changed, what stayed the same, where are the management needs? ©So what?
From "CUL Goals & Objectives 2002 -2007" II. 3. Establish and operate a "consulting to production" metadata service capable of producing metadata in a variety of formats to organize, manage, and preserve collections over time and to enable effective discovery and use.
CTS formed Metadata Services by reallocation
DCAPS service model DIGITAL MEDIA METADATA DCAPS COPYRIGHT ELECTRONIC PUBLISHING TECHNOLOGY SUPPORT DCAPS: Digital Consulting & Production Services
The Metadata Services mission Metadata Services provides metadata consulting, design, development, production, and conversion services to Cornell's faculty, staff, and community partners to increase the value of their digital resources.
Handwork is not the norm ©Our market niche has consistently been in consulting, design, development, and data conversion, not in production per se ©In production projects, the work done by automated processes far exceeds the work done by staff ©In production projects, staff resolve data anomalies and do quality control reviews
From cataloging to metadata: How our work changed Unit record Content object Collection Catalog Online service Delivery system Collection cataloging Catalog workflows Online service Delivery system Unit record metadata workflows Content object
Spanning community boundaries Our success in digital projects depends on our ability to interpret, translate, and relay messages among communities such as: higher ed research & instruction cultural heritage metadata harvesting text encoding electronic publishing visual resources information technology digital preservation
Pressures to interoperate We work in an environment marked by an increasing emphasis on (semantic) interoperability, largely due to: ©mainstreamed metadata workflows (internal cause) ©development efforts to integrate digital collection access locally and globally (external cause)
Metadata processing involves ©Mapping - defining relationships between metadata schemes ©Transformation - moving metadata between schemes ©Metadata management - coordinating metadata tasks and resources
Metadata management challenges ©Workflows are not well established ©Mapping and transformation work is often decentralized ©Documents and files reside throughout the library
I -TE o C-t i app ng m R A y. M Making of America gac e L Dates? MARC records Edi tion Samuel J. May Collection stat e men ts? Collection-specific mappings and transformations are inevitable HEARTH
A mapping/transformation model Tools for Collection 1 Standard mapping and transformation tools Library-wide mapping and transformation tools Tools for Collection 2 Tools for Collection 3
Metadata management needs ©Local: Document metadata relationships and processes organization-wide ©Global: Document community best practices for metadata elements and content ©Global/Local: Develop cross-community tools for metadata sharing and reuse to reduce costs and risk ©Local: Coordinate metadata activities using documented relationships and processes
A last question If our experiences in a library metadata environment marked by heterogeneity and interoperability suggest trends that will affect many libraries in the next few years, how should PCC support local library needs?