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.
On September 1st we completed the final stage of the Crossmark v2.0 release and sent an email to all participating publishers containing instructions for upgrading. The first phase of v2.0 happened when we changed the design and layout of the Crossmark box back in May of this year. That allowed us to better display the growing set of additional metadata that our members are depositing, and saw the introduction of the Linked Clinical Trialsfeature.
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:
TL;DR Crossref and Datacite provide a service to link publications and data. The easiest way for Crossref members to participate in this is to cite data using DataCite DOIs and to include them in the references within the metadata deposit. These data citations are automatically detected. Alternatively and/or additionally, Crossref members can deposit data citations (regardless of identifier) as a relation type in the metadata. Data & software citations from both methods are freely propagated.
Everyone is invited to our free annual event this 1-2 November in London. (Register here)!
In years past, only Crossref members typically attended the [Crossref Annual Meeting](/crossref-live-annual). This year, we looked at the event with new eyes. We realized that we’d have even richer conversations, more creative energy, and the meeting would be even better for our members if we could rally the entire community together. So we decided to re-develop our annual event from the ground-up.
The buzz is building around PIDapalooza - the first open festival of scholarly research persistent identifiers (PID), to be held at the Radisson Blu Saga Hotel Reykjavikon November 9-10, 2016.
PIDapalooza will bring together creators and users of PIDs from around the world to shape the future PID landscape through the development of tools and services for the research community. PIDs support proper attribution and credit, promote collaboration and reuse, enable reproducibility of findings, foster faster and more efficient progress, and facilitate effective sharing, dissemination, and linking of scholarly works.
We’re putting the final touches on the changes that will allow preprint publishers to register their metadata with Crossref and assign DOIs. These changes support Crossref’s CitedBy linking between the preprint and other scholarly publications (journal articles, books, conference proceedings). Full preprint support will be released over the next few weeks.
Crossref began its service by linking publications to other publications via references. Today, this extends to relationships with associated entities. People (authors, reviewers, editors, other collaborators), funders, and research affiliations are important players in this story. Other metadata also figure prominently in it as well: references, licenses and access indicators, publication history (updates, revisions, corrections, retractions, publication dates), clinical trial and study information, etc. The list goes on.
What is lesser known (and utilized) is that Crossref is increasingly linking publications to associated scholarly artifacts.
Did you know that we have a shiny, not so new, APIkicking around? If you missed Geoffrey’s post in 2014 (or don’t want a Cyndi Lauper song stuck in your head all day), the short explanation is that the Crossref Metadata API exposes the information that publishers provide Crossref when they register their content with us. And it’s not just the bibliographic metadata either-funding and licensing information, full-text links (useful for text-mining), ORCID iDs and update information (via Crossmark)-are all available, if included in the publishers’ metadata.