Latest blog posts

2024 December 12

A progress update and a renewed commitment to community

Looking back over 2024, we wanted to reflect on where we are in meeting our goals, and report on the progress and plans that affect you - our community of 21,000 organisational members as well as the vast number of research initiatives and scientific bodies that rely on Crossref metadata. In this post, we will give an update on our roadmap, including what is completed, underway, and up next, and a bit about what’s paused and why.

...Find out more

2024 December 09

A summary of our Annual Meeting

The Crossref2024 annual meeting gathered our community for a packed agenda of updates, demos, and lively discussions on advancing our shared goals. The day was filled with insights and energy, from practical demos of Crossref’s latest API features to community reflections on the Research Nexus initiative and the Board elections. Our Board elections are always the focal point of the Annual Meeting. We want to start reflecting on the day by congratulating our newly elected board members: Katharina Rieck from Austrian Science Fund (FWF), Lisa Schiff from California Digital Library, Aaron Wood from American Psychological Association, and Amanda Ward from Taylor and Francis, who will officially join (and re-join) in January 2025.

...Find out more

2024 December 07

2024 POSI audit

Background The Principles of Open Scholarly Infrastructure (POSI) provides a set of guidelines for operating open infrastructure in service to the scholarly community. It sets out 16 points to ensure that the infrastructure on which the scholarly and research communities rely is openly governed, sustainable, and replicable. Each POSI adopter regularly reviews progress, conducts periodic audits, and self-reports how they’re working towards each of the principles. In 2020, Crossref’s board voted to adopt the Principles of Open Scholarly Infrastructure, and we completed our first self-audit.

...Find out more

2024 December 05

Summary of the environmental impact of Crossref

In June 2022, we wrote a blog post “Rethinking staff travel, meetings, and events” outlining our new approach to staff travel, meetings, and events with the goal of not going back to ‘normal’ after the pandemic. We took into account three key areas: The environment and climate change Inclusion Work/life balance We are aware that many of our members are also interested in minimizing their impacts on the environment, and we are overdue for an update on meeting our own commitments, so here goes our summary for the year 2023!

...Find out more

Documentation

Controlling query execution

Some query elements have optional properties that control how a query is executed by the XML API. Our query engine operates by evaluating several logic rules in series. Each rule focuses on certain fields in the query, with the first rule processing the entire query. If any rule returns a single metadata record as its output, this DOI is taken as the result for the query, and rule processing terminates.

Controls include:

Match: use to specify level of fuzzy or exact matching. This attribute may be applied to several elements (ISSN, author, issue, article_title)
Enable-multiple-hits: allows or prevents matches returning more than one DOI
Secondary-query: instructs the system to perform a specific query if the default query mode does not produce a result. Current options include author/title, multiple hits, and author/title multiple hits.

Table of query controls

Element	Property	Value	Purpose
query	key	string	to track a query to its results
query	enable-multiple-hits	false (default)	have the system reduce the query to one DOI and return nothing if it can not do so
query	enable-multiple-hits	true	have the system return one DOI for each query rule it executes
query	enable-multiple-hits	multi_hit_per_rule	have the system return many DOIs for each query rule it executes - will produce up to 50 candidate DOIs which partially match the query
query	enable-multiple-hits	exact	rule processing is disabled, all DOIs matching a simple comparison to query values are returned
query	forward-match	false (default)	no query is stored
query	forward-match	true	store this query and re-run it automatically and notify via email any matches that are found
query	list-components	false (default)	components not included in results
query	list-components	true	list the DOIs of any components that have deposited which are linked to this DOI
query	expanded-results	false (default)	will not include article title in results
query	expanded-results	true	include article title in the results (only applicable when results format=XML_XSD)
query	secondary-query	author-title	perform author-title search if metadata search fails
query	secondary-query	multiple-hits	returns multiple hits (if present)
query	secondary-query	author-title-multiple-hits	performs author/title and multiple hits search if initial search fails
issn	match	optional	value may be missing from deposited metadata
issn	match	exact	match exactly as it appears in the query
journal_title	match	optional	not required
journal_title	match	fuzzy (default)	use fuzzy string matching
journal_title	match	exact	match exactly as it appears in the query
author	match	optional	instructs the query engine that this field may be ignored
author	match	fuzzy (default)	use fuzzy string matching
author	match	null	match if author is missing in the metadata
author	match	exact	match exactly as it appears in the query
issue	match	fuzzy (default) / exact	– see above –
first_page	match	fuzzy (default) / exact	– see above –
year	match	optional (default) / exact	– see above –
article_title	match	fuzzy (default) / exact	– see above –

Page owner: Martyn Rittman | Last updated 2020-April-08