1. Building Repository Networks with DRIVER Wolfram Horstmann Universität Bielefeld

2. DRIVER motivation Scholarly communication changes towards distributed provision of text, data and services Repositories are thought as a saviour in this development building such a distributed system An infrastructure supporting distributed repositories and services is needed (and reactions) (needs explanation)

3. DRIVER Objectives Organisational structure for repositories e.g. the „Confederation“ Improving quality and standards in local rep. e.g. validation procedures Building a distributed runtime system e.g. service and data sharing Target Groups Repository Managers Service Providers Information System Executives

4. 44 A DRIVER Genealogy 2007 2008200920102011 COAR D-NET v1.0D-NET v1.2 Portal

5. Some Results: Studies

6. Some Results: A Portal

7. Some Results: A Search

8. Some Results: Repository Registration

9. Some Results: Guidelines Build on knowledge from past & current IR projects (EU) 26 actively involved contributors (experts and repository managers) from 8 countries. Practical answers on how to: Improve full-text access Standardize metadata quality Create a reliable infrastructure for permanent identification, resolution, traceability and storage Resolve semantic and classification issues

10. Some Results: Support structures

11. Some Results: Repositories 200++ harvested repositories 30++ countries 1Mio++ documents

12. Some Results: Service-Oriented-Arch. 9 hosting nodes 25+ Functionality typologies (services) 36 service Instances 3 applications: DRIVER Portal, EFG, Belgium, Spain, Slovenia, China (?)

13. 13 Some Results: Runtime-System & Hosting Enabling Layer Data Layer EU Open Access Repositories Functionality Layer Administrators End users Advanced User Interfaces National portals Project Applications

14. Some Results: A software Meant for large service providers only!

15. Options for Networking of Repositories Using the DRIVER D-NET production system Forming an open & reusable information space Quality standards of repositories in the focus Building a service based on DRIVER D-NET User interface for a specific section of DRIVER Becoming national aggregator / country correspondent Run your own services on your own machines Having an own D-NET installation Maintain your own hardware and software Develop your own infrastructure service

16. Cooperation with CAS

17. Technical cooperation with CAS: Basics Exploring own infrastructure most powerful / demanding Own D-NET infrastructure for CAS IR-Grid Own deployment, individual service development Bielefeld helps with installation of CAS D-NET Win/Win-Situation for CAS and D-NET CAS receives exclusive test-version D-NET v1.1 Not ready to install but therefore highest available version Dedicated personell effort in Bielefeld for CAS CAS tests aptitude of D-NET for their purposes No obligation from DRIVER to take it D-NET receives feedback for D-NET v1.2 What has to be improved or extended?

18. Technical cooperation with CAS: Events Start in Summer 2009 with Mr. Zhu Provision of machines in China Remote installation of D-NET by Imialek (Bielefeld) First tests and feedback by Mr. Zhu Ongoing communication between Imialek and Mr. Zhu Visit of Ma Jianxia in November 2009 Double Checking CAS repository standards Study of issues and challenges with D-NET v1.1 Registration of Chinese repositories in DRIVER D-NET Aggregating 2 Chinese repositories on CAS D-NET Will continue with limited scope: eMail / Visits

19. Technical cooperation with CAS: Results „Much richer than initially expected“ DRIVER helping CAS with repository standards Important for being „networkable“, also internationally CAS helping DRIVER identifying challenges with v1.1 Documentation, installation routines, interface localization Communication between techn. partners established Bielefeld (Germany), Athens (Greece), Pisa (Italy) CAS should now have a „flavour“ of D-NET How to build a powerful and flexible IR-infrastructure Colloboration in open-source service development ? CAS as Chinese „Country Correspondent“ for DRIVER? Decision still open – but experience is promising To be continued …

20. Thanks