<div dir="ltr"><div>UCSC Special Collections & Archives also supports AS-76. We are experiencing a scenario similar to Harvard's.<br><br></div><br><div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><span><font color="#888888"><div>Kate Dundon<br>Archivist, Special Collections & Archives<br></div><div>University Library<br></div><div>University of California, Santa Cruz<br>831-502-7587<br><br></div></font></span></div></div></div></div></div>
<br><div class="gmail_quote">On Tue, Feb 9, 2016 at 3:41 PM, Cyndi Shein <span dir="ltr"><<a href="mailto:cyndi.shein@unlv.edu" target="_blank">cyndi.shein@unlv.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div style="font-family:tahoma,sans-serif">UNLV University Libraries supports AS-76 as well.<br></div></div><div class="gmail_extra"><br clear="all"><div><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>Cyndi Shein </div><div><font size="1">Head, Special Collections Technical Services</font></div><div><font size="1">University Libraries, University of Nevada, Las Vegas</font></div><div><font size="1"><a href="mailto:cyndi.shein@unlv.edu" target="_blank">cyndi.shein@unlv.edu</a> <a href="tel:%28702%29%20895-2223" value="+17028952223" target="_blank">(702) 895-2223</a></font></div><div><br></div><div><img src="https://docs.google.com/uc?export=download&id=0B2OzX83HDLhZQXF0eTVaRk1DNXM&revid=0B2OzX83HDLhZY1RYOS8xZVk5MGhYdTBlY1NlbUNFaUpYQm84PQ" style="color:rgb(0,0,0);font-size:12.8px"><font style="color:rgb(0,0,0);font-size:12.8px" face="arial narrow, sans-serif"><span style="font-size:12.8px"> </span><a href="https://www.facebook.com/unlvspecialcollections" style="color:rgb(17,85,204);font-size:12.8px" target="_blank">unlvspecialcollections</a></font><br></div><div><img src="cid:_2_0B1D23800B1B25800073DD1F88257D66" height="65" width="96"><br></div></div></div></div></div></div></div></div></div></div></div></div></div></div><div><div class="h5">
<br><div class="gmail_quote">On Tue, Feb 9, 2016 at 10:02 AM, Dougherty, Laurel <span dir="ltr"><<a href="mailto:l1dougherty@ucsd.edu" target="_blank">l1dougherty@ucsd.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">UC San Diego concurs. The experience (and resulting complications with managing data effectively) that Anne describes below are identical to UC San Diego’s, and
we too support AS-76.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Laurel McPhee Dougherty<u></u><u></u></span></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Supervisory Archivist, Special Collections & Archives Program<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">UC San Diego Library |
</span><span style="font-size:10.0pt;font-family:Wingdings;color:#1f497d">(</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:#1f497d">
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><a href="tel:858-534-5619" value="+18585345619" target="_blank">858-534-5619</a> |</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:#1f497d">
</span><span style="font-size:10.0pt;font-family:Wingdings;color:#1f497d">*</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif;color:#1f497d">
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#2e74b5"><a href="mailto:l1dougherty@ucsd.edu" target="_blank"><span style="color:#2e74b5">l1dougherty@ucsd.edu</span></a></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">archivesspace_users_group-bounces@lyralists.lyrasis.org</a> [mailto:<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>]
<b>On Behalf Of </b>Engelhart, Anne<br>
<b>Sent:</b> Tuesday, February 09, 2016 8:58 AM<br>
<b>To:</b> Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" target="_blank">archivesspace_users_group@lyralists.lyrasis.org</a>><br>
<b>Cc:</b> Sniffin-Marinoff, Megan <<a href="mailto:megan_sniffin-marinoff@harvard.edu" target="_blank">megan_sniffin-marinoff@harvard.edu</a>><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Collection management - processing status disappeared...<u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">I’ve been asked by the Harvard ArchivesSpace Interim Steering Group to post Harvard University’s position on AS-76. I also posted it on JIRA, AS-76. (Here it
is below.) <u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Anne Engelhart<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Head, Collection Services<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Schlesinger Library, Radcliffe Institute<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">10 Garden St.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Cambridge, MA 02138<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"><a href="tel:617.495.8521" value="+16174958521" target="_blank">617.495.8521</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><b>Restoration of processing status to collection management records in ArchivesSpace<u></u><u></u></b></p>
<p class="MsoNormal"><b>Summary </b><b><span style="font-size:11.0pt"><u></u><u></u></span></b></p>
<p class="MsoNormal"><span style="color:black">Sometime during the past year, ArchivesSpace made a major change to its functionality.<u></u><u></u></span></p>
<p style="line-height:normal">
<u></u><span style="font-family:Symbol;color:black"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="color:black">It eliminated the processing status from collection management records.<u></u><u></u></span></p>
<p style="line-height:normal">
<u></u><span style="font-family:Symbol;color:black"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="color:black">The processing status and associated date were converted to “event” records.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black">This has created several problems for archivists at Harvard who rely on this information for workflow and reporting purposes including:<u></u><u></u></span></p>
<p style="margin-left:38.25pt;line-height:normal">
<u></u><span style="font-family:Symbol;color:black"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="color:black">The “processing status” in all accessions migrated from the Archivists’ Toolkit (AT) for which processing statuses were assigned now displays as “Not specified” (see Screenshot 1).<u></u><u></u></span></p>
<p style="margin-left:38.25pt;line-height:normal">
<u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="color:black">The conversion of processing status from a condition (or type) to an event overcomplicates what was previously a fairly straightforward piece of collection management information.</span><u></u><u></u></p>
<p class="MsoNormal"><b>Detailed discussion of issues<u></u><u></u></b></p>
<p class="MsoNormal">There are three troubling issues associated with this change in functionality.
<u></u><u></u></p>
<p style="line-height:normal">
<u></u><span>1.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>The first should be important to all archives: <span style="color:black">
by converting the processing status to an event, the A</span>rchives<span style="color:black">Space developers have changed the nature of the data. A status is not equivalent to an event, although they can be related.
</span>There is one and only one “status” at any one time, but there can be multiple events. Events can lead to status changes. For example<span style="color:black">,</span> two “partially processed” events may or may not lead to a status of “processed,” because
it is entirely possible that three or more processing events might be needed to conclude that the status of the collection is “processed.” In addition, some statuses may have no relation to an event. For example “Unknown” is a possible processing status.
Finally, how does an archivist identify “unprocessed” accessions in this scenario? This is another “non-event”. Are ArchivesSpace users expected to run a report on all accessions and look for those for which there is no “processing” event? Since there are
many possible event types, this seems counter-productive and unnecessarily complex.<u></u><u></u></p>
<p style="line-height:normal"><u></u> <u></u></p>
<p style="line-height:normal">
<u></u><span>2.<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>The second issue is perhaps unique to Harvard albeit no less critical. The Harvard AT-to-AS migration did not create event records based on processing status. Instead, while our back-end data has processing status in it, these statuses
are, troublingly, not visible to staff. Instead <span style="color:black">the processing status displays as
</span>“not specified” (Screenshot 1). The same record in AT displays a processing status. (Screenshot 2)<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
<p class="MsoNormal" style="margin-left:.5in"><b>Screenshot 1<u></u><u></u></b></p>
<p class="MsoNormal" style="margin-left:.5in"><img src="cid:image001.png@01D16320.CE4FE1E0" height="155" border="0" width="435"><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in"><b>Screenshot 2<u></u><u></u></b></p>
<p class="MsoNormal" style="margin-left:.5in"><img src="cid:image002.png@01D16320.CE4FE1E0" height="148" border="0" width="469"><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
<p><u></u><span style="color:black"><span>3.<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="color:black">Processing status is a critical piece of information that should be available to archivists for reporting on their accessions. In Harvard's current ArchivesSpace environment is that it is not possible
to understand the scope and nature of our backlogs. The staff member who discovered this issue previously used the AT to readily determine the number of unprocessed accessions. While attempting to gather the same information from ArchivesSpace, the staff
member found that it was not possible to achieve the same results with existing ArchivesSpace functionality.
<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:31.5pt"><u></u> <u></u></p>
<p class="MsoNormal">It is essential to the Harvard University ArchivesSpace user community that processing status be restored to its original functionality. The restoration of processing status to collection management records would:<u></u><u></u></p>
<p style="line-height:normal">
<u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u>Allow archivists to report out on backlog and processing statistics;
<u></u><u></u></p>
<p style="line-height:normal">
<u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u>Assist archivists in resource allocation planning for grant proposals and yearly projects; and<u></u><u></u></p>
<p style="line-height:normal">
<u></u><span style="font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u>Make this data currently in the back-end of ArchivesSpace easily available to archivists<u></u><u></u></p>
<p class="MsoNormal">As such, Harvard University ArchivesSpace user community supports the JIRA ticket (AS-76) submitted by Matt Francis of Penn State Libraries.
<u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p>
<div>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">
<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">archivesspace_users_group-bounces@lyralists.lyrasis.org</a> [<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</a>]
<b>On Behalf Of </b>MATTHEW R FRANCIS<br>
<b>Sent:</b> Monday, January 04, 2016 12:56 PM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Collection management - processing status disappeared...<u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Quick FYI update for anyone interested in this thread. After a couple of off-list discussions I decided to go ahead an create a new "feature request" ticket in JIRA
requesting that the "Processing Status" field be restored to the Collection Management sub-record. The ticket can be viewed at:
<a href="https://archivesspace.atlassian.net/browse/AS-76" target="_blank">https://archivesspace.atlassian.net/browse/AS-76</a> (my apologies for forgetting to submit in the form of a user story!).<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">If there are any questions, concerns, or clarifications that I can help with related to the request please let me know.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">-Matt<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><u></u> <u></u></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Arial",sans-serif;color:black">Matt</span></b><b><span style="font-family:"Georgia",serif;color:black"> Francis</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:black">Archivist for Collection Management</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:black">Special Collections Library<br>
Penn State University</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><u></u><u></u></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><u></u> <u></u></span></p>
</div>
<div class="MsoNormal" style="text-align:center" align="center"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">
<hr align="center" size="2" width="100%">
</span></div>
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">From:
</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">"MATTHEW R FRANCIS" <<a href="mailto:mrf22@psu.edu" target="_blank">mrf22@psu.edu</a>><br>
<b>To: </b>"Archivesspace Users Group" <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" target="_blank">archivesspace_users_group@lyralists.lyrasis.org</a>><br>
<b>Sent: </b>Wednesday, November 25, 2015 4:50:24 PM<br>
<b>Subject: </b>Re: [Archivesspace_Users_Group] Collection management - processing status disappeared...<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><u></u> <u></u></span></p>
</div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Thank you Brad for your explanation for why the change occurred with the processing status field, and thank you Kate, Noah, and Carolyn for your additional thoughts
and feedback.<u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><u></u> <u></u></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Based on all of the provided feedback I asked some of our staff to work/test the new functionality while trying to consider the intent behind the changes, our existing
local workflows and collections metadata, and the abstract "what do we consider processing status to mean". Based on this examination of the new functionality we would like to provide the following feedback (many of which have already been stated in this email
thread):<u></u><u></u></span></p>
</div>
<ul type="disc">
<li class="MsoNormal" style="color:black">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">In regards to "an event record allows much more information to be associated with the event", it has been our local practice and belief that more nuanced processing information that would help researchers
and staff better understand a finding aid/the physical collection should be recorded in a corresponding "Processing Information" note (which is informed by our interpretation of DACS 7.1.8). That said, we do appreciate that the event record allows for the
capturing of some metadata that would be less relevant to researchers, and consequently a place where additional metadata could be recorded outside of the aforementioned note field.<u></u><u></u></span></li><li class="MsoNormal" style="color:black">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">After examining our "processing status" data and discussing the new functionality, we agree with Kate's observation that "events and processing statuses are not logical equivalents." Additionally,
we also agree with Noah's comment "that a resource or accession will always have only one current status."
<u></u><u></u></span></li><li class="MsoNormal" style="color:black">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Additionally, based on our examination, we do not believe that is ideal or logical to separate "processing status" from collection management records that still include: "processing priority", "processing
plan", and "processors". <u></u><u></u></span></li><li class="MsoNormal" style="color:black">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Our local workflows appear to be at a high level similar to what Carolyn has reported, and along with the data we had already created to take advantage of the previous functionality, we also preferred
the simplicity of the processing status being a simple drop-down selection in the collection management records.<u></u><u></u></span></li><li class="MsoNormal" style="color:black">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Based on our local use the processing status field, along with the current status of the ASpace tool, we found it much easier to report on collection status and to locate appropriate collections
projects for our workers with the previous functionality over the current.<u></u><u></u></span></li><li class="MsoNormal" style="color:black">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Finally, we also echo Kate's sentiment in that we do not understand why the new event features requires the removal of the processing status from the collection management records and consequently
wonder if there is any reason not to have both?<u></u><u></u></span></li></ul>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Due to the above points we are of the opinion that if the new event features cannot be appropriately maintained while also having the processing status functionality
reside in the collection management records, we would be in favor of a return to the previous functionality, or a new approach that is more similar to the previous functionality. With that said, we understand that our rationale for this request is largely
based on our local understanding of the role of the processing status field, our local workflows, and and our existing data. Because of this we recognize that not all ASpace members might share our perspective, and consequently we welcome continued discussion
on this subject as appropriate.<u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><u></u> <u></u></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Thank you again to everyone who have already participated in the conversation, and we hope that as a community we can reach a consensus on the best direction for
us to proceed in the near future.<u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><u></u> <u></u></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Hope all of you have a wonderful Thanksgiving.<u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><u></u> <u></u></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">-Matt<u></u><u></u></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><u></u> <u></u></span></p>
<div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Arial",sans-serif;color:black">Matt</span></b><b><span style="font-family:"Georgia",serif;color:black"> Francis</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:black">Archivist for Collection Management</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:black">Special Collections Library<br>
Penn State University</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><u></u> <u></u></span></p>
<div class="MsoNormal" style="text-align:center" align="center"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">
<hr align="center" size="2" width="100%">
</span></div>
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">From:
</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">"Runyon, Carolyn" <<a href="mailto:Carolyn-Runyon@utc.edu" target="_blank">Carolyn-Runyon@utc.edu</a>><br>
<b>To: </b>"Archivesspace Users Group" <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" target="_blank">archivesspace_users_group@lyralists.lyrasis.org</a>><br>
<b>Sent: </b>Tuesday, November 24, 2015 2:12:09 PM<br>
<b>Subject: </b>Re: [Archivesspace_Users_Group] Collection management - processing status disappeared...<u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><u></u> <u></u></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">We used the Processing Status field in the Collection Management module to track processing of our all our Resource records. It’s a little less complex than the data
needed to populate an Event. I preferred the basic dropdown menu offered in Collection Management because it doesn’t require and Event Date/Time or a link it to an Agent. With legacy data, I won’t able to link an accurate Agent or Date to my processing events,
which means I’ll have to devise some sort of input workaround for undated and anonymous Events.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">One last note, when Processing Status became and Event, Event Date/Time and Agent Links were populated, but they’re not accurate. They appear to reflect the Agent
who selected the Processing Status and the Timestamp of when the Agent made the Processing Status selection. This means that if I want accurate data, I’ll need to clean up this legacy data.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Cheers,<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Carolyn<u></u><u></u></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><u></u> <u></u></span></p>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Carolyn Runyon<br>
Assistant Head of Collection Services and Director of Special Collections<br>
University of Tennessee at Chattanooga Library<br>
615 McCallie Ave., Chattanooga, TN 37403<br>
<a href="mailto:Carolyn-Runyon@utc.edu" target="_blank">Carolyn-Runyon@utc.edu</a>, <a href="tel:%28423%29%20425-4503" value="+14234254503" target="_blank">(423) 425-4503</a><br>
Dept. 6456, LIB 439D<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><u></u> <u></u></span></p>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">On Nov 19, 2015, at 9:57 AM, Noah Huffman <<a href="mailto:noah.huffman@duke.edu" target="_blank">noah.huffman@duke.edu</a>> wrote:<u></u><u></u></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">I tend to agree with Kate here. It seems useful to allow a resource or accession to have lots of processing events associated with it (who did what, when), but
it also seems that a resource or accession will always have only one current status (processed, not processed, partially processed, etc.).</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Also, associated events do not display in “edit” mode for resources or accessions (collection management sub-records do). As a result, it’s a bit complicated
to figure out what the processing status is if you have to sort through a long list of associated events in “view” mode.</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">-Noah</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:</span></b><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>
[<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</a>]<span> </span><b>On Behalf Of<span> </span></b>Bowers,
Kate A.<br>
<b>Sent:</b><span> </span>Thursday, November 19, 2015 9:40 AM<br>
<b>To:</b><span> </span>Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" target="_blank">archivesspace_users_group@lyralists.lyrasis.org</a>><br>
<b>Subject:</b><span> </span>Re: [Archivesspace_Users_Group] Collection management - processing status disappeared...</span><span style="color:black"><u></u><u></u></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="color:black"><br>
Brad,<br>
<br>
Thanks for your very thorough reply!<br>
<br>
I think you presented this as an either/or choice. However, because events and processing status are not logical equivalents (they may be associated in that the status may be the result of an event, but it does not have to be), I do not understand why adding
features to the events record requires removal of the status. I short, is there any reason not to have both?<br>
<br>
Thanks again,<br>
<br>
Kate<br>
<br>
Kate Bowers<br>
Collections Services Archivist for Metadata, Systems, and Standards<br>
Harvard University Archives<br>
Cambridge, Massachusetts, USA<br>
voice: <a href="tel:%28617%29%20384-7787" value="+16173847787" target="_blank">(617) 384-7787</a><br>
fax: <a href="tel:%28617%29%20495-8011" value="+16174958011" target="_blank">(617) 495-8011</a><br>
<a href="mailto:kate_bowers@harvard.edu" target="_blank"><span style="color:purple">kate_bowers@harvard.edu</span></a><u></u><u></u></span></p>
<div class="MsoNormal" style="text-align:center" align="center"><span style="color:black">
<hr align="center" size="2" width="98%">
</span></div>
<div>
<div>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:</span></b><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank"><span style="color:purple">archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a><span> </span><<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank"><span style="color:purple">archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a>>
on behalf of Brad Westbrook <<a href="mailto:brad.westbrook@lyrasis.org" target="_blank"><span style="color:purple">brad.westbrook@lyrasis.org</span></a>><br>
<b>Sent:</b><span> </span>Wednesday, November 18, 2015 6:04:27 PM<br>
<b>To:</b><span> </span>Archivesspace Users Group<br>
<b>Subject:</b><span> </span>Re: [Archivesspace_Users_Group] Collection management - processing status disappeared...</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Hi.</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Certainly it is possible and reasonable to have a discussion of how to adjust this change in functionality to make it more satisfying and less confusing, including
reverting back to the functionality first included in ArchivesSpace. <span> </span></span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">As I recall that functionality, it consisted of the ability to link a single collection management record to a material description record (accession, resource,
or digital object but not components for resources and digital objects) and, further, to indicate in that collection management record the processing status of the material being described. Default terms were “completed”, “in_progress”, and “new”, but the
controlled value list was completely configurable. So institutions could add any terms they wanted to that list but they could only ever apply one status term to the material being described at a given time. </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">We removed this field from the collection management field with the understanding such data would be better handled as event information and with the understanding
that a change in status is first an event accomplished at a time and by an agent. We envisioned several benefits to this change: </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div style="margin-left:.5in">
<p class="MsoNormal"><span style="color:black">1)</span><span style="font-size:7.0pt;color:black"> <span> </span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">As
before, an organization has complete liberty to decide what terms it wants to use for expressing processing events and changes in processing status, as well as for any other events an institution chooses to track. The “Event Event Type” list is completely
configurable. </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div style="margin-left:.5in">
<p class="MsoNormal"><span style="color:black">2)</span><span style="font-size:7.0pt;color:black"> <span> </span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">An
event record allows much more information to be associated with the event, including a descriptive note about the event, when the event occurred, and who was responsible for the event. It struck us that knowing that processing of a collection was completed
on a certain date and by a certain individual could be more useful information that know processing was simply completed. </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div style="margin-left:.5in">
<p class="MsoNormal"><span style="color:black">3)</span><span style="font-size:7.0pt;color:black"> <span> </span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Multiple
event records can be associated to the same material description record. For instance, using event records it would be possible to indicate when processing of material started in one event record and when it was completed in another. </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div style="margin-left:.5in">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div style="margin-left:.5in">
<p class="MsoNormal"><span style="color:black">4)</span><span style="font-size:7.0pt;color:black"> <span> </span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Multiple
event records can be linked to component records. Thus for processing projects split into parallel parts, it would be possible to track, say, the processing progress of series. <span> </span></span><span style="color:black"><u></u><u></u></span></p>
</div>
<div style="margin-left:.5in">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">In short, our belief is that the collection management record in conjunction with event records provides a more comprehensive and flexible way for organizations
to record collection management information. In that relationship, the collection management record is the location for planning—indicating processing priority, estimating processing time, indicating processing plan(s) and processor(s), but also noting funding
source and whether rights are determined (it’s questionable whether or not these last two should be included in the collection management record)—while the event record is for recording completion (or not) of processing / administrative tasks associated with
the materials—acquiring a purchase agreement, starting processing, completing processing, etc.</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">There are requisites for this, of course:</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div style="margin-left:.5in">
<p class="MsoNormal"><span style="color:black">1)</span><span style="font-size:7.0pt;color:black"> <span> </span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Institutional
policies regarding what events are to be tracked and what event vocabulary is to be used. </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div style="margin-left:.5in">
<p class="MsoNormal"><span style="color:black">2)</span><span style="font-size:7.0pt;color:black"> <span> </span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">A
process for creating and sharing reports that relate material descriptions, collection management, and events in meaningful ways. A segment of the ArchivesSpace community has been working to develop a reporting process, but the trajectory being taken will
place the burden on institutions to define reports (You can, btw, see a record of this effort at<span> </span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_wiki_display_AC_2015-2D16-26-2343-3BReports&d=CwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=pyfDl0NLRM2Jvhgo4nw49RzEuLIWLzobJtqOMHw8wZY&s=8UVzAZgZUYCTKzwFwtZ-ItCHeuR_vGn6ZXiJbokIYsc&e=" target="_blank"><span style="color:purple">https://archivesspace.atlassian.net/wiki/display/AC/2015-16+Reports</span></a><span> </span>(current
work) and<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_wiki_display_AC_Reports-26-2343-3BSub-2Dteam&d=CwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=pyfDl0NLRM2Jvhgo4nw49RzEuLIWLzobJtqOMHw8wZY&s=gR2KAeUPGvIhxYIWoXd34WpOx_Fv8C2o6k7-biJ_1S0&e=" target="_blank"><span style="color:purple">https://archivesspace.atlassian.net/wiki/display/AC/Reports+Sub-team</span></a><span> </span>(past
work). It was also noted in the ArchivesSpace developers meeting last week, that information of this type would be very suitable for displaying in a dashboard widget. Of course, institutions can already build their own reporting and define their own reports
by using report software to extract and format data from the ArchivesSpace MySQL database.</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div style="margin-left:.5in">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">But these would be requisites for any collection management information, supplemented or not by event information. They would be requisites for a reversion for
a return to the previous data model.</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Let me close with two observations to other parts of this thread:</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div style="margin-left:.5in">
<p class="MsoNormal" style="line-height:15.0pt;background:white">
<span style="color:black">1)</span><span style="font-size:7.0pt;color:black"> <span> </span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">The display problem that Noah noted in his comment
yesterday is a remnant of moving collection status to events. There is a bug report requesting its correction at<span> </span></span><span style="font-size:10.5pt;font-family:"Arial",sans-serif;color:#333333"><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_AR-2D1324&d=CwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=pyfDl0NLRM2Jvhgo4nw49RzEuLIWLzobJtqOMHw8wZY&s=_4rsWhuS5vR89lgPot1DeY3XwBuDLb5wp_nbHwCIMZI&e=" target="_blank"><span style="color:#3b73af">AR-1324</span></a>.</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div style="margin-left:.5in">
<p class="MsoNormal"><span style="color:black">2)</span><span style="font-size:7.0pt;color:black"> <span> </span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">The
presence of the “Collection Management Processing Status” in the list of controlled values is also remnant of that change. It should be removed , unless there is a collective decision to revert. Thanks for pointing that out, Kelly.</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div style="margin-left:.5in">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">So it would be great to hear others weigh in on this. Collection management and event information have, as far as I know, no prevailing models or standards that
we can simply follow. The closest to such is the de facto collection management sub-record created for accessions in the Archivists’ Toolkit, which was generalized for all top-level material descriptions in ArchivesSpace and supplemented by the inclusion
of events. The ArchivesSpace event module is itself an extension of the PREMIS events. </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Best,</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Brad W.</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black">From:</span></b><span><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black"> </span></span><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black"><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank"><span style="color:purple">archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a><span> </span>[<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank"><span style="color:purple">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a>]<span> </span><b>On
Behalf Of<span> </span></b>MATTHEW R FRANCIS<br>
<b>Sent:</b><span> </span>Wednesday, November 18, 2015 4:49 PM<br>
<b>To:</b><span> </span>Archivesspace Users Group<br>
<b>Subject:</b><span> </span>Re: [Archivesspace_Users_Group] Collection management - processing status disappeared...</span><span style="color:black"><u></u><u></u></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">For the reasons outlined by Kate, and seconded by Glynn, we have also found this change rather confusing, and unfortunately it has hampered our ability to identify
and report on various issues related to processing status, including the previously mentioned backlog issue.</span><span style="color:black"><u></u><u></u></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">I do not know if this is an issue that others would like revisited, but from our perspective we would welcome a conversation on if there is better alternative moving
forward (including possibly reverting back to the pre-v1.3 set-up).</span><span style="color:black"><u></u><u></u></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">-Matt</span><span style="color:black"><u></u><u></u></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Arial",sans-serif;color:black">Matt</span></b><span><b><span style="font-family:"Georgia",serif;color:black"> </span></b></span><b><span style="font-family:"Georgia",serif;color:black">Francis</span></b><span style="color:black"><u></u><u></u></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:black">Archivist for Collection Management</span><span style="color:black"><u></u><u></u></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:black">Special Collections Library<br>
Penn State University</span><span style="color:black"><u></u><u></u></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div class="MsoNormal" style="text-align:center" align="center"><span style="color:black">
<hr align="center" size="2" width="100%">
</span></div>
<div>
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">From:<span> </span></span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">"Glynn Edwards" <<a href="mailto:gedwards@stanford.edu" target="_blank"><span style="color:purple">gedwards@stanford.edu</span></a>><br>
<b>To:<span> </span></b>"Archivesspace Users Group" <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" target="_blank"><span style="color:purple">archivesspace_users_group@lyralists.lyrasis.org</span></a>><br>
<b>Sent:<span> </span></b>Wednesday, November 18, 2015 11:13:44 AM<br>
<b>Subject:<span> </span></b>Re: [Archivesspace_Users_Group] Collection management - processing status disappeared...</span><span style="color:black"><u></u><u></u></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:black">Hi Kate,</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:black">We're on the same page...I too find this rather confusing. It is not straightforward enough for tracking status of collections across holdings easily. </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:black">Cheers,</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:black">Glynn</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="color:black">Glynn Edwards<br>
Head, Technical Services<br>
Director, ePADD project<br>
Special Collections<br>
Stanford University Libraries<br>
Stanford, CA 94305-6064<br>
<a href="tel:%28650%29%20521-2255" value="+16505212255" target="_blank">(650) 521-2255</a> | </span><span style="font-family:"Calibri",sans-serif;color:black"><a href="mailto:gedwards@stanford.edu" target="_blank"><span style="font-family:"Times New Roman",serif;color:purple">gedwards@stanford.edu</span></a></span><span style="color:black"> <u></u><u></u></span></p>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt;background:white;background-position:initial initial;background-repeat:initial initial">
<span style="font-family:"Calibri",sans-serif;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
<div>
<div class="MsoNormal" style="text-align:center;background:white" align="center">
<span style="color:black">
<hr align="center" size="2" width="98%">
</span></div>
<div>
<div>
<p class="MsoNormal" style="background:white"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:</span></b><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank"><span style="color:purple">archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a><span> </span><<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank"><span style="color:purple">archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a>>
on behalf of Bowers, Kate A. <<a href="mailto:kate_bowers@harvard.edu" target="_blank"><span style="color:purple">kate_bowers@harvard.edu</span></a>><br>
<b>Sent:</b><span> </span>Tuesday, November 17, 2015 1:08 PM<br>
<b>To:</b><span> </span>Archivesspace Users Group<br>
<b>Subject:</b><span> </span>Re: [Archivesspace_Users_Group] Collection management - processing status disappeared...</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">I am very confused. Can you explain how this is would work? How is an archivist supposed to understand an accession’s status from one
or more associated “events” rather than from a straightforward status? I can also see how this would make reporting out backlogs really difficult.</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">The reason I ask is that I can see how an event can lead to a status, but it is entirely possible that a status may have no associated
event. Furthermore, the same type of event may lead to different statuses.</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">In brief, status is not the same as “event”. I can think of a couple of examples to illustrate this:</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div style="margin-left:.5in">
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:Symbol;color:#1f497d">·</span><span style="font-size:7.0pt;color:#1f497d"> <span> </span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">“Unknown”
can be a status, but it has no associated event</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div style="margin-left:.5in">
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:Symbol;color:#1f497d">·</span><span style="font-size:7.0pt;color:#1f497d"> <span> </span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">“Partially
processed” can be both a status an event. However, if one “partially processes” an accession once, then the accession remains partially processed. If one “partially processes” again, it could be that the processing has been completed and the accession’s
status is now “processed” or it could be that the accession is still only “partially processed” and that additional processing events will be necessary to reach a “processed” status.</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Thanks,</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Kate</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<div>
<p class="MsoNormal" style="background:white"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Kate Bowers</span></b><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Collections Services Archivist for Metadata, Systems, and Standards</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Harvard University Archives</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><a href="mailto:megan_sniffin-marinoff@harvard.edu" target="_blank"><span style="color:purple">kate_bowers@harvard.edu</span></a></span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><a href="tel:617.496.2713" value="+16174962713" target="_blank">617.496.2713</a></span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">voice: <a href="tel:%28617%29%20384-7787" value="+16173847787" target="_blank">(617) 384-7787</a></span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">fax: <a href="tel:%28617%29%20495-8011" value="+16174958011" target="_blank">(617) 495-8011</a></span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">web:<span> </span><a href="http://nrs.harvard.edu/urn-3:hul.eresource:archives" target="_blank"><span style="color:purple">http://nrs.harvard.edu/urn-3:hul.eresource:archives</span></a></span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Twitter: @k8_bowers</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<p class="MsoNormal" style="background:white"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black">From:</span></b><span><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black"> </span></span><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black"><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank"><span style="color:purple">archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a><span> </span>[<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank"><span style="color:purple">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a>]<span> </span><b>On
Behalf Of<span> </span></b>Noah Huffman<br>
<b>Sent:</b><span> </span>Tuesday, November 17, 2015 3:01 PM<br>
<b>To:</b><span> </span>Archivesspace Users Group<br>
<b>Subject:</b><span> </span>Re: [Archivesspace_Users_Group] Collection management - processing status disappeared...</span><span style="color:black"><u></u><u></u></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Hi Kelly,</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">During a previous release (v1.3), I think Processing Status was moved from the collection management subrecord to an Event record. Here
is a JIRA issue describing this change:<span> </span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_AR-2D827&d=CwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=KjdPV61xIn7OR7Ks9cg6HRC91WufUrZNTXFAT4skW8w&s=AZTgid9lXUTh7glUns7pyqqX7w28sAhx7rK3QIIMb8o&e=" target="_blank"><span style="color:#0563c1">https://archivesspace.atlassian.net/browse/AR-827</span></a></span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Here are some specifics:</span><span style="color:black"><u></u><u></u></span></p>
</div>
<table style="border-collapse:collapse" border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td style="width:239.4pt;border:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt" valign="top" width="319">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Remove “Processing Status” Collection Management sub-record</span><u></u><u></u></p>
</div>
</td>
<td style="width:239.4pt;border:solid windowtext 1.0pt;border-left:none;padding:0in 5.4pt 0in 5.4pt" valign="top" width="319">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If data is present, migrate to Event record with these settings and linked to same record collection management sub-record is linked to:</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Type = “Processing [Value in Collection Management Record for Processing Status]”</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Date/Time Specifier = “Time stamp for last modification of Collection Management record”</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Label= Agent relationship</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Type=Single</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Role=Implementer</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Agent=ID of agent last modifying the collection management sub-record</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><u></u><u></u></p>
</div>
</td>
</tr>
</tbody>
</table>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">So, if you previously had processing status in a collection management subrecord, you might try browsing your event records to see if
you can locate that data.</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Hope this helps,</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">-Noah</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#404040"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#404040">================</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#404040">Noah Huffman</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#404040">Archivist for Metadata, Systems, and Digital Records</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#404040">David M. Rubenstein Rare Book & Manuscript Library</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#404040">Duke University | <a href="tel:919-660-5982" value="+19196605982" target="_blank">919-660-5982</a></span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#404040"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__library.duke.edu_rubenstein_&d=CwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=KjdPV61xIn7OR7Ks9cg6HRC91WufUrZNTXFAT4skW8w&s=_GXkqn82Z-IInAOMJ80LH9QqQ2QNs6vZ496YUW6DDdw&e=" target="_blank"><span style="color:#404040">http://library.duke.edu/rubenstein/</span></a></span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<p class="MsoNormal" style="background:white"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:</span></b><span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank"><span style="color:#0563c1">archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a><span> </span>[<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank"><span style="color:#0563c1">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a>]<span> </span><b>On
Behalf Of<span> </span></b>Kelly Spring<br>
<b>Sent:</b><span> </span>Tuesday, November 17, 2015 2:40 PM<br>
<b>To:</b><span> </span><a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" target="_blank"><span style="color:#0563c1">archivesspace_users_group@lyralists.lyrasis.org</span></a><br>
<b>Subject:</b><span> </span>[Archivesspace_Users_Group] Collection management - processing status disappeared...</span><span style="color:black"><u></u><u></u></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Hello!</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Our Processing Status field is visible when using the Manage Controlled Value Lists feature; but is not present when actually working within
a collection management sub-record in an accession or resource. Any tips or advice out there?</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Thank you and have a great day!</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">*Kelly</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Kelly Spring</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Archivist for Special Collections</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">University of California, Irvine Libraries</span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><a href="tel:%28949%29%20824-6573" value="+19498246573" target="_blank">(949) 824-6573</a></span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__special.lib.uci.edu_&d=CwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=KjdPV61xIn7OR7Ks9cg6HRC91WufUrZNTXFAT4skW8w&s=zFl3APrxF-DYAdjHiyHfabcKKA8Exkt6l-SzojCi4hA&e=" target="_blank"><span style="color:#0563c1">http://special.lib.uci.edu</span></a></span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> </span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lib.uci.edu_about_zot-2Dsmarter.html&d=CwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=KjdPV61xIn7OR7Ks9cg6HRC91WufUrZNTXFAT4skW8w&s=Ts5rSOVYPjSmSaxnBfWRYPYHSdVkhu9yZ4MoUwdLS-g&e=" target="_blank"><span style="color:purple;text-decoration:none"> </span></a></span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lib.uci.edu_about_zot-2Dsmarter.html&d=CwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=KjdPV61xIn7OR7Ks9cg6HRC91WufUrZNTXFAT4skW8w&s=Ts5rSOVYPjSmSaxnBfWRYPYHSdVkhu9yZ4MoUwdLS-g&e=" target="_blank"><span style="color:purple;text-decoration:none"> </span></a></span><span style="color:black"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lib.uci.edu_about_zot-2Dsmarter.html&d=CwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=KjdPV61xIn7OR7Ks9cg6HRC91WufUrZNTXFAT4skW8w&s=Ts5rSOVYPjSmSaxnBfWRYPYHSdVkhu9yZ4MoUwdLS-g&e=" target="_blank"><span style="color:purple;text-decoration:none"><br>
_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
</span><span style="color:purple">Archivesspace_Users_Group@lyralists.lyrasis.org</span><span style="color:purple;text-decoration:none"><br>
</span><span style="color:purple">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</span></a></span><span style="color:black"><u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black">_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" target="_blank">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=CwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=QRZODf9XXD3bgxGHWgBXsAvw7uhg6gGfVUJ1KmSajT8&m=0Ck_7IMJVnx6wohz4qKGlbGyhudg134OSblcthSYEpo&s=Hy6Jm25S5RX5J4co3hzouZaE-u_g-orFLrA1i0aglwU&e=" target="_blank">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a></span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><u></u><u></u></span></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><u></u> <u></u></span></p>
</div>
</div>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><br>
_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" target="_blank">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" target="_blank">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><u></u> <u></u></span></p>
</div>
</div>
</div>
</div>
<br>_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" target="_blank">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br>
<br></blockquote></div><br></div></div></div>
<br>_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br>
<br></blockquote></div><br></div></div></div>