Multiple Resolution @ CrossRef Chuck Koscher Director of Technology Handle System Workshop 21 June 2007 Washington, DC.

Multiple Resolution @ CrossRef

Chuck KoscherDirector of Technology

Handle System Workshop21 June 2007

Washington, DC

MR has been ‘in the works’ for a long time

-1995/99: Handle and DOI documents speak of multiple resources

-2000: Appropriate copy solutions emerge

-2003: CrossRef implementation discussed at IDF annual meeting

-2004: CrossRef begins pilot of ‘menu-based’ MR

-2005: Focus shifts to “interim-page” MR, need for country code based MR expressed at IDF annual meeting

-2006: MR pilot registers 40,000+ DOIs with interim page service

-2007: Country code based MR implemented by CNRI, CrossRef adopts CNRI.RSC_LOC approach, implements ‘production’ scale MR service

MR solution has two parts

1) Handle system data representation and resolution processes

• Best done collaboratively (ex. IDF)

• Best implemented centrally (e.g. CNRI)

2) Data management

• Deal with needs of a specific community (ex. CrossRef)

• Provide a service for these users to maintain Handle data

• Provide neutral intermediary services

CrossRef works by owners depositing XML<?xml version="1.0" encoding="UTF-8"?> …<timestamp>200706181120</timestamp> …<journal><journal_metadata> <full_title>Test Publication</full_title> <abbrev_title>T27P</abbrev_title> <issn media_type='print'>99999999</issn></journal_metadata><journal_issue> <publication_date media_type='print'> <month>5</month> <day>5</day> <year>2001</year> </publication_date> <journal_volume> <volume>33</volume> </journal_volume> <issue>1</issue></journal_issue><journal_article publication_type='full_text'> <titles> <title>Article Apr 16, 2007 11:51</title></titles> <contributors> <person_name sequence='first' contributor_role='author'> <given_name>Chuck</given_name> <surname>Koscher</surname> </person_name>

(cont.) <publication_date media_type='print'> <month>5</month> <day>9</day> <year>1995</year> </publication_date> <pages> <first_page>100</first_page><last_page>200</last_page> </pages> <doi_data> <doi>10.50505/test_200704082300</doi> <resource>http://www.crossref.org/</resource> </doi_data> <component_list> <component parent_relation="isPartOf"> <description>Some component DOI</description> <doi_data> <doi>10.50505/test_200611161118</doi> <resource>http://www.crossref.org/</resource> </doi_data> </component> </component_list>

MR ULRs expressed as added <resources> <publication_date media_type='print'> <month>5</month> <day>9</day> <year>1995</year> </publication_date> <pages> <first_page>100</first_page><last_page>200</last_page> </pages> <doi_data> <doi>10.50505/test_200704082300</doi> <resource>http://www.crossref.org/</resource> </doi_data> <collection> <property type="xref:mr:enable-interim-page"/> <property type="xref:mr:list"/> <item> <!-- this one gets display on top(or first) on the interim page --> <property type="xref:mr:label">Soil Science Society of America</property> <property type="xref:mr:use-prime-url"/> <!--Directs this link to use whatever URL the publisher originally deposited -> </item> <item> <!-- this, and subsequent items, are links to this article co-hosted on other platforms --> <property type="xref:mr:label">GeoScienceWorld</property> <resource>http://vzj.geoscienceworld.org/cgi/content/abstract/4/2/225</resource> </item> </collection> <component_list> <component parent_relation="isPartOf"> <description>Some component DOI</description> <doi_data> <doi>10.50505/test_200611161118</doi> <resource>http://www.crossref.org/</resource> </doi_data> </component> </component_list>

MR data in Handle: pilot

MR data in Handle: production

Neutral intermediary services ?

• Interim page is a way-point

• Users decide

• Independent of any target hosting platform

www.crossref.org/iPage

Interim page is template driven

Concerns

• Multiple participants with independent objectives

• Permissions

• Education (redirection confuses everyone)

• Merging overlapping data

Questions?