CrossRef Text and Data Mining services


Published on

Presentation by Carol Anne Meyer introducing CrossRef Text and Data Mining services- previously known as Prospect-to the Center for Research Libraries (CRL) Webinar on Text and Data Mining, July 17, 2013

A recording of this presentation is available here The CrossRef presentation begins at 30:40 on the video.

Published in: Business, Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

CrossRef Text and Data Mining services

  1. 1. Carol Anne Meyer Business Development, CrossRef
  2. 2. Not-for-profit membership association of scholarly publishers 4000 international publishers All subjects, all business models 83 non-publisher affiliates, 2000 library affiliates 60 million DOIs
  3. 3. Prospect - Why? All parties would benefit from standard APIs and data representations to enable TDM across both open access and subscription publishers. Subscription publishers find it impractical to negotiate multiple bilateral agreements with thousands of researchers and institutions in order to authorize TDM of subscribed content. Researchers find it impractical to negotiate multiple bilateral agreements with thousands of subscription publishers in order to authorize TDM of subscribed content.
  4. 4. Prospect - What? Content negotiation to direct researchers to machinereadable full text Central license store for researchers to agree to multiple T&Cs Means for publishers to check that researchers have agreed to T&Cs before granting TDM access
  5. 5. DOI Content Negotiation
  6. 6. (Accept: text/html)
  7. 7. (Accept: application/bibjson+json)
  8. 8. (Accept: application/unixref+xml) “prospect” “prospect”
  9. 9. Summary DOI Content Negotiation can serve as a crosspublisher API for accessing full text for TDM purposes. ! To make use of this, researchers need to query our data, and register with Prospect, and the publisher will have needed to something. ! But how do researchers determine whether the full-text is available for TDM?
  10. 10. <lic_ref>
  11. 11. Interim Solution <lic_ref> licenses/by/3.0 </lic_ref>
  12. 12. Interim Solution (possible extension - embargoes) <lic_ref startdate=”2013-08-1”> http://psychoceramics/proprietary_license.html </lic_ref> <lic_ref startdate=”2013-09-1”> </lic_ref>
  13. 13. Summary NISO working on fuller specification ! Interim solution is to at least record URIs to wellknow licenses using <lic_ref> element. ! Possible to extend <lic_ref> to handle embargos, if needed. ! But what if publishers want to use unusual licenses?
  14. 14. Prospect License Registry
  15. 15. Publisher registers licenses with Prospect Researcher reviews, accepts/declines licenses Prospect grants researcher an API Token
  16. 16. Research queries DOI using CN + API token Publisher verifies API token with Prospect (frequency at publisher discretion) If token verified AND access control allows, publisher returns fulltext
  17. 17. Prospect will provide publishers with a simple API that allows them to: • Check which licenses have been “accepted” • Revoke tokens that are detected to be abusing their systems.
  18. 18. Going into pilot this month (7/13)
  19. 19. Questions?