Patricia Feeney Aug 31 • Support Announcements
We are having outages related to problems at our data center. Our APIs and system are affected, we'll give details when available.
UPDATE: the outage issue isn't 100% solved but we're stable-ish, intermittent outages may still occur.
Patricia Feeney Mar 8 • Support Announcements
We have recently released Crossref deposit schema 4.3.7 to support the addition of clinical trials to CrossMark. We've also included the option to deposit journals without ISSNs. Deposits without ISSNs must include a journal title-level DOI and that title-level DOI must be consistently supplied with every deposit for the journal. When an ISSN is obtained for a journal it should be supplied in deposits as well. A sample deposit without an ISSN is available here.
Patricia Feeney Mar 1 • Support Announcements
For our Enhanced CMS Subscribers (those who use OAI-PMH for harvesting), Friday - yesterday afternoon there was a bug which caused resumption tokens to direct harvesters to the same page, causing harvesting to loop through the same results over and over. This has been fixed and existing resumption tokes will work, so those who rely on automated harvesting should automatically advance through the full list of records without intervention.
Patricia Feeney August 27, 2015 • Support Announcements
We’ve begun a behind the scenes effort to make conflict identification and resolution easier to manage. When a conflict is created, it is assigned a ‘conflict ID’ that identifies that specific instance of a conflict (meaning: multiple DOIs have been identified as having identical metadata). If either DOI is re-deposited with the same metadata, a new conflict ID is created. If a conflict is flagged as ‘resolved’ (meaning no DOI is flagged as the ‘prime’ DOI), subsequent deposits of the DOIs will re-activate the conflict status and trigger a new conflict ID.
We are in the midst of consolidating existing conflict IDs into a single ID, and identifying and resolving situations where a DOI conflict has been resolved in some way but reopened. Most conflicts are straightforward, but when multiple DOIs and instances of conflict creation are involved, our conflict reports and resolution processes become unwieldy. Ultimately the important thing to identify is what DOIs are not distinct, not when or how many times the conflict has been introduced and re-introduced.
At the moment two DOIs updated with identical metadata over time can create a situation like this (displayed in our conflict management interface) :
While amusing, this report does not accurately reflect what is actually happening: two DOIs are in conflict and the conflict has been flagged as 'resolved'. After our conflict consolidation process has completed, this conflict will be assigned a single conflict ID and the correct status of ‘resolved’:
The most recent conflict status will also be reflected in conflict reports, and in submission logs when conflicts are created (or re-introduced). Those of you who regularly investigate and resolve any deposit warnings will hopefully find this a welcome change. The consolidation of conflicts will be reflected in the DOI history report. This process should be a seamless improvement for members with DOI conflicts, making conflicts easier to identify and resolve, but if you run into any issues or have questions please contact email@example.com.