Knowledge Exchange - Persistent Identifiers

URN-NBN based Persistent Identifier infrastructure pilot

Knowledge Exchange

Persistent Identifiers

Attendees / Participants

Use Cases

Background

Goal

This presentation is about a European Project that promotes and implements a robust and sustainable identifier and resolution infrastructre for permanent access to knowledge assets for science and cultural heritage that is sustainable for the long term.

• Trustworthy Citation References

• Long Term resolution to knowledge assets

• Enhanced-publications: reliable (machine-to-machine) linking of knowledge relations e.g. Publications to Datasets

An identification and resolution infrastructure for knowledge objects that is

• International / Global
• Stable and Robust
• Sustainable on the Long Term

KE meeting on PID proposal (incl Belgium)

meeting on PID (including Australia-PILIN)

KE decides on PID project (SURF leader)

practical URN-NBN PID pilot proposal

building a global resolver demonstrator

KE workshop on URN-NBN PID pilot

KE identified PIDs as a priority

• Geert van Grootel: Department of Economy, Science and Innovation/Flanders, Belgium
• Maurizio Lunghi: The Fondazione Rinascimento Digitale/Italy
• Roberto Puccinelli: DCSPI - Ufficio Sistemi Informativi/Italy
• Stina Degerstedt: National Library Sweden/Sweden
• Christa Schöning-Walter: Deutsche National Bibliothek/Germany
• Roger Mathiesen: National Library of Norway/Norway
• Adrian Price: University of Copenhagen/Denmark
• Juha Hakula, Tommi Jauhiainen and Esa Keskitalo: National Library of Finland/Finland
• Maurice Vanderfeesten, Bas Cordewener: SURFfoundation/KE/Netherlands
• Maarten Hoogerwerf, Laurents Sesink: DANS/Netherlands

cc-by ted.com

March 2009,

Copenhagen

June 2008,

Stockholm

June 2008,

Utrecht

Feb 2009,

Copenhagen

May 2008,

Utrecht

Jan 2009,

Utrecht

Oct/Nov 2008,

Utrecht

http://driver2.dans.knaw.nl/demonstrator/demonstrator_v1.zip

http://www.ted.com/talks/tim_berners_lee_on_the_next_web.html

4min.

https://www.surfgroepen.nl/sites/surfshare/public/pid/Shared%20Documents/software

What is Knowledge Exchange?

Friday 13th of March 2009 -

TED published Tim Berners-Lee's talk about "Linked Data"

see also: http://dbpedia.org/ and http://www.gapminder.org/

In Practice

Strategic Vision

Focus Areas

Institutional Repository activities

To make a layer of scholarly and scientific content openly available on the Internet (October 2006, Berlin)

• building an integrated repository infrastructure
• exploring new developments in the future of publishing
• facilitating integrated management services within education and research institutions
• supporting the European digital libraries agenda

Invest in structural exchanges

• partner representatives meet frequently
• senior management meet at annual Strategy Forum

Effective brokerage, sharing and exchange

• studies, networks, trends, stratregies
• comparing approaches, procedures, programmes

Bring experts together

• exchanging information
• define roadmaps, prioritise issues
• exploring collaboration
• participation from partner countries and beyond

• Access Management
• National Licenses
• Open Access
• Interoperability of Repositories
• Virtual Research Environments
• Research Data
• Strategy
• Libraries in the Digital Age

Interoperability of Repositories working group

• Exchange expertise and make recommendations to partner organisations
• Initiate studies, workshops and/or joint projects

usage statistics / statistics usage

need for Author Identification,

business models for author ID based services

• Keep Knowledge Exchange connected to support DRIVER2 (EC PP7 project)
• Overseeing current joint KE IR projects

Joint Institutional Repository projects

• Enhanced Publications (e-theses & dissertations (reporting phase)
• CRIS-OAR interoperability; Persistent Identifiers (workshop February 2010)
• URN-NBN Persistent Identifier infrastructure pilot (June 2009 – June 2010)

Participation in KE activities so far

• Denmark, United Kingdom, Netherlands, Germany, France, Sweden, Norway, Italy, Finland, Belgium (and Australia)

Agreed on draft Workplan ( June 2009 – May 2010)

Policy and Organisation

Awareness and

Communication

Global Resolver and

Technical Issues

Identification

Persistency

Analysis

Design

Awareness, Promote, Buy-in

Objectives

• Defines what we need to identify for our project
• Define what we can identify with NBN, ISBN, ISSN (scope definitions)
• Granularity aspects, and how these Identifiers can work together. (ISBN for books, and NBN for images in the books.)

Approach

• workgroup for standards in order to revise relevant RFC
• workgroup for policy in order to make practical recommendations
• descriptions of best practices via case studies / use cases

Outcomes

• practical guidelines for persistent identification
• better understanding on usage and scope of Persistent ID systems
• improved and updated URN standards

Objectives

• Identify the LTP commitments made for each participating country
• Define the consequences, responsibilities and expectations of PID users
• Define the service levels, manage end user (human/machine) expectations
• Recommend updating policy (to identify versions, emulation, migration)

Approach

• LTP use cases (each country) and how it is connected to PID activities.
• Show use cases on updating and versioning
• Comply with recommendations on international LTP strategies.
• Work out principles

Outcomes

• Guidelines for services provided by PID systems
• Guidelines for updating and versioning
• Guidelines for connecting LTP international initiatives (are you a trusted repository/ how to become one)

Initiative established in 2005

Members are four funding policy organisations which have responsibility for technology development in education and research within their nations

Purpose is to add value to current activities; to increase return on investment of funding partners; and to improve quality of education and research

Method is structural knowledge exchange facilitated by staff; stimulate expert networks and co-ordinated activities; exchange strategies; explore policy opportunities to ’speak with one voice’

Objective

• Determine required functionality

Approach

• Find experts on publication and archival process, with ICT skills
• Gather requirements (functional + technical)
• Risk Analysis concerning security.
• Identify risks, chance/impact
• Create test cases for functional requirements
• Test functional requirements

Deliverables

• Requirements documents
• Report on risks
• Functional test cases and functional test report

Objectives

• Determines how functionality should be implemented.

Approach

• Find people with analytic skills
• Create a high level architecture
• Address security risks
• Define a strategy to sync mirrors
• Define a maintenance procedure
• Document the architecture
• Define operational roles and responsibility

Deliverables

• Architecture document
• Report on open issues

Syntax & Encoding

Organisation Model

Objectives

• Convince community that PID efforts are urgent
• Promote benefits of URN-NBN approach
• Raise interest in KE PID URN-NBN infrastructure pilot
• Get buy-in (for project and in general for URN-NBN PID usage)

Approach

• Create basis conditions for effective communication
• Promote the challenge
• Internal communication
• Dissemination, future preparation

Deliverables

• Website, newsletter, brochures
• Studies, reports, articles
• Lobbying, liaison efforts, events

Development

Objectives

• Revising RFC 2141 to update the URN encoding to the URL encoding standard

Approach

• Work plan for modernization of the URN standards (spring of 2009)
• Start the IETF working group (during 2009)
• DRAFT revision for the namespace registrations NBN, ISSN, ISBN (depended on outcome of work plan)

Outcomes

• IETF working group on revising the URN standards
• Work plan on revising the URN standards
• Internet DRAFT of modernizing RFC 2141 (end 2009)

Objectives

• Clearly define the roles and responsibilities,

# regarding the national resolver and registration agencies

# regarding the global resolver

# regarding Long Term Sustainability of critical components

Approach

• make definition about roles and responsibilities
• assign the roles and responsibilities in this project; proof of concept

Outcomes

• a business model
• evaluation of the business model in this pilot (test on partners)

Objective

• Implement the functionality as specified by the designers.

Approach

• Find people with system administration- and programming skills
• Implement the global resolver
• Setup mirrors and sync
• Implement DNS load-balancing
• Non-functional testing (stress, code)

Deliverables

• Prototype of global resolver
• Technical documentation
• Test report

(bas) cordewener@surf.nl

(maurice) vanderfeesten@surf.nl

Any questions?

Thank you