open access repository junction 1 assisting deposit into multiple repository services theo andrew...

Open Access Repository Junction

1

assisting deposit into multiple repository services

Theo AndrewProject Manager

EDINA


2

Talk outline

• The problem• Case studies

– Multiple authored paper– Mandated open access

• A solution– The Broker model– The Junction

• Next steps


3

Repositories were designed as silos*

*silo image from www.ashburnweb.com


4

SWORD allows transfer from one silo to another


5

Real life is more complex


6

Case study 1: multiple authored paper

Journal Y

Repository 1Repository 2 Repository 3

Copy A3


7

Case study 2: Mandated open access

Journal Y

Paper A

Researcher 1

£000s

Copy A1

Copy A1

Researchers 2 & 3


8

How a broker model could simplify things:- one consistent deposit process- single sign up for content providers and receivers- building a network of trust

Content providers Content receivers

Broker

Institutional Repository 1




9

OARJbroker

Broker demonstrator 1: how a journal publisher can assist



10

1. Acceptance of manuscript by publisher

2. Publisher packages data for transfer:<manuscript #><manifest><xml>*based on NLM DTD 2.3*<file/s>

7. Publication of manuscript by Publisher

8. Publisher creates 2nd data package:<DOI-Citation-Manu #>

3. Package sent to OA-RJ 9. Package sent to OA-RJ

13. SWORD transfer to primary IR, plus any other nominated IRs

4. OA-RJ receives and unpacks data

5. OA-RJ deduces correct IR locations

10. OA-RJ receives and matches <manu #>

11. OA-RJ sets release date from embargo details6. Initial notification sent

to IR Managers that OARJ has content, not yet available for release 12. Notification sent to IRs

Release metadata, withhold file until embargo expiresOARJ broker – Dark Archive


11

Institutional partner

All NPG journals

Participating NPG journals

50% author participation rate*

Edinburgh 194 65 32

Cambridge 1429 476 237

Oxford 962 321 160

MIT 499 166 83

Cornell 275 92 46

Yale** 248 83 41

Auckland 53 17 8

TOTAL 3660 1220 607

Estimate of the number of broker transferred items during a six month demonstrator service. Data is based upon the number of papers published in journals from the participating NPG portfolio during Jan - June 2010. Data retrieved from PubMed Central and ISI Web of Knowledge. (*Figure rounded down, **Still to be confirmed as a participating institutions).


12

Broker demonstrator 2: how UKPMC can assist

OARJbroker



13

Matching authors to repositories

Author Institution Repository

network

postal address

email registry


14

The Junction

openDOAR

ROAR

UKAMF

Junction db:Org IDs matched to IRs

Named entity recognition

WhoIS

NAMES

Funding codes

ORCID

SOURCES

AP

I

Known org ID

Article XML

Known IP location

INPUTS

Matched repositories


15

The Junction API

Suite of three APIs for interacting with the data:/api [primary point of interaction]/cgi/list/ [lists known values - type/content/country/lang/org/net] /cgi/get [used for internal AJAX functions orgs, repos, net]

http://oarepojunction.wordpress.com/junction-api/

• /api can be given a specific locus to deduce repositories (IP address or an ID code) to specify the organisation, or it will deduce a locus based on the calling client.

• The script can be asked to restrict the returned list by repository type or accepted content.

• Data is returned in either JSON, Text, or XML formats


16

The next steps

• Demonstrator services for both use cases.• March to July 2011.• Sustainability depends on success and

demand.• If positive, expand target group of IRs and

content providers.• Improvements to broker


17

Project Blog:http://oarepojunction.wordpress.com/

Thankyou for listening.Questions?

open access repository junction 1 assisting deposit into multiple repository services theo andrew...

Documents

institutional repository

repository type

journal y repository

junction api suite

complex slide

oarj broker paper

oarj broker dark archive

broker model