1. Three Years Later: Lessons Learned from Establishing a Metadata Service Marty Kurth PCC Policy Committee Meeting November 5, 2004

2. 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?

3. 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.

4. CTS formed Metadata Services by reallocation

5. DCAPS: Digital Consulting & Production Services COPYRIGHT TECHNOLOGY SUPPORT METADATADIGITAL MEDIA DCAPS ELECTRONIC PUBLISHING DCAPS service model

6. 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.

7. 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

8. From cataloging to metadata: How our work changed Unit record Content object Unit record Content object Collection Catalog Online service Delivery system Collection Catalog Online service Delivery system metadata workflows cataloging workflows

9. 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 text encoding visual resources digital preservation metadata harvesting electronic publishing information technology

10. 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)

11. Metadata processing involves Mapping - defining relationships between metadata schemes Transformation - moving metadata between schemes Metadata management - coordinating metadata tasks and resources

12. Metadata management challenges Workflows are not well established Mapping and transformation work is often decentralized Documents and files reside throughout the library

13. Collection-specific mappings and transformations are inevitable HEARTH Samuel J. May CollectionMARC records Making of America Legacy MARC-to-TEI mapping Dates? Edition statements?

14. A mapping/transformation model Standard mapping and transformation tools Library-wide mapping and transformation tools Tools for Collection 1 Tools for Collection 3 Tools for Collection 2

15. 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

16. 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?