[Archivesspace_Users_Group] Feature request re: deleted items - thoughts?

Kevin Clair Kevin.Clair at du.edu
Thu May 7 17:05:22 EDT 2015


I had been meaning to ask similar questions to the list about suppressed resources and archival objects. I’ve been experimenting with that a little bit on our development servers (in part to prevent this from happening, by having staff think to suppress first), but I’m not sure what happens to those records once I suppress them. Some of what’s in this message would apply there, I think.

thanks!  -k

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Lora Davis
Sent: Thursday, May 07, 2015 2:27 PM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Feature request re: deleted items - thoughts?


Posting here in the hopes of getting thoughts/feedback before submitting as a potential feature request through JIRA.

For the second time now, an otherwise well-meaning, highly trained professional staffer at our institution has accidentally deleted a resource record.  I have a few thoughts as to why this keeps happening, and at least one feature request is already in JIRA to address them.  Namely:

1. When an archival component is deleted from a resource record, the resource record "refreshes" and places the user back at the top/collection level of the record.  Thus, a user (Repository Manager/Project Manager/Advanced Data Entry) deleting multiple archival components from a resource may find themselves in a "groove" wherein they keep scrolling from the top collection, down to the archival object to be deleted, selecting the archival object, hitting "delete," and rinsing and repeating the above.  Twice now we've had users not realize they were still at the RESOURCE level (not object level) when they hit delete and, therefore, bye bye resource.

2. The popup that confirms deletion is truly intended doesn't highlight what content is actually being deleted (archival component, resource, etc.)?

Both of the above would be addressed by implementing feature request AR-1132<https://archivesspace.atlassian.net/browse/AR-1132>.

However, I'm also wondering about the feasibility of a feature that would park "deleted" items (resources, objects, etc.) in a staging area before they are well and truly removed permanently from the db.  The idea initially came when I first contacted Lyrasis (we're hosted) to see about data recovery after our first improper deletion.  Mark Cooper wrote back:

I can also make a feature request to ArchivesSpace to put deleted items into a "staging" state, where they are actually deleted (removed from the database) when purged via the interface or through a background job.

This could be a good model (especially as background jobs get built out more).  In our particular institutional setting (and perhaps for others), it would be ideal if the purge could only be instituted as a background job by the System Administrator, but, perhaps for others, you may want it to just be done as a regular cron job or something without user input.



Lora J. Davis
Collections Archivist
Colgate University Libraries
13 Oak Drive
Hamilton, NY 13346
Tel:  (315) 228-6376
Fax: (315) 228-7934
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150507/a6127202/attachment.html>

More information about the Archivesspace_Users_Group mailing list