Emailed reports come from reports@crossref.org. You should make sure the emails aren’t being caught by your spam filter. It’s also possible that we don’t have current contact information for your organization, or you aren’t the designated reports person in our database. Contact us and we’ll sort it out for you.
We can’t stop them entirely - they’re important! We can send reports to a different email address. If you don’t find our reports useful, please let us know and we’ll see what we can do.
Maybe. You can get a lot of information out of our REST API. If that doesn’t suite your needs, contact us and we’ll see how we can help.
We send out a few reports intended to help you keep your metadata records up to date. Some are sent by email, some are available on our website. The reports delivered via email are:
You should review the .csv file attached to your emailed report, and make sure that no ‘real’ DOIs are listed. Any DOIs included in your report have not been registered.
It’s possible that someone is trying to link to your content with the wrong DOI. If you Google the reported DOI you may find the source of your problem - we often find incorrect linking from user-provided content like Wikipedia, or from DOIs inadvertently distributed by publishers to PubMed. If it’s still a mystery, contact us.
The Resolution report gives you an overview of DOI resolution traffic, and can identify problems with your DOI links. Review our resolution report guide for details.
The overall resolution failure rate is around 2-4%. If you exceed that, you should take a close look at the .csv file of failed DOIs attached to your account and make sure the DOIs listed do not need to be registered. New members are often concerned about resolution rates. If your overall number of resolutions is low, a few bad DOI clicks can lead to a high failure rate. If you are registering your content on time, you don’t need to worry.
If you aren’t able to determine the source of the failed DOIs, we can run additional reports to tell where the resolutions are coming from. Unfortunately our resolution logs often do not have referring URL information so we’re not always able to determine the source of resolution failures.
We send you all failed resolutions from the preceding month, even if the content has been registered. If an unregistered DOI is clicked on December 5 but not registered until December 6, we count that as a resolution failure. If you find a lot of registered DOIs in your failed DOI list, you should make sure you aren’t distributing your DOIs before they have been registered.
It won’t impact your membership status (unless you’re truly negligent and regularly distribute DOIs without registering them) but a Crossref membership is of limited value if you don’t register your DOIs and provide quality metadata.
We aren’t currently able to provide that level of detail but may do so in the future.
We can run a report to identify the top IP addresses accessing your DOIs, contact support@crossref.org
The failed DOI .csv attached to your Resolution Report contains a list of all DOIs with failed resolution attempts. This means, if a user clicks on a DOI with your DOI prefix and the DOI is not registered, it will be included on your report.
There’s a certain amount of noise with these reports (resolutions from crawlers or automated processes) but they quite often point to problems so please pay attention to them.
Resolution statistics are based on the number of DOI resolutions made through the DOI proxy server (https://0-doi-org.wam.leeds.ac.uk/) on a month-by-month basis. These statistics give an indication of the traffic generated by users clicking DOIs. CNRI (the organization that manages the DOI resolver) sends us resolution logs at the end of every month and we pass along a selection of the data to you. We do our best to filter out obvious crawlers and machine activity.
The “unique DOI” number is the number of distinct DOIs that have been resolved. If your report lists 20 resolutions and 1 unique DOI, this means 1 DOI was resolved 20 times.
The index page is updated weekly. Title-level reports are updated dynamically.
We currently only have depositor reports for journals, books, and conference proceedings.
A ‘conflict’ can happen when two (or more) records are created with identical metadata. Read more about conflicts and your conflict report in our technical documentation.
Schematron is a pattern-based XML validation language, more information is available at http://www.schematron.com/.
We try to block obvious issues but because of a diversity of publication practices there are some things we can’t block. For example, most surnames in our database that end with ‘jr’ are the result of a publisher including a suffix (Jr.) in a surname, but there are of course surnames ending with ‘jr’.
More questions? Review other FAQs or visit our Support Center to open a support ticket or review detailed technical documentation.