Open Access Repository Junction

assisting deposit into multiple repository services

Theo Andrew Project Manager EDINA

1

Open Access Repository Junction Talk outline • The problem • Case studies – Multiple authored paper – Mandated open access • A solution – The Broker model – The Junction • Next steps

2

Open Access Repository Junction Repositories were designed as silos* *silo image from www.ashburnweb.com

3

Open Access Repository Junction SWORD allows transfer from one silo to another

4

Open Access Repository Junction Real life is more complex

5

Open Access Repository Junction Case study 1: multiple authored paper Journal Y Paper A Researcher 2 Copy A 2 Metadata A 2 Repository 2 Researcher 1 Metadata A 1 Repository 1 Copy A 1 Researcher 3 Copy A 3 Metadata A 3 Repository 3

6

Open Access Repository Junction Case study 2: Mandated open access £000s Researcher 1 Paper A Researchers 2 & 3 Copy A 1 Copy A 1 Journal Y

7

Open Access Repository Junction Content providers Content receivers Institutional Repository 1 Broker Institutional Repository 2 Institutional Repository 3 How a broker model could simplify things: - one consistent deposit process - single sign up for content providers and receivers - building a network of trust

8

Open Access Repository Junction Broker demonstrator 1: how a journal publisher can assist Paper A Researcher 1 OARJ broker Copy A 1 Metadata A 1 Repository 2 Metadata A 1 Repository 1 Metadata A 1 Repository 3

9

Open Access Repository Junction manuscript by publisher 7. Publication of manuscript by Publisher 2. Publisher packages data for transfer: * based on NLM DTD 2.3

* 3. Package sent to OA-RJ 8. Publisher creates 2 nd data package: 9. Package sent to OA-RJ 4. OA-RJ receives and unpacks data 5. OA-RJ deduces correct IR locations 10. OA-RJ receives and matches 6. Initial notification sent to IR Managers that OARJ has content, not yet available for release OARJ broker – Dark Archive 11. OA-RJ sets release date from embargo details 12. Notification sent to IRs Release metadata, withhold file until embargo expires 13. SWORD transfer to primary IR, plus any other nominated IRs

10

Open Access Repository Junction

Institutional partner

Edinburgh Cambridge Oxford MIT Cornell Yale** Auckland

TOTAL All NPG journals

194 1429 962 499 275 248 53 3660

Participating NPG journals

65 476 321 166 92 83 17 1220

50% author participation rate*

32 237 160 83 46 41 8 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).

11

Paper A Open Access Repository Junction Broker demonstrator 2: how UKPMC can assist Researcher 1 OARJ broker Copy A 1 Metadata A 1 Repository 2 Metadata A 1 Repository 1 Metadata A 1 Repository 3

12

Author Open Access Repository Junction Matching authors to repositories Institution Repository email network postal address registry

13

SOURCES open

DOAR

Open Access Repository Junction The Junction Matched repositories ROAR UKAMF WhoIS NAMES Funding codes ORCID Junction db: Org IDs matched to IRs Known org ID Named entity recognition Article XML INPUTS Known IP location

14

Open Access Repository Junction 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] •

/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 http://oarepojunction.wordpress.com/junction-api/

15

Open Access Repository Junction

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

16

Open Access Repository Junction Thankyou for listening.

Questions?

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

17