Suppress Component because Submitted by Mistake or Is Duplicate
This was first discussed in issue #118 (closed) - but I am also creating it as a feature request of what we need to support for deployment based on testing, migration, and usability issues
Context
It is possible for submitters to create a component by mistake or that is a duplicate to the record already existing in the BCMS / Bookshelf. We need to be able to delete these cases from the BCMS to prevent users from updating and publishing the wrong record and to avoid data itegrity issues in the archive with duplicates.
Proposal
See:
Design
See above
Scoping outcome
Full Record of scoping a BCMS Miro board
BCMS System admins need to know about duplicate records and prevent users from updating and publishing the wrong record to avoid data integrity issues in the Bookshelf archive
Here is a high-res version the image from Miro with the flow we discussed
After the first session this was updated to the following:
In summary: Check specified metadata values in the converted xml to find potential duplicate records. Report duplicates in a new status 'Bookshelf Editorial Review' for NCBI system admins to resolve, by overriding the check, locking the content or suppressing the content, prior to sending the files to NCBI systems at load to PMC step.
Note that there is corresponding development on NCBI-side to update the Domain Service which is not included in Coko's estimate.
Implementation (if applicable)
Open issues (if applicable)
See #118 (closed)