80 likes | 192 Views
OAI: What happened since Summer 2000. End of Summer 2000 Not only e-prints research library community publishers, librarians, scholars Digital Library Federation and Coalition of Netwoked Information decided to support OAI Set up of a steerling and a technical committee
E N D
OAI: What happened since Summer 2000 • End of Summer 2000 • Not only e-prints • research library community • publishers, librarians, scholars • Digital Library Federation and Coalition of Netwoked Information decided to support OAI • Set up of a steerling and a technical committee • Revise interoperability specifications to allow adoption beyond preprints
OAI: What happened since Summer 2000 • November 2000-January 2001: Alpha test of specifications: • arXiv -- Los Alamos • NACA -- NASA • CogPrints -- U Southampton • ETD -- Virginia Tech • Thesis & Dissertations from WorldCat -- OCLC • American Memory -- Library of Congress
OAI: What happened since Summer 2000 • Alpha test of specifications (cont.): • HeinOnline law journals -- Cornell U • TEI-lite collection -- U Tennessee • STM publisher metadata -- U Illinois • Resource Disovery Network -- UKOLN • Open Language Archives -- U Pennsylvania • Open Video Project -- U Northern Carolina • CIMI
OAI: What happened since Summer 2000 • January 2001 • Released Version 1.0 of the OAI protocol
OAI – Cyclades: What happened since summer 2000 • October 2000: Cornell submitted proposal for Prism supplement funding • Interoperabiliy Architecture • Collection Service Architecture • December 2000: Cornell submitted a proposal under the NSF – EU joint DL agreement • Collection level metadata • Context sensitive extended services
Why Cyclades is interesting for the OAI? • Experimentation and evaluation of the low barrier interoperability • Harvesting • Archive description • Data description • Which services can be implemented with the current level of interoperability agreements?
Why Cyclades is interesting for the OAI? • What improvements will be possible by introducing appropriate controlled extensions? • Which are the limitations that cannot be overcome? • First example of set of interoperable archive services
Establishing assumptions • Will Cyclades harvest all the OAI registered archives or a subset of them (e.g. e-print)? • Do we require DC mandatory fields (e.g. abstract)? • Do we need specific archive descriptions? Personal view: Establish minimal initial assumptions, see how far we can go with them, and possibly to revise them later