[Archivesspace_Users_Group] Processors ability to delete?

Lisa Calahan lcalahan at umn.edu
Tue Mar 7 15:58:34 EST 2017

Hi Eric,

We have also run into this issue. It would be a great feature if the
deletion of component records could be a separate permission from the
"delete all major record types in this repository."

We have a couple of workarounds that we've used, none of which are really
sustainable. 1) A student/staff person will report when they need a
component record deleted and a staff person with that permission will
delete the record for them (usually happens when a component record was
accidentally duplicated) and a supervisor is sitting close by. 2) The
repository manager or ASpace administrator will temporarily give the
permission group "delete the major record types of this repository"
permission to be able to delete; which is paired with a stern talking to
about being careful to not delete a resource record. 3) Move
multiple/various component records that need to be deleted into a "To
delete" grouping/fake series at the end of the resource record to have a
supervisor delete as one of the final review tasks.


On Tue, Mar 7, 2017 at 2:35 PM, Eric Milenkiewicz <eric.milenkiewicz at ucr.edu
> wrote:

> Hi All,
> We have recently hired/trained student employees on processing archival
> collections in ASpace, however we cannot seem to find a way of fine tuning
> the user permission groups to provide them with an appropriate level of
> access.
> For example, the advanced/basic data entry staff and archivist levels do
> not allow permissions for resource component records to be deleted (which
> is often times needed while processing, as things change). This level of
> access is not achieved until the repository/project manager level which
> provides much greater permissions. Configuring the User Permission Groups
> also has not helped here since once the “delete the major record types in
> this repository” option is checked then entire Resource and Accession
> records can be deleted (a function we want to restrict to higher level
> staff).
> Has anyone else run into this type of permissions issue? And if so, have
> you identified any workarounds?
> Thanks,
> Eric Milenkiewicz
> Manuscripts Curator
> Special Collections & University Archives
> UCR Library
> 951-827-4942 <(951)%20827-4942>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


Head of Archival Processing

University of Minnesota Libraries
Archives and Special Collections
Elmer L. Andersen Library, Suite 315
222-21st Ave. S.
Minneapolis MN 55455

Phone: 612.626.2531
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170307/732a26bf/attachment.html>

More information about the Archivesspace_Users_Group mailing list