Reports

Our dashboard gives an overview of our ever growing corpus of metadata. We also have some resources for evaluating your own metadata records:


Resolution report

Used for DOI resolution statistics

Resolution reports are sent out via email at the beginning of each month and include statistics about DOI resolutions from the preceding month. The reports are sent by default to the business contact provided for your organization, but we can add or change the recipient(s) as needed. We’ll send you a separate report for each DOI prefix you’re responsible for.

The report includes:

  • Resolution failure rate: the percentage of DOI resolution attempts that failed. The prefix failure rate and the overall failure rate (for all Crossref members) are also included.
  • Resolutions by month: total number of resolutions per month for the past 12 months, by prefix (Count) and overall (All Members).
  • Resolution stats: resolution counts for the report prefix.
  • Top ten DOIs: list of the ten DOIs with the highest number of successful resolutions for the month, and the number of times each DOI was successfully resolved.
  • Failed DOIs: a list of DOI resolution attempts that failed (i.e. resolved to a Handle error page). This list is presented as a .csv file attached to the report email and contains both the failed DOI and number of failures.
  • Resolution counts by publication title: the number of total DOI resolutions per title

DOI Error report

When a user clicks on a DOI that has not been registered they are sent to a form that collects the DOI, the user’s email address, and any comments the user wants to share. We pass those reports and comments along nightly to the member responsible for the DOI prefix. The data is recorded in a .csv attachment.

These reports very often identify problems with your registration process so please pay attention to them. Any legitimate DOIs found in this report should be registered immediately. When a DOI reported via the form is registered, we’ll send out an alert to the reporting user (if they’ve shared their email address with us).

We find that approximately 2/3 of reported errors are ‘real’ problems. You might get this report if: * you’ve published/distributed but haven’t registered a DOI * the DOI you published doesn’t match the registered DOI * a link was formatted incorrectly (a . at the end of a DOI, for example) * an end user has made a mistake (confusing 1 for l or 0 for O, or cut-and-paste errors)


Depositor report

Used for checking basic info about your DOI registrations

These reports lists all DOIs by member and title for journals, books, and conference proceedings. Each title-level report lists all DOIs registered for the title as well as (for each DOI) the owning prefix, the deposit timestamp, the date the record was last updated, and the number of cited-by matches. To view each title-level report, select the member name then the appropriate title.

Field / missing metadata report: You can also see what basic bibliographic metadata fields are populated for your journal articles - click on the green triangle to the right of each member name to view a field / missing metadata report.

DOI Crawler: We crawl a broad sample of journal DOIs to make sure the DOIs are resolving to the appropriate page. For each journal crawled, a sample of DOIs that equals 5% of the total DOIs for the journal up to a maximum of 50 DOIs is selected. You can access the crawler details for a given journal by selecting the linked date in the ‘last crawl date’ column.


Conflict report

Used for identifying records with identical metadata

The Conflict report includes information about conflicts that have been created between member metadata records. Conflicts occur when two (or more) records are created with the same metadata.

Conflicts are flagged in your submission log when a conflict is created. We also record all current conflicts in the conflict report on our website. We’ll email you a reminder monthly if you have active conflicts.

For complete details about all your organization’s conflicts, retrieve the XML file by clicking on its name (to the right of the member name). The XML file will list every conflict for the selected prefix, with details provided for each conflict, including the DOIs and basic metadata. Other information includes:

  • conflict id is the unique ID number for the conflict.
  • causeID is the deposit submission of the DOI causing the conflict.
  • otherID is the deposit submission of the affected DOI.

You may also examine the conflicts for a particular publication by clicking on the title in the expanded view. This will display a text file where:

  • ConfID is the unique ID number for the conflict.
  • CauseID is the deposit submission of the DOI causing the conflict.
  • OtherID is the deposit submission of the affected DOI.
  • JT is the publication’s title.
  • MD is metadata for the DOIs.Metadata for DOIs in conflict will be the same.
  • DOI is the DOI involved in the conflict.

If you do not see your member name on the conflict report page you have no outstanding conflicts. If you do have conflicts, review our documentation on resolving conflicts between metadata records.


Schematron report

Used for alerts about metadata quality issues

We do a weekly post-registration metadata quality check on all journal, book, and conference proceedings submissions, and record the results in the Schematron report. If we spot a problem we’ll send you an alert. More information is available in our technical documentation. Schematron is a pattern-based XML validation language, more information is available at http://www.schematron.com/.


General reports


More questions? Review our reports FAQ or contact our support team.

Last Updated: 2017 June 20 by Patricia Feeney