The deletion of an AIP and the re-ingest of a new one (in 1.4.1) is an easy enough task; however, I have a few questions about the proper/best way to do so (with regards to what we are trying to do at my institution).
Situation: 1) currently store DIPs, 2) daily auto-sync AIPsStore to DuraCloud space, 3) need to replace 50 AIPs (processing configuration included "Examine contents") with 50 AIPs of identical content but minus the hundreds of bulk-extracted TXT files in the /data/logs directory
Questions:
1. When I delete an AIP, it is retained in the AIPsStore for possible recovery. But if I want to eliminate it entirely from the archival storage (and database) so that it does not get continually synced to DuraCloud, how might I do that -- other than going in the backend and manually eliminating the packages? And what other issues could that cause?
2. What is the best way to deal with the 50 stored DIPs corresponding to the AIPs that I intend to eliminate? Is there a way to delete them entirely too? And if I leave them (since they will contain the same content) and forego the creation of DIPs at re-ingest, what problems might I encounter when I eventually move them to a DAMS (will have same content and titles, but of course different UUIDs) if and when we integrate systems?
Anyway, any insights, suggestions, guidance, or instructions would be greatly appreciated. I feel that I could come up with a roundabout way to accomplish what we need to do, but am hoping someone might be able to provide me with a better, more succinct method or solution to resolving my problem. Thanks.
Sean Buckner
Digital Preservation Librarian
Texas A&M University Libraries