Integrated into #295 and added to the data import protocol.
Exactly 250.000 records were created to block the numbers reserved for DaSSCo. These numbers will have to be deleted to enable import. We could now delete all of them at once, but then there would be the slight risk of some of them being taken by people manually entering a catalog number within this range instead of relying on Specify to generate the catalog number.
Therefore, maybe we need some protocol to delete the dummy records that correspond to the records that are about be imported, but only those. This way we can continue to block the reserved numbers and at the same time allow for the ready records to be imported.
It should be added to the import protocol that a request is sent to one of the Specify data coordinators (via the e-mail specify@snm.ku.dk) to have the specified range of dummy records deleted. The Specify data coordinator will then perform the deletion so that the DaSSCo data manager can proceed with the import.
FedorSteeman
commented
1 year ago
Integrated into #295 and added to the data import protocol.
Exactly 250.000 records were created to block the numbers reserved for DaSSCo. These numbers will have to be deleted to enable import. We could now delete all of them at once, but then there would be the slight risk of some of them being taken by people manually entering a catalog number within this range instead of relying on Specify to generate the catalog number.
Therefore, maybe we need some protocol to delete the dummy records that correspond to the records that are about be imported, but only those. This way we can continue to block the reserved numbers and at the same time allow for the ready records to be imported.
It should be added to the import protocol that a request is sent to one of the Specify data coordinators (via the e-mail specify@snm.ku.dk) to have the specified range of dummy records deleted. The Specify data coordinator will then perform the deletion so that the DaSSCo data manager can proceed with the import.