Blog

Measuring Metadata Impacts: Books Discoverability in Google Scholar

This blog post is from Lettie Conrad and Michelle Urberg, cross-posted from the The Scholarly Kitchen. As sponsors of this project, we at Crossref are excited to see this work shared out. The scholarly publishing community talks a LOT about metadata and the need for high-quality, interoperable, and machine-readable descriptors of the content we disseminate. However, as weā€™ve reflected on previously in the Kitchen, despite well-established information standards (e.g., persistent identifiers), our industry lacks a shared framework to measure the value and impact of the metadata we produce.

How funding agencies can meet OSTP (and Open Science) guidance using existing open infrastructure

In August 2022, the United States Office of Science and Technology Policy (OSTP) issued a memo (PDF) on ensuring free, immediate, and equitable access to federally funded research (a.k.a. the ā€œNelson memoā€). Crossref is particularly interested in and relevant for the areas of this guidance that cover metadata and persistent identifiersā€”and the infrastructure and services that make them useful. Funding bodies worldwide are increasingly involved in research infrastructure for dissemination and discovery.

Better preprint metadata through community participation

Preprints have become an important tool for rapidly communicating and iterating on research outputs. There is now a range of preprint servers, some subject-specific, some based on a particular geographical area, and others linked to publishers or individual journals in addition to generalist platforms. In 2016 the Crossref schema started to support preprints and since then the number of metadata records has grown to around 16,000 new preprint DOIs per month.

Flies in your metadata (ointment)

Quality metadata is foundational to the research nexus and all Crossref services. When inaccuracies creep in, these create problems that get compounded down the line. No wonder that reports of metadata errors from authors, members, and other metadata users are some of the most common messages we receive into the technical support team (we encourage you to continue to report these metadata errors). We make membersā€™ metadata openly available via our APIs, which means people and machines can incorporate it into their research tools and services - thus, we all want it to be accurate.

2022 public data file of more than 134 million metadata records now available

In 2020 we released our first public data file, something weā€™ve turned into an annual affair supporting our commitment to the Principles of Open Scholarly Infrastructure (POSI). Weā€™ve just posted the 2022 file, which can now be downloaded via torrent like in years past. We aim to publish these in the first quarter of each year, though as you may notice, weā€™re a little behind our intended schedule. The reason for this delay was that we wanted to make critical new metadata fields available, including resource URLs and titles with markup.

Amendments to membership terms to open reference distribution and include UK jurisdiction

Tl;dr Forthcoming amendments to Crossref’s membership terms will include: Removal of ‘reference distribution preference’ policy: all references in Crossref will be treated as open metadata from 3rd June 2022. An addition to sanctions jurisdictions: the United Kingdom will be added to sanctions jurisdictions that Crossref needs to comply with. Sponsors and members have been emailed today with the 60-day notice needed for changes in terms. Reference distribution preferences In 2017, when we consolidated our metadata services under Metadata Plus, we made it possible for members to set a preference for the distribution of references to Open, Limited, or Closed.

With a little help from your Crossref friends: Better metadata

We talk so much about more and better metadata that a reasonable question might be: what is Crossref doing to help? Members and their service partners do the heavy lifting to provide Crossref with metadata and we donā€™t change what is supplied to us. One reason we donā€™t is because members can and often do change their records (important note: updated records do not incur fees!). However, we do a fair amount of behind the scenes work to check and report on the metadata as well as to add context and relationships.

A Registry of Editorial Boards - a new trust signal for scholarly communications?

Background Perhaps, like us, you’ve noticed that it is not always easy to find information on who is on a journal’s editorial board and, when you do, it is often unclear when it was last updated. The editorial board details might be displayed in multiple places (such as the publisher’s website and the platform where the content is hosted) which may or may not be in sync and retrieving this information for any kind of analysis always requires manually checking and exporting the data from a website (as illustrated by the Open Editors research and its dataset).

A ROR-some update to our API

Earlier this year, Ginny posted an exciting update on Crossrefā€™s progress with adopting ROR, the Research Organization Registry for affiliations, announcing that we’d started the collection of ROR identifiers in our metadata input schema. šŸ¦ The capacity to accept ROR IDs to help reliably identify institutions is really important but the real value comes from their open availability alongside the other metadata registered with us, such as for publications like journal articles, book chapters, preprints, and for other objects such as grants.

Come and get your grant metadata!

Tl;dr: Metadata for the (currently 26,000) grants that have been registered by our funder members is now available via the REST API. This is quite a milestone in our program to include funding in Crossref infrastructure and a step forward in our mission to connect all.the.things. This post gives you all the queries you might need to satisfy your curiosity and start to see what’s possible with deeper analysis. So have the look and see what useful things you can discover.