OARJ: assisting deposit into multiple repository services


Published on

Presentation given by Theo Andrew at the Repository Support Project Winter School 2011, 9 February 2011.

Published in: Education
1 Like
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

OARJ: assisting deposit into multiple repository services

  1. 1. Open Access Repository Junctionassisting deposit into multiple repository services Theo Andrew Project Manager EDINA 1
  2. 2. 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
  3. 3. Open Access Repository Junction Repositories were designed as silos* *silo image from www.ashburnweb.com 3
  4. 4. Open Access Repository Junction SWORD allows transfer from one silo to another 4
  5. 5. Open Access Repository Junction Real life is more complex 5
  6. 6. Open Access Repository Junction Case study 1: multiple authored paper Paper A Journal Y Copy A2 Copy A1Researcher 2 Researcher 1 Researcher 3 Copy A3 Metadata A2 Metadata A1 Metadata A3Repository 2 Repository 1 Repository 3 6
  7. 7. Open Access Repository Junction Case study 2: Mandated open access £000s Journal Y Researcher 1 Paper A Copy A1 Copy A1Researchers 2 & 3 7
  8. 8. Open Access Repository JunctionContent providers Content receivers Institutional Repository 1 Institutional Broker 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
  9. 9. Open Access Repository Junction Broker demonstrator 1: how a journal publisher can assist Paper A OARJ broker Researcher 1 Copy A1 Metadata A1 Metadata A1 Metadata A1Repository 2 Repository 1 Repository 3 9
  10. 10. Open Access Repository Junction 1. Acceptance of manuscript by publisher 7. Publication of manuscript by Publisher 2. Publisher packages 8. Publisher creates 2nd data for transfer: data package: <manuscript #> <DOI-Citation-Manu #> <manifest> <xml>*based on NLM DTD 2.3* <file/s> 3. Package sent to OA-RJ 9. Package sent to OA-RJ 4. OA-RJ receives and 10. OA-RJ receives and unpacks data matches <manu #> 5. OA-RJ deduces correct IR locations 11. OA-RJ sets release 6. Initial notification sent date from embargo details to IR Managers that OARJ has content, not yet available for release 12. Notification sent to IRs Release metadata, withhold file until embargo OARJ broker – Dark Archive expires 13. SWORD transfer to primary IR, plus any other nominated IRs 10
  11. 11. Open Access Repository Junction All Participating 50% author Institutional NPG NPG participation rate* partner journals journals 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 607Estimate 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 duringJan - June 2010. Data retrieved from PubMed Central and ISI Web of Knowledge. (*Figure rounded down, **Still to be confirmed as a participating institutions). 11
  12. 12. Open Access Repository Junction Broker demonstrator 2: how UKPMC can assist Paper A OARJ broker Researcher 1 Copy A1 Metadata A1 Metadata A1 Metadata A1Repository 2 Repository 1 Repository 3 12
  13. 13. Open Access Repository Junction Matching authors to repositoriesAuthor Institution Repository email registry network postal address 13
  14. 14. Open Access Repository Junction SOURCES The Junction openDOAR Matched repositories ROAR Junction db: API Org IDs matched to IRs UKAMF WhoIS Named entity recognition NAMES Known Article Known IPFunding codes org ID XML location ORCID INPUTS 14
  15. 15. Open Access Repository Junction The Junction APISuite 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 IDcode) to specify the organisation, or it will deduce a locus based on the callingclient.•The script can be asked to restrict the returned list by repository type oraccepted content.•Data is returned in either JSON, Text, or XML formats http://oarepojunction.wordpress.com/junction-api/ 15
  16. 16. 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
  17. 17. Open Access Repository Junction Thankyou for listening. Questions? Project Blog:http://oarepojunction.wordpress.com/ 17
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.