IDF Annual Members Meeting June 23, 2004

1

IDF – Annual Member’s Meeting

Implementation Update

IDF Annual Members Meeting June 23, 2004

2

Key benefits of the CrossRef system

As a business infrastructure for linking

No bilateral linking agreements needed – an agreement with CrossRef is a linking agreement with all CrossRef publishers

Publishers maintain their own business models while enhancing value and functionality of their content

Collaborative foundation for developments in information access

As a technology service A search engine to find DOIs based on an article’s metadata (title / author / volume / issue / page / year) Operates an OpenURL 1.0 resolver

As a technology provider Standards and industry coordination Linking expertise

IDF Annual Members Meeting June 23, 2004

3

CrossRef Indicators

307 participating publishers 290 libraries and consortia 33 agents and affiliates 11.2 million items, 9,500 journals 6 million DOI resolutions/month >2.5 million DOIs retrieved per month ~300,000 records updated per month 650,000 book and proceedings DOIs

IDF Annual Members Meeting June 23, 2004

4

CrossRef DOIs being ‘clicked’

DOI Resolutions

0

1,000,000

2,000,000

3,000,000

4,000,000

5,000,000

6,000,000

7,000,000

Jan-01 May-01 Sep-01 Jan-02 May-02 Sep-02 Jan-03 May-03 Sep-03 Jan-04 May-04

DOI Resolutions

IDF Annual Members Meeting June 23, 2004

5

What's New at CrossRef Forward linking is now operational

Provides ‘cited-by’ links CrossRef search pilot with Google is ongoing Expanded content

Gray literature: working papers, dissertations, reports, patentsMore granular: images, tables, figures, datasets

Increased usage reportsDOI clicks by prefix, title and article

Improved infrastructure : local secondary handle

IDF Annual Members Meeting June 23, 2004

6

Multiple Resolution Built on commonly available technology

• Server side includes (servlets that build HTML on the fly)• Dynamic HTML (menu operation)• DOI API (application profiles and services)

Targeted at helping solve the appropriate copy problem• A publisher hosts their journal in two locations

Technology is the easy part, governance is harder• Control over the menu structure and content• Access to the DOI (who gets to add what?)• Management of the many targets

IDF Annual Members Meeting June 23, 2004

7

Architecture – Two approaches

Metadata storageDOI

CrossRef

On the fly

Batch pre-display

DOI Registration

Page loaded in a browser1

Server side include called to populate MR info2

Servlet gets DOI AP context info 3

Menu rendered on page4

CrossRef alerts host of of new MR data for a DOI

1

Host retrieves MR info 2

Page rendered with menu info built in 3

IDF Annual Members Meeting June 23, 2004

8

Use of the DOI API

One application profile, with several services• 10.ap/profile_cr_mr_menu• 10.service/cr_mr_svc_default-form-primary 10.service/cr_mr_svc_alt-form-primary 10.service/cr_mr_svc_related-links-primary 10.service/cr_mr_svc_related-works-primary …

A working “On the fly” prototype is ready• Uses API version 2.1• Feedback given to CNRI on two items• Use to demo/pilot appropriate copy solution with real publisher data

IDF Annual Members Meeting June 23, 2004

9

Use of DOI Services

Service contexts hold segments of menu data Menu organization is controlled by policy

IDF Annual Members Meeting June 23, 2004

10

Demo

Demo