1 / 6

Timothy W. Cole ( t-cole3@uiuc ) Thomas G. Habing ( thabing@uiuc )

Experiences Implementing OAI Provider Services 13 September 2001 -- ACM SIGIR, New Orleans Open Archives: Communities, Interoperability and Services. Timothy W. Cole ( t-cole3@uiuc.edu ) Thomas G. Habing ( thabing@uiuc.edu ) University of Illinois at Urbana-Champaign.

kennethmurray
Download Presentation

Timothy W. Cole ( t-cole3@uiuc ) Thomas G. Habing ( thabing@uiuc )

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Experiences Implementing OAI Provider Services13 September 2001 -- ACM SIGIR, New OrleansOpen Archives: Communities, Interoperability and Services Timothy W. Cole(t-cole3@uiuc.edu) Thomas G. Habing(thabing@uiuc.edu) University of Illinois at Urbana-Champaign

  2. Our Observations & Generalizations • Creation & Management of Metadata Much More Difficult than Implementation of OAI PMH • Wide Range of Viable Implementation Options, But Some Workflow Accommodation Is Required • Scalability & Value of Services That Can Be Built On Top of OAI PMH Remain To Be Proven • Greatest Strength May Be Content & Format Flexibility for Metadata / Data shared via OAI Timothy W. Cole – University of Illinois at UCOpen Archives: Communities, Interoperability and Services

  3. Our Architecture Approach Timothy W. Cole – University of Illinois at UCOpen Archives: Communities, Interoperability and Services

  4. Our Technical Choices • Use of Sets: Hierarchical, Non-Overlapping, Comprehensive Set Name Reflected in Identifier (colon delimited) • Repository Updates: Scheduled Time of Day for Routine Updates Repository Taken Offline During Update (Respond 503) • Flow Control: Use with ListRecords & ListIdentifiers Only ResumptionTokens Expire with Repository Update Timothy W. Cole – University of Illinois at UCOpen Archives: Communities, Interoperability and Services

  5. Additional Metadata Formats • Other Metadata Formats of Interest: • Qualified DC in RDF (More Structured) • MARC (Have Existing Data) • EAD (Have Existing Data) • Crosswalks to DC • Better Done by Provider or Harvester? • Complex Crosswalks (e.g., from EAD) a Concern • Use of Multiple Namespaces with XSD • Canonical Namespaces, But No Canonical XSDs • XSD Import, ##any / ##other, lax Processing Timothy W. Cole – University of Illinois at UCOpen Archives: Communities, Interoperability and Services

  6. Our List of Open Issues & Concerns • IP Rights Management • Need Machine-Readable “<about>” Formats • Restricted Access Harvesting & Use Limitations • Use of Sets • Consensus on Best Practices • Concept of Null Set or Set Information as Part of Record Header Element • OAI Record Timestamp Granularity Timothy W. Cole – University of Illinois at UCOpen Archives: Communities, Interoperability and Services

More Related