The REPOX system Nuno Freire - nuno.freire@bnportugal.pt

1. The REPOX systemNuno Freire - nuno.freire@bnportugal.pt Europeana Local Knowledge Sharing Workshop Den Haag 13 January 2009

2. Outline • Common OAI-PMH implementation scenarios in data providers • The REPOX system • For data providers • For service providers and aggregators • REPOX current status and future releases

3. The three most common scenarios of OAI-PMH implementation • Library/Archive/Museum Management System OAI- module provided by the vendor • In-house OAI-PMH server development • Standalone OAI server

4. The three most common scenarios of OAI-PMH implementation • OAI- module provided by the vendor Library/Archive/Museum Management System OAI-PMH Server Module Metadata Repository

5. The three most common scenarios of OAI-PMH implementation • In-house OAI-PMH server development Library/Archive/Museum Management System OAI-PMH Server Metadata Repository

6. The three most common scenarios of OAI-PMH implementation • Standalone OAI-PMH server OAI-PMH Server Library/Archive/Museum Management System Metadata Repository Metadata Repository Metadata export/import

7. The three most common scenarios of OAI-PMH implementation • Metadata crosswalks • All scenarios require metadata to be converted to other formats: • To simple Dublin Core • Useful for sharing your data with other service providers • To the TEL application profile (national libraries) • To Europeana Semantic Elements • Other xml based metadata formats…

8. The three most common scenarios of OAI-PMH implementation • More detailed information about these implementation scenarios is available in “D2.1 OAI-PMH implementation and tools guidelines” from TELplus project • Available: http://www.theeuropeanlibrary.org/telplus/outcomes.php

9. Standalone OAI-PMH server • Main tasks • Choose an open source standalone OAI-PMH server • Install and configure the server • Develop metadata crosswalks for your format • Implement an procedure in the IT department to export/import the metadata records into the OAI-PMH server • Test the server

10. Standalone OAI-PMH server • Implementing an procedure in the library to transfer the metadata records from into the OAI-PMH server • Exporting the metadata records • In libraries, typically in ISO2709 or MarcXchange • Execute the metadata conversion • Generating xml records in TEL, ESE and DC • Import the records into the OAI-Server • This process should be automated as much as possible • Ideally it should be fully automatic

11. Standalone OAI-PMH server • Advantages • Very easy to deploy • It may take just a few hours • Requires only free open source software • No software development is needed • In some cases, the metadata crosswalks may require software development • Disadvantages • High maintenance in those cases where the metadata transfer can’t be fully automated

12. The REPOX system • Currently being developed by the Technical University of Lisbon • May be deployed as a standalone OAI-PMH server • For data providers • May be deployed as a OAI-PMH aggregator • For service providers

13. The REPOX system • An open-source solution (all developed in JAVA) that can be installed locally and provide an OAI-PMH Server to the exterior • Able to manage multiple internal data sources and export multiple collection sets • REPOX reuses other open-source software…

14. REPOX development phases OAI-PMH OAI-PMH REPOX TEL Central Index REPOX SRU or Z39.50 Harvester Phase 1 (2008) Internet Phase 3 (2nd half 2009) Phase 2 (2009…)

15. The REPOX system for data providersMain objective • Provide an standalone OAI-PMH server that can be deployed without any software development • Data import: • Supports any XML metadata format • Supports several variations of the ISO2709 standard • Metadata crosswalks • User interface to define the metadata crosswalks

16. The REPOX system for data providersDefining metadata crosswalks

17. The REPOX system for data providersCurrent Status and Plan • Version 1.1 released in December 2008 • Planned releases: • Support for Europeana Semantic Elements (Spring 2009) • Additional metadata crosswalks • Contributed by the libraries using REPOX • From UNIMARC and MARC21 to Europeana Semantic Elements • Additional import data formats • Z39.50/SRU harvesting (December 2009)

18. The REPOX system for service providers and aggregatorsMain objective • Provided a scalable tool for managing the metadata harvesting process: • With capacity to manage hundreds of data providers • With capacity to hold billions of metadata records

19. The REPOX system for service providers and aggregatorsCurrent Status and Plan • Deployed in small/medium scale scenarios • Public release planed for October 2009 • Planned features for managing a large number of data providers: • Scheduling harvests • Monitoring OAI-PMH servers • Automatic notifications of unavailability • Central metadata transformations (Metadata registry) • Programming APIs/Web Services • Scalability • Statistics • OAI-PMH Aggregator • Particular requirements of The European Library Office

20. The REPOX systemFuture work • Under Europeana Connect project • OAI-PMH management infrastructure • Interoperability between REPOX and the Metadata Registry for metadata crosswalks

21. Thank you • REPOX is available at: http://repox.ist.utl.pt • Email contacts: diogo.menareis@ist.utl.pt nuno.freire@bnportugal.pt