<div dir="ltr">Hi Eric,<div><br></div><div>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." </div><div><br></div><div>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.</div><div><br></div><div>Best,</div><div>Lisa</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 7, 2017 at 2:35 PM, Eric Milenkiewicz <span dir="ltr"><<a href="mailto:eric.milenkiewicz@ucr.edu" target="_blank">eric.milenkiewicz@ucr.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="m_635721108885844299WordSection1">
<p class="MsoNormal">Hi All,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">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.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">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).<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Has anyone else run into this type of permissions issue? And if so, have you identified any workarounds?
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Thanks,<u></u><u></u></p>
<p class="MsoNormal"><br>
Eric Milenkiewicz<u></u><u></u></p>
<p class="MsoNormal">Manuscripts Curator<u></u><u></u></p>
<p class="MsoNormal">Special Collections & University Archives<u></u><u></u></p>
<p class="MsoNormal">UCR Library<u></u><u></u></p>
<p class="MsoNormal"><a href="tel:(951)%20827-4942" value="+19518274942" target="_blank">951-827-4942</a><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<br>______________________________<wbr>_________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><br>Head of Archival Processing<br><br>University of Minnesota Libraries<br>Archives and Special Collections<br>Elmer L. Andersen Library, Suite 315<br>222-21st Ave. S.<br>Minneapolis MN 55455<br><br>Phone: <a value="+16126248812" style="color:rgb(17,85,204)">612.626.2531</a><br></div></div></div></div>
</div>