1 / 17

assisting deposit into multiple repository services Theo Andrew Project Manager EDINA

assisting deposit into multiple repository services Theo Andrew Project Manager EDINA. Talk outline. The problem Case studies Multiple authored paper Mandated open access A solution The Broker model The Junction Next steps. Repositories were designed as silos*.

grady
Télécharger la présentation

assisting deposit into multiple repository services Theo Andrew Project Manager EDINA

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. assisting deposit into multiple repository services Theo Andrew Project 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 Copy A3 Repository 2 Repository 1 Repository 3

  7. Case study 2: Mandated open access £000s Journal Y Researcher 1 Paper A 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 Institutional Repository 1 Broker Institutional Repository 2 Institutional Repository 3

  9. Broker demonstrator 1: how a journal publisher can assist OARJ broker Repository 2 Repository 1 Repository 3

  10. 1. Acceptance of manuscript by publisher 7. Publication of manuscript by Publisher 2. Publisher packages data for transfer: <manuscript #> <manifest> <xml>*based on NLM DTD 2.3* <file/s> 8. Publisher creates 2nd data package: <DOI-Citation-Manu #> 3. Package sent to OA-RJ 9. Package sent to OA-RJ 4. OA-RJ receives and unpacks data 10. OA-RJ receives and matches <manu #> 5. OA-RJ deduces correct IR locations 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 13. SWORD transfer to primary IR, plus any other nominated IRs

  11. 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 OARJ broker Repository 2 Repository 1 Repository 3

  13. Matching authors to repositories Repository Author Institution email registry network postal address

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

  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] • /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/

  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?

More Related