Latest blog posts
Martyn Rittman
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
Dominika Tkaczyk
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
Kornelia Korzec
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
Lucy Ofiesh
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
  • Menu
search

Documentation

Retraction Watch

Research can be modified after publication, including being corrected or retracted. This is a natural part of the research process and important for accurately reporting changes. While members can deliver this information to us, Retraction Watch has also collected a large number of retractions. Many of these have not been reported by our members.

In September 2023, we acquired the Retraction Watch database from the Center of Scientific Integrity and have made it publicly available. The database contains retractions gathered from publisher websites and is updated every working day by Retraction Watch. Some other update types, such as expressions of concern and corrections, are also included in the data, but these are not as comprehensive as retractions. Various methods are used to find retractions, including searching scholarly databases, checking publisher websites, web searches, and reports from the community. For further details, see this document.

Accessing the Retraction Watch Database

The Retraction Watch database is available in csv format from a git repository. It is updated once per working day. Git is a widely used for sharing software code and can also be used for datasets.

To create a local copy of the Retraction Watch metadata file, install git and use the command git clone https://gitlab.com/crossref/retraction-watch-data. This creates a folder called retraction-watch-data. When you want to update to the most recent version, run the command git pull from this folder. This is the recommended method for keeping a locally synced copy of the full Retraction Watch metadata. Note that it is not necessary to pull changes more than once per day.

The downloaded file contains the complete database. In the future we intend to make the data available through an API, a prototype is being tested on our labs API. The csv file was also formerly available from our labs infrastructure. This method will continue for a short while so that users can switch their collection method. We strongly recommend that existing users move to the git repository as soon as possible.

Data in the csv file is comma-separated, with lists within a single entry separated by a semicolon (such as author names or reasons for retraction). The column headings in the csv file are:

  • Record ID: An internal identifier from Retraction Watch.
  • Title: The title of the retracted or updated content.
  • Subject: The subject area of the publication.
  • Institution: Author affiliations, as given in the content.
  • Journal: The source (serial, book, etc.) in which the research was published.
  • Publisher: The organisation responsible for publication.
  • Country: Countries included in author affiliations.
  • Author: A list of author names.
  • URLS: Links to relevant pages on the Retraction Watch website, including blog posts about the retraction.
  • ArticleType: The content type, using a list of types maintained by Retraction Watch. Note that this isn’t the same as the Crossref work type.
  • RetractionDate: The date of the published retraction.
  • RetractionDOI: The DOI of the published retraction, if available. If there is no DOI, the value is either blank, ‘unavailable’, or ‘Unavailable’.
  • RetractionPubMedID: PubMED ID of the published retraction, if available. If there is no Pubmed ID, the value is either blank or 0.
  • OriginalPaperDate: The publication date of the retracted content.
  • OriginalPaperDOI: The DOI of the retracted publication, if available. If there is no DOI, the value is either blank, ‘unavailable’, or ‘Unavailable’.
  • OriginalPaperPubMedID: PubMED ID of the original publication, if available. If there is no Pubmed ID, the value is either blank or 0.
  • RetractionNature: The type of update notice, which can be Retraction, Correction, Expression of concern, or Reinstatement. Note that these are different to the list of update types in the Crossref schema.
  • Reason: A list of reasons for retraction. This uses a controlled vocabulary maintained by Retraction Watch.
  • Paywalled: Is a fee or paid subscription required to access the retraction notice? Note that there can be cases where this changes some time after publication of the notice.
  • Notes: Additional comments about the retraction.

These fields are also documented on the Retraction Watch website. Changes to the field names and vocabulary used are recorded by Retraction Watch.

Page owner: Martyn Rittman   |   Last updated 2024-October-10