<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<pre><span style="color:black">Thanks for the feedback all and some potential workarounds. I agree that none are truly sustainable, though, in a production environment. Workflow management functionality for this would be awesome! Fingers crossed that makes it into development sometime down the line. <o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Best,<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Eric Milenkiewicz<o:p></o:p></span></pre>
<pre><span style="color:black">Manuscripts Curator<o:p></o:p></span></pre>
<pre><span style="color:black">Special Collections & University Archives<o:p></o:p></span></pre>
<pre><span style="color:black">UCR Library<o:p></o:p></span></pre>
<pre><span style="color:black">951-827-4942<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">My number one #ASpacePipeDream is for there to be some sort of workflow management functionality built-in.<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">- Data entry user marks whoopsie item for deletion<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">- Repo manager is notifed<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">- Repo manager chooses to allow deletion or send back for review<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">- Repo manager actually deletes<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">I say this as someone who once had a truly awesome, talented employee (at a former gig) accidentally delete an entire resource record. (Though, this fix has made that far less likely <a href="https://archivesspace.atlassian.net/browse/AR-1313">https://archivesspace.atlassian.net/browse/AR-1313</a>)<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Lora<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Lora J. Davis<o:p></o:p></span></pre>
<pre><span style="color:black">Digital Archivist<o:p></o:p></span></pre>
<pre><span style="color:black">The Sheridan Libraries<o:p></o:p></span></pre>
<pre><span style="color:black">Johns Hopkins University<o:p></o:p></span></pre>
<pre><span style="color:black">3400 North Charles Street<o:p></o:p></span></pre>
<pre><span style="color:black">Baltimore, MD 21228<o:p></o:p></span></pre>
<pre><span style="color:black">(410) 516-5898<o:p></o:p></span></pre>
<pre><span style="color:black"><a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group">ljdavis at jhu.edu</a><o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">From: <a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group">archivesspace_users_group-bounces at lyralists.lyrasis.org</a> [mailto:<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group">archivesspace_users_group-bounces at lyralists.lyrasis.org</a>] On Behalf Of Majewski, Steven Dennis (sdm7g)<o:p></o:p></span></pre>
<pre><span style="color:black">Sent: Tuesday, March 07, 2017 4:10 PM<o:p></o:p></span></pre>
<pre><span style="color:black">To: Archivesspace Users Group <<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group">archivesspace_users_group at lyralists.lyrasis.org</a>><o:p></o:p></span></pre>
<pre><span style="color:black">Subject: Re: [Archivesspace_Users_Group] Processors ability to delete?<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">We’ve also run into this where people can create a resource, but can’t delete it if they make a mistake and want to start over, or just want to create a test object when learning. But in general, I think it’s a good idea to make deleting a record more privileged. Maybe a useful feature would be to make the permission behavior dependent on resource status - perhaps make only published items require elevated permission to delete, or else make a exception for “draft” status or some other value.<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">On Mar 7, 2017, at 3:58 PM, Lisa Calahan <<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group">lcalahan at umn.edu</a><mailto:<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group">lcalahan at umn.edu</a>>> wrote:<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Hi Eric,<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">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."<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">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.<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Best,<o:p></o:p></span></pre>
<pre><span style="color:black">Lisa<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">On Tue, Mar 7, 2017 at 2:35 PM, Eric Milenkiewicz <<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group">eric.milenkiewicz at ucr.edu</a><mailto:<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group">eric.milenkiewicz at ucr.edu</a>>> wrote:<o:p></o:p></span></pre>
<pre><span style="color:black">Hi All,<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">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.<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">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).<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Has anyone else run into this type of permissions issue? And if so, have you identified any workarounds?<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Thanks,<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Eric Milenkiewicz<o:p></o:p></span></pre>
<pre><span style="color:black">Manuscripts Curator<o:p></o:p></span></pre>
<pre><span style="color:black">Special Collections & University Archives<o:p></o:p></span></pre>
<pre><span style="color:black">UCR Library<o:p></o:p></span></pre>
<pre><span style="color:black">951-827-4942<o:p></o:p></span></pre>
</div>
</body>
</html>