DINI certification of Institutional Repositories

1
DINI certification of Institutional Repositories
DRIVER guidelines for exposing textual
resources with OAI-PMH

• S. Dobratz, F. Scholze W. Horstmann
• DCC/DPE/DRIVER/NESTOR BERLIN 28-NOV-2007

2
ToC

• DINI-Introduction
• DINI Certificate for Document- and Publication
  Repositories
• DRIVER-Guidelines
• DRIVER-Validation Activities
• Conclusion

3
DINI

• Deutsche Initiative für Netzwerk Information
• (German Initiative for Networked Information))
• Coalition of German Higher Education
  Infrastructure- or Service-Institutions
• Libraries
• Computing Centres
• Media Centres
• Scientific Communinity
• 8 Working Groups

4
DINI primary objectives

• What?
• Creating recommendations for standardized and
  interoperable information services and
  communication networks in and between
  universities
• Structuring and construction of networked digital
  publication possibilities
• Development of archiving services
• How?
• Transfer ideas, technologies and implement recent
  developments in Germany, e.g. OAI-PMH
• Initiation and intensification of regional,
  nationwide and international collaboration
• Advice and recommendations for funding bodies,
  e.g. DFG
• ? Develop and support infrastructure

5
DINI Electronic Publishing WG

• Active since start of DINI (2000)
• Members from German Universities and Higher
  Education Institutions
• Workshops
• 2003 OAI Tutorials in Germany (Stuttgart,
  Frankfurt, Berlin)
• 2004 Implementation of digital repositories
  (Frankfurt)
• 2005 Open Access Symposium (Göttingen)
• 2006 International Workshop on Institutional
  Repositories and Enhanced and Alternative
  Metrics of Publication Impact (Berlin)
• 2006 OA experiences of certified repositories
  (Berlin)
• 2007 Open Access and IR DINI Certificate 2007
  (Frankfurt)
• 2007 Open Access Policies (Stuttgart)

6
Motivation for a Certificate

• Since 1996 development of digital repositories in
  Germany
• 2003 Survey of German University Repositories
• Approx. 120 Server in Germany
• Approx. 51 with OAI-Interfaces
• Very dissapointing use of standards
• Key Issues
• Document formats
• Metadata DC, ETD-MS, qualified DC (DL Meta)
• Interfaces promote OAI PMH, web services
• Cataloguing, subject cataloguing MAB2, DDC
• Visibility of repositories within universities

7
DINI Certificate for Document- and Publication
Repositories

• First Certificate launched in 2003 by Electronic
  Publishing working group
• Introduced quality control for Document- and
  Publication Repositories for the first time
• Defines a set of minimum standards (requirements)
  for a repository and its operator(s) mandatory
  for modern scholarly communication
• Recommends foreseeable developments that might
  turn into future requirements
• DINI Certificate 2007 released September 2006
• Focus support of Open Access (green golden
  road)

8
Certification and Institutional Repositories

• Universities need guidance for implementing
  Institutional Repositories
• Certificate can enhance visibility of the service
  Institutional repository within the University
• Quality and add-on functionalities that can be
  reached by using an Institutional Repository
  instead of a personal home page are essential
• Authenticity and integrity
• Visibility / Impact

9
DINI Certificate 2007 Content

• Visibility of the Service
• Policy, Guidelines
• Author Support
• Legal Aspects
• Security, Authenticity and Data Integrity
• Indexing
• Subject indexing
• Metadata Export
• Interfaces
• Logs and Statistics
• Long-term Availability

10
Conclusion DINI certification

• Germany 21 DINI certified IR ( 19 with 2004
  version)
• Certification enhances the quality of service of
  IRs
• Is thus an important step to increase the
  visibility of standardisation and
  interoperability
• Standardisation and interoperability are still
  badly needed to built service layers on top of
  IRs
• Certification can promote the acceptance of
  Institutional repositories
• Can thus be a vital part of OA advocacy

11
DINI contacts

• http//www.dini.de
• Susanne Dobratz dobratz_at_cms.hu-berlin.de
• Frank Scholze scholze_at_ub.uni-stuttgart.de

12
DRIVER guidelines for content providersExposing
textual resources with OAI-PMH
13
DRIVER-Guidelines

• http//www.driver-support.eu
• helpdesk_at_driver-support.eu

14
DRIVER-Guidelines

• Work-in-Progress-Disclaimer
• add-on, in-kind development of DRIVER 6 months so
  far
• Improve full-text access
• Standardize records quality in IRs
• Aggregators perspective e.g. BASE experience
• Very lightweight
• Test-bed application in BE, DE, FR, NL, UK
• Around 60 repositories
• Influenced by DINI-certificate, DAREnet

15
DRIVER ltgt DINI

• Differences
• DRIVER guidelines only aggregators perspective
• More specific for full-text availability
• DINI certificate respects all local IR operations
• Commonalities
• Metadata exposure and technical reliability only
• DINI compliance brings DRIVER compliance
• but not vv.
• DINI certificate is more than DRIVER guidelines

16
Basics of the DRIVER guidelines

• Gereral OAI-PMH protocol guidelines rule out
  implementations problems
• E.g. valid XML according to OAI-PMH
• DRIVER OAI-PMH the use of sets that define
  collections of open full-text is mandatory, if
  not all resources are textual and open access
• Plus e.g. support for incremental harvesting
• Metadata guidelines rule out shortcomings arising
  from heterogeneous interpretations of DUBLIN
  CORE.
• E.g. identifier, MIME-type, language etc
• high quality services can only build on valid IR

17
The process

• Definition of Guidelines
• Definition of test-bed repositories
• Implementation of validation tool
• Apply validation to repositories
• Communicate Reports
• Evaluate Communication
• Automate Validation Process
• Invite all repositories

18
First Impressions

• generic oai-pmh Only a few non-harvestable
  repositories
• driver oai-pmh still ambiguity manual checks
  needed
• driver oai_dc some repositories comply in the
  sample
• no repository is 100 compliant, but many are
  near
• a 5 error margin may be enough for being valid

19
Next steps

• Complete automation
• Sometime 2008
• Open up for all repositories
• Apply valid repositories for value-added services
  e.g.
• full-text indexing
• Subject browsing
• Citation analysis
• Issue further guidelines /validators e.g. for
• Specific datatypes (datasets, images etc.)
• Enhanced publications / Compound datasets
  (OAI-ORE?)

20
DRIVER guidelines contacts

• http//www.driver-support.eu
• helpdesk_at_driver-support.eu