Repair deposit processing so that book and conference-level title records are not duplicated resulting in multiple title records in the admin tool
Background
comment: # The admin tool continues to create duplicate records when simultaneous deposits get processed for the same book/conference during initial content registration.
For example, Silverchair submitted DOIs for the ASME 2020 Pressure Vessels & Piping Conference using proceedings title Volume 1: Codes and Standards in simultaneous submissions:
https://doi.crossref.org/servlet/submissionAdmin?sf=detail&submissionID=1480801356 (DOI 10.1115/PVP2020-21053 registered)
and
https://doi.crossref.org/servlet/submissionAdmin?sf=detail&submissionID=1480801375 (10.1115/PVP2020-21051)
This resulted in two distinct cite IDs: 3651459 and 3651460 with matching titles and ISBNs.
So, these DOIs were registered against cite ID 3651459:
- 10.1115/PVP2020-21051
- 10.1115/PVP2020-21438
- 10.1115/PVP2020-21220
- 10.1115/PVP2020-21262
- 10.1115/PVP2020-21373
- 10.1115/PVP2020-21678
- 10.1115/PVP2020-21828
- 10.1115/PVP2020-21426
- 10.1115/PVP2020-21854
- 10.1115/PVP2020-21001
- 10.1115/PVP2020-21211
- 10.1115/PVP2020-21421
- 10.1115/PVP2020-21061
- 10.1115/PVP2020-21212
- 10.1115/PVP2020-21238
- 10.1115/PVP2020-21251
- 10.1115/PVP2020-21264
- 10.1115/PVP2020-21717
- 10.1115/PVP2020-21721
- 10.1115/PVP2020-21054
- 10.1115/PVP2020-21028
And, only DOI 10.1115/PVP2020-21053 was registered against cite ID 3651460.
This isn't a problem with the initial deposit, but if a member returns to register new DOIs or update existing DOIs against this title/ISBN, their subsequent submissions will all fail with an error like this:
ISBN "9780791883815" has already been assigned, title: 9780791883815/Volume 1 Codes and Standards
from submission: https://doi.crossref.org/servlet/submissionAdmin?sf=detail&submissionID=1480801428
This type of problem happens fairly often, as you can see from the examples in user_stories#287 (closed). It creates confusion for members and a good deal of toil for the support team.
There are many more examples from: user_stories#287 (closed)
NOTE: I have manually merged these two cite IDs - 3651459 and 3651460 - so the member can register content against this title/ISBN.
Observed behavior
comment: # Simultaneous deposits by members submitting non-journal content can result in duplicate title-level records.
Expected behavior
comment: # Simultaneous deposits by members submitting non-journal content do not create duplicated title-level records.
Definition of ready
-
Product owner: @SaraBowman -
Tech lead: @myalter -
Service:: label applied -
Definition of done updated -
Acceptance testing plan: deposit testing via the test system, or local demo if necessary -
Weight applied
Definition of done
-
Unit tests identified, implemented, and passing -
Code reviewed -
Knowledge base reviewed and updated -
Public documentation reviewed and updated -
Consider any impacts to current or future architecture/infrastructure, and update specifications and documentation as needed -
Acceptance criteria met -
Simultaneous deposits by members submitting non-journal content do not create as many duplicated title-level records (It is reasonable to get 99% success, the last 1% would require a lot more effort) -
Follow up with members and close Zendesk tickets: 301086
-
Notes
Simple implementation to reduce the vast majority of these issues would be to check immediately before commiting the processed deposit.