Presentation is loading. Please wait.

Presentation is loading. Please wait.

Open Access Repository Junction 1 assisting deposit into multiple repository services Theo Andrew Project Manager EDINA.

Similar presentations


Presentation on theme: "Open Access Repository Junction 1 assisting deposit into multiple repository services Theo Andrew Project Manager EDINA."— Presentation transcript:

1 Open Access Repository Junction 1 assisting deposit into multiple repository services Theo Andrew Project Manager EDINA

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

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

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

5 Open Access Repository Junction 5 Real life is more complex

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

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

8 Open Access Repository Junction 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 providersContent receivers Broker Institutional Repository 1 Institutional Repository 2 Institutional Repository 3

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

10 Open Access Repository Junction 10 1. Acceptance of manuscript by publisher 2. Publisher packages data for transfer: * based on NLM DTD 2.3 * 7. Publication of manuscript by Publisher 8. Publisher creates 2 nd data package: 3. Package sent to OA-RJ9. 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 11. OA-RJ sets release date from embargo details 6. 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 expires OARJ broker – Dark Archive

11 Open Access Repository Junction 11 Institutional partner All NPG journals Participating NPG journals 50% author participation rate* Edinburgh19465 32 Cambridge1429476 237 Oxford962321 160 MIT499166 83 Cornell27592 46 Yale**24883 41 Auckland5317 8 TOTAL36601220 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 Open Access Repository Junction 12 Broker demonstrator 2: how UKPMC can assist OARJ broker Paper A Copy A 1 Researcher 1 Metadata A 1 Repository 1 Repository 2 Repository 3

13 Open Access Repository Junction 13 Matching authors to repositories AuthorInstitution Repository network postal address emailregistry

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

15 Open Access Repository Junction 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 Open Access Repository Junction 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 Open Access Repository Junction 17 Project Blog: http://oarepojunction.wordpress.com/ Thankyou for listening. Questions?


Download ppt "Open Access Repository Junction 1 assisting deposit into multiple repository services Theo Andrew Project Manager EDINA."

Similar presentations


Ads by Google