Latest blog posts

2024 November 15

Research Integrity Roundtable 2024

For the third year in a row, Crossref hosted a roundtable on research integrity prior to the Frankfurt book fair. This year the event looked at Crossmark, our tool to display retractions and other post-publication updates to readers. Since the start of 2024, we have been carrying out a consultation on Crossmark, gathering feedback and input from a range of members. The roundtable discussion was a chance to check and refine some of the conclusions we’ve come to, and gather more suggestions on the way forward.

...Find out more

2024 November 06

How good is your matching?

In our previous blog post in this series, we explained why no metadata matching strategy can return perfect results. Thankfully, however, this does not mean that it’s impossible to know anything about the quality of matching. Indeed, we can (and should!) measure how close (or far) we are from achieving perfection with our matching. Read on to learn how this can be done! How about we start with a quiz? Imagine a database of scholarly metadata that needs to be enriched with identifiers, such as ORCIDs or ROR IDs.

...Find out more

2024 October 28

Update on the Resourcing Crossref for Future Sustainability research

We’re in year two of the Resourcing Crossref for Future Sustainability (RCFS) research. This report provides an update on progress to date, specifically on research we’ve conducted to better understand the impact of our fees and possible changes. Crossref is in a good financial position with our current fees, which haven’t increased in 20 years. This project is seeking to future-proof our fees by: Making fees more equitable Simplifying our complex fee schedule Rebalancing revenue sources In order to review all aspects of our fees, we’ve planned five projects to look into specific aspects of our current fees that may need to change to achieve the goals above.

...Find out more

2024 September 24

Meet the candidates and vote in our 2024 Board elections

On behalf of the Nominating Committee, I’m pleased to share the slate of candidates for the 2024 board election. Each year we do an open call for board interest. This year, the Nominating Committee received 53 submissions from members worldwide to fill four open board seats. We maintain a balanced board of 8 large member seats and 8 small member seats. Size is determined based on the organization’s membership tier (small members fall in the $0-$1,650 tiers and large members in the $3,900 - $50,000 tiers).

...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: Patrick Polischuk | Last updated 2020-April-08