UCLA Digital Library Online User Services Committee Tech Talk #9 February 27, 2003 Specialized OAI Service Providers: A Sheet Music Harvester Data Provider, Harvester and Service Software Demonstration Presenter: Curtis Fornadley Digital Library Architect, UCLA Library

UCLA Digital Library Open Archives Initiative Protocol for Metadata Harvesting (OAI Version 2.0) The Goal of OAI: “to supply and promote an application-independent interoperability framework that can be used by a variety of communities who are engaged in publishing content on the Web.” The OAI protocol facilitates metadata harvesting Editors: Herbert Van de Sompel and Carl Lagoze Cornell University - Computer Science

UCLA Digital Library OAI Requests and Responses OAI Requests and Responses use HTTP - “just like the web”. But… All OAI Responses are valid XML Two Classes of Participants: Data Providers: expose metadata about the content in their systems. Service Providers (aka harvesters): Issue OAI requests to the systems of data providers, and use the returned metadata as a basis for building value-added services.

UCLA Digital Library

Sheet Music OAI Data Providers Indiana University (active) Johns Hopkins University (active) Library of Congress (passive) UCLA (active) Each participating institution was responsible for creating their own OAI-compliant sheet music repository. Major hurdles to becoming a Data Provider: -Programming -Data Mapping – Using OAI Minimum - Unqualified DC

UCLA Digital Library T00:10:16Z oai:ucla:sheetmusic/NS My honey's lovin' arms Meyer, Joseph [composer] Ruby, Herman [lyricist] F Major [key] New York : Fred Fisher, Inc NS BOX 183, SX English UCLA Library

UCLA Digital Library - Java 2 Enterprise Edition (J2EE) (v1.4) - Harvester code from UIUC (Mellon funded) - XML, XSLT - Oracle 8i (Windows Migrating to 9i on Linux) - Oracle Intermedia Tool Kit - Apache Web Server - JRun Application Server (v4.0) (Windows 2000) UCLA Digital Library - Software Tool Kit

UCLA Digital Library High Level Design of OAI Sheet Music Service Provider

UCLA Digital Library Note: The Harvester and the Service Provider utilize the same Database

UCLA Digital Library Virtual Collections: Persistent Sessions With a Twist In the “Resource Discovery Arena” Service Providers (or portals) will be distinguished by the services they provide.

UCLA Digital Library Virtual Collections - An Experiment of “Open Source Thought” - Any user can save “Music Stand” contents as a VC, under a name they choose. - Users can attached notes to any item, in any unlocked VC. - VC’s are stored as lightweight XML - only stores note and a pointer to record - By default, all VC’s are saved “unlocked” and can be expired at a specified interval based on the data stamp. - Locked VC’s can be saved indefinitely - Public vs. Private Virtual Collections - A search of VC note fields would allow for a whole other level of metadata development and search. - “Academic Amazon”

UCLA Digital Library VC The Selections for Class 123 Prof. Plum The items in this Virtual Collection will be on the final true this is an example of “Chicago Blues” 3102 Note the key 67 this is an example of “Delta Blues”

UCLA Digital Library Demo of the Sheet Music OAI Service Provider

UCLA Digital Library Development Cycle -Timeline “A Results Driven Project” Goal : Deliver Something - Don’t Just Talk January - February 2002: Learning Curve, OAI 1.0 data provider March - August 2002: Harvester and Service Provider. Upgrade data provider to 2.0 September - October 2002: Load data, test, debug, interface tuning November February 2003: Usability testing and reports

UCLA Digital Library Hurdles and Bumps in the Road Performance of Data Providers (ListRecords) Upgrading from 1.0 to 2.0 OAI decision Reverse engineering UIUC code Bad characters in XML - MS quotes, parsers chokes Data Mapping – harvester does not edit what arrives Getting Data mapping and programmers together QA Getting more Collections to create Data Providers…