Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

5. Your Crossref questions answered


Published on

Crossref LIVE Oakland

Published in: Technology
  • Be the first to comment

  • Be the first to like this

5. Your Crossref questions answered

  1. 1. #hashtag @CrossrefOrg Crossref, your questions answered (well, some of ‘em anyway) Crossref LIVE Oakland @CrossrefOrg #CRLIVEOakland
  2. 2. Question: So, uh, what’s new?
  3. 3. Participation Reports
  4. 4.
  5. 5. Where is the full text? What can I do with it? Is it in the iThenticate database?
  6. 6. Metadata Manager
  7. 7. Relationships Between Items
  8. 8. Grant IDs
  9. 9. Question: What are the Pain Points for publishers working with Crossref
  10. 10. Small Publishers ● What is a DOI? Can I buy a batch of DOIs? How do I make a DOI suffix? ● XML?! ● Manual metadata deposits via our helper tools ● Self-hosting OJS and implementing the DOI registration plugin ● Switching between self-publishing and contracting with a larger publisher to register content on their behalf, or vice versa
  11. 11. Mid-sized Publishers ● What metadata is my Vendor sending in for me? ● Workflow for initial registration is fine, but updating metadata over time is complicated ● Core bibliographic metadata is easy, but ancillary metadata (references, funding, licenses, etc.) is harder ● Negotiating title transfers, especially determining who will be responsible to maintain the backfile ● Workflow for journal content is well established; not always obvious how to register books, conference papers, etc.
  12. 12. Large Publishers ● Fixing problems is much harder at scale ● Some of our processes (title transfers, multiple resolution, co-access) require that publishers coordinate with one another. This can be difficult for very large organizations. ● The limits of the DOI Handle system and Crossref inspire some “creative” workarounds ● Communications lag between editorial and production teams can make for metadata errors or unregistered content ● Non-registered DOIs for recently transferred/acquired titles
  13. 13. Question: What are metadata users asking for?
  14. 14. Accurate Metadata ● Authors often catch name misspellings and other typos ● Mixups between print publication date and online publication date ● Inaccurate first page numbers ● Affiliations deposited incorrectly as group-authors ● Titles, Suffixes, or Credentials in author name tags ● Cited-by counts don’t quite meet expectations
  15. 15. Thorough Metadata ● Both publication dates (online and print) when both are available ● Page numbers, especially first page number ● Volume and Issue Numbers ● All co-authors, not just first author ● Updated resolution URLs, no broken links!
  16. 16. Even More Metadata ● Abstracts! [This is the #1 thing we get asked for] ● References ● ORCIDs ● Licenses, especially embargo dates and <free_to_read> tag when applicable
  17. 17. Question: What’s next for Crossref?
  18. 18. ● API Stability Enhancements ● Building out Metadata Manager ● Conference Proceedings and Books ● Bulk .csv updates for funding metadata, license URLs, and Similarity Check URLs ● Title Transfer Permissions ● Collaboration with OJS to improve Crossref integration plugin
  19. 19. #hashtag @CrossrefOrg Thanks Shayn Smulyan Technical Support Specialist @CrossrefSupport