Allow to delete records in Primo BE ( included dedup records )
Right now the only way to delete a record in Primo is to refer to a KB Article [1] explaining how to write an xml OAI-PMH record with status 'deleted' and let the xml file to be ingested by a pipe. The procedure is cumbersome and error prone (e.g. issues with compression of the file on non linux machines etc.) and it does not always work properly. For example, dedup records are not properly deleted by this procedure.
It would be good to provide a feature in the Primo BE allowing to look for specific PNX and to delete it. This should work with both plain records and dedup records.
Luigi Siciliano
shared this idea
-
Katharina Wolkwitz
commented
The How-to-Article also specifically targets only libraries "Relevant for Installation Type: Local" - so all other Libraries need an alternative way to delete destinct single records which have no corresponding source record in the Library-System.
We've got the problem that our SandBox has a lot of "orphaned" records from deleted Aleph-records that stayed in the SandBox because there is no OnGoing-Publishing set-up between Aleph and the SandBox.
At the moment we're using Primo Back-Office in combination with Aleph. We're starting our migration to Alma/PrimoVE-project in June though, so from the end of 2022 onwards we're going to need the feature for PrimoVE...
-
Ian Mirfin
commented
This is a great Idea, there really needs to be a way for an administrator to remove a record from the primo database manually.
We use an OAI for publishing & removing items from Primo, however we still have users that are over keen to delete records in the source system prior to the remove pipe running. Which means its a nightmare to recreate the records to run the delete pipe.
I cant see why its so hard to add this feature, we can search and review a PNX vs source record using the primary key, why cant we delete a record a similar way.
-
Stacey van Groll
commented
I believe this is technically possible by a different manner of running a Delete and Reload pipe. This can now be scheduled with NERS delivery of '6184: Make it possible to override Start Harvest date for Delete and ReLoad pipes' in May 2020. I run this process monthly, which seems sufficient for our 3 OAI data sources.