4. The Repository landscape – somefigures DRIVER Summit, October 20 2009 - Ghent, Belgium DRIVER activity 254 repositories – 31 countries 1,116,755 documents European repositories > 500
5. The Repository landscape – somefigures DRIVER Summit, October 20 2009 - Ghent, Belgium ¼ of the repositories come from small countries with different policies
6. The Repository landscape – somefigures Half the documents come from 200 different repositories with different practices DRIVER Summit, October 20 2009 - Ghent, Belgium
7. A look inside the repository metadata Various vocabularies No standards Various interpretations No file locations DRIVER Summit, October 20 2009 - Ghent, Belgium
10. Examples Genericdc:type text - 54.068 texte - 15.051 dc:date 2006-11-07 2004-05-31T00:00:00Z 21st century dc:language Proven x00E7 al Old to 1500 - 1 pt, es. - 1 spa;cat - 1 eng; slv - 1 noreng - 1 [BLANK] - 1 [language = Uvean, West] - 1 [language = Madngele] – 1 DRIVER Summit, October 20 2009 - Ghent, Belgium
11. Fine when your repository is the center of the universe...It becomes a mess when repositories get aggregated! DRIVER Summit, October 20 2009 - Ghent, Belgium
12. What to do about all thatambiguity? Guidelines Talking about the issues and provide theoretical solutions Validator Going from theory to implementation Helpdesk Opening channels of communication with actual repository community DRIVER Summit, October 20 2009 - Ghent, Belgium
13. Repositoryguidelines – the basics Interoperablemetadata (field content) InteroperableOAI-PHM (behaviour) Cleardistinguishable Open Access set DRIVER Summit, October 20 2009 - Ghent, Belgium
14. Guidelines – Basedon best practices Cross Europeancollaborationactivity from Repositorymanagers Service providers & Metadata experts DRIVER Summit, October 20 2009 - Ghent, Belgium
15. DRIVER Summit, October 20 2009 - Ghent, Belgium http://www.driver-support.eu/managers.html
17. Validator – interoperability check HelpingRepository managers to look from a service provider point of view Competition: the DRIVER score DRIVER Summit, October 20 2009 - Ghent, Belgium
24. DRIVER outcome Took 3.5 years of hard and multiple effort The outcome: To be continued through COAR DRIVER Summit, October 20 2009 - Ghent, Belgium Guidelines, Validator and Helpdesk have helped increase repository interoperability
25. Average interoperability with the DRIVER guidelines increases over time Total validations: 262 DRIVER Summit, October 20 2009 - Ghent, Belgium
27. Story – Tales from Repository managers “ Initially I just used the Validation tool to see if our repository is more or less on track and was reassured when the results looked good, which gave me confidence to register. - Louw Venter, Boloka Research Repository of the North-West University South Africa ” DRIVER Summit, October 20 2009 - Ghent, Belgium
28. Story – Tales from Service providers “ Adoption of a common standard for exporting metadata by repositories is very important for projects such as ours, so we can provide more effective access to their materials. The DRIVER Guidelines provide an excellent set that we hope many more repositories will take up. - Phil Cross UK Institutional Repository Search ” DRIVER Summit, October 20 2009 - Ghent, Belgium
29. TriasPoliticaModel: for reliable democracy Legislative Reliable Democracy Judicial Executive DRIVER Summit, October 20 2009 - Ghent, Belgium
30. An analogy: What we have so farfor reliable content provision Guidelines “Reliable Content Provision” Validator Helpdesk Support DRIVER Summit, October 20 2009 - Ghent, Belgium
31. A structure for formal commitment to accept Repository Interoperability Guidelines World Wide Executive enforcement enabling action on adopting Interoperability Guidelines for Repositories, World Wide, on a National and local level We DON’T have: DRIVER Summit, October 20 2009 - Ghent, Belgium
32. Some food for thought What strategies can be used to create a global “TriasPolitica” for repositories in order to come to “reliable content provision” by using interoperability guidelines? What strategies are there to maintain repository guidelines? Who is responsible? What strategies are known to create an acceptance mechanism for global agreement to repository guidelines? What strategies can be used to come to repository guidelines? Who is responsible for the (metadata) quality of the repository output? DRIVER Summit, October 20 2009 - Ghent, Belgium
33.
34. Friedrich Summann – University of Bielefeld (DE)Thankyou DRIVER Summit, October 20 2009 - Ghent, Belgium