Mike YalterDeveloper

DOI Services for Multiple Hosts of Book Content

Co-Access

Mike YalterDeveloper

Topics Covered:

1. What is Co-Access?2. Multi-resolution recap3. What Problem Does Co-Access Solve?4. How Will the Problem be Solved?5. How Will it Affect You?6. Technical implementation details

All involved DOIs are examined and the MR-Control string is created

All involved DOIs are updated in Handle to the new control string – Co-Access is now in effect!

All resolutions to any involved DOIs will now go to the iPage

Metadata for each DOI is unaltered

1. What is Co-Access?

The ability of multiple DOI owners to reference the same book content.

Similar to Multi-resolution, but automated.

Multi-Resolution, a quick tour

Handle resolution MR Control Strings Ipage controller Templates

Sample Multi-Resolution deposit block

<doi_data> <doi>10.1177/152216280100400122</doi> <resource>http://www.portico.org/Portico/article?article=pd3qw16ws</resource> <collection property="list-based" multi-resolution="unlock" setbyID="creftest" /> <collection property="list-based" setbyID="clockss_su"> <item label="CLOCKSS_SU"> <resource>http://triggered.stanford.clockss.org/ServeContent?rft_id=info:doi/10.1177/152216280100400122</resource>

</item> </collection> <collection property="list-based" setbyID="clockss_edina"> <item label="CLOCKSS_EDINA"> <resource>http://triggered.edina.clockss.org/ServeContent?rft_id=info:doi/10.1177/152216280100400122</resource>

</item> </collection> <collection property="list-based" setbyID="nlnether"> <item label="KB_fulltext"> <resource>http://resolver.kb.nl/resolve?urn=urn:nbn:nl-kb:edepot:ewtij:1228472125213</resource>

</item> </collection></doi_data>

Sample Control String

<locations chooseby="locatt,country,weighted"><location id="1" cr_type="MR-LIST" href="http://www.crossref.org/iPage?doi=10.50505%2Fbookseriestest" weight="1" />

<location id="2" cr_src="creftest" label="CREFTEST" cr_type="MR-LIST" href="http://help.crossref.org/what_is_a_doi" weight="0" />

<location id="3" cr_src="creftest2" label="CREFTEST2" cr_type="MR-LIST" href="http://help.crossref.org/what_is_a_doi/" weight="0" />

</locations>

MultiResolution Flow 1 of 2

Publisher 1

TemplatePage

Crossref

Publisher 2

MultiResolution Flow 2 of 2

Publisher 1

Crossref

Deposit XMLPublisher 1

Deposit XMLPublisher 2

Database

Handle

Publisher 2

Sample Multi-Resolution iPage

2. What Problem Does Co-Access Solve?

Multi-Resolution :• Requires strong coordination between publishers• Requires Multi-Resolution templates to be created and

maintained with involved publisher details

Mike YalterDeveloper

CoAccess Process Flow

1. Publishers determine what prefixes are permitted.2. Deposit is examined to determined if CoAccess is permitted, if so then CoAccess is enabled.3. Deposit is examined to find ISSN/ISBN matches. 4. Matches are checked for CoAccess permission5. If all matching DOIs are permitted CoAccess is put in effect for all DOIs.

3. How Will the Problem be Solved?

ISBN/ISSN determine Volume CoAccess Chapters determined by metadata match Server side automation Template does not need to be coordinated Simplify deposit workflow

Co-Access Flow

Deposit XMLPublisher 1

Crossref

Database

Deposit XMLPublisher 2

Handle

Handle Crossref

Crossref

Publisher 1

4. How Will it Affect You?

Crossref must be notified of publishers to be included in Co-Access group.

Book/Series titles that should be excluded from Co-Access (opted out)

Possible Multiresolution Template generated Deposit Metadata does not need to include

mrcontrol elements Automation process does not affect metadata Resolution accomplished wholly via Handle and

Crossref transparently

5. Technical Implementation Details

Determining co-access candidates Ensuring publisher permissions via groups and

opt outs Generating Handle mr-crontrol strings for all

involved DOIs Resolving arbitrary number of involved DOIs

A new Book DOI Deposit appears!

Deposit is examined for ISSN/ISBN Database is searched for Matching ISSN/ISBN

and Title No ISSN/ISBN or Title match is made DOI deposit is done normally.

A duplicate Book Deposit appears!

Deposit is examined for ISSN/ISBN Database is searched for Matching ISSN/ISBN

and Title Matching ISSN/ISBN is found! ISSN/ISBN Owner is checked against Co-Access

group – Co-Access is enabled DOI processing continues until Handle update

point

Since deposit XML is unaltered, CoAccess relationships are shown in the “crm-item” fields in UniXSD view.

<crm-item name="publisher-name" type="string">Portico</crm-item><crm-item name="prefix-name" type="string">Portico</crm-item><crm-item name="inCoAccessWith" type="doi">10.50505/bookseriestest</crm-

item><crm-item name="inCoAccessWith" type="doi">10.5055/bookseriestest</crm-item>

Chapter Metadata Matching

Book volume (by ISSN/ISBN or title) Year Page Author Component number Sequence Title Edition number

iPage notes

CoAccess iPage allows for any prefixes in CoAccess

Publisher icons are retrieved by prefix

Questions?