As the linking hub for scholarly content, it’s our job to tame URLs and put in their place something better. Why? Most URLs suffer from link rot and can be created, deleted or changed at any time. And that’s a problem if you’re trying to cite them.
We’re excited to say that we’ve finished the work on our infrastructure to allow members to register preprints. Want to know why we’re doing this? Jennifer Lin explains the rationale in detail in an earlier post, but in short we want to help make sure that:
Doing so will help fully integrate preprint publications into the formal scholarly record.
The scholarly communications sector has built and adopted a series of open identifier and metadata infrastructure systems to great success.  Content identifiers (through Crossref and DataCite) and contributor identifiers (through ORCID) have become foundational infrastructure to the industry. Â
A bit different from our traditional meetings, Crossref LIVE16 next week is the first of a totally new annual event for the scholarly communications community. Â Our theme is Smart alone; brilliant together. Â We have a broad program of both informal and plenary talks across two days. There will be stations to visit, conversation starters, and entertainment, that highlight what our community can achieve if it works together.
TL;DR The indexing of Similarity Check users’ content into the shared full-text database is about to get a lot faster. Now we need members assistance in helping Turnitin (the company who own and operate the iThenticate plagiarism checking tool) to transition to a new method of indexing content.
Crossref will be updating its DOI Display Guidelines within the next couple of weeks.  This is a big deal.  We last made a change in 2011 so it’s not something that happens often or that we take lightly.  In short, the changes are to drop “dx” from DOI links and to use “https:” rather than “http:”.  An example of the new best practice in displaying a Crossref DOI link is: https://doi.org/10.1629/22161
You might recognize my name if you’ve ever applied for Crossref membership on behalf of your organization. It recently occurred to me that, since I’ve been working in our membership department for eight years, I’ve been a part of shepherding new members for half of our history. And my, how we’ve grown.
We first met the team from PaperHive at SSP in June, pointed them in the direction of the Crossref Metadata API and let things progress from there. That’s the nice thing about having an API - because it’s a common and easy way for developers to access and use metadata, it makes it possible to use with lots of diverse systems and services.
So how are things going? Alexander Naydenov, PaperHive’s Co-founder gives us an update on how they’re working with the Crossref metadata:
PIDs for conferences - your comments are welcome!
2018 April 19
Do you want to be on our Board?
2018 April 18
