<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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Century Gothic";
panose-1:2 11 5 2 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#993366;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1241939907;
mso-list-template-ids:1273915506;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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-AU" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366">Dear all<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366">Thanks for such a thorough discussion on this issue. We were very dismayed when the processing status field initially disappeared (not having been notified
that this was going to happen in the first place). But when it did we adapted our workflows to use Events to track our various Accessioning and Processing stages and have done significant work to correct that problems associated with the movement of information
from the Processing Status field to an Event. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366">As such we agree with Kate’s and Laurel’s approach – we would
<u>not</u> want to see the Events that we now use to track processing status disappear and would want to retain them. We are happy if the processing status is re-instated in Collection Management (we can always ignore the field if we don’t want to use i) but
would not want to see all of the information now in Events affected.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366">Best wishes<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366">Emma<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366">National Library of Australia<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Century Gothic","sans-serif";color:#17365D">Emma Jolley</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Century Gothic","sans-serif";color:#17365D">| Curator of
Digital Archives, Pictures and Manuscripts Branch|National Library of Australia Canberra ACT 2600<br>
e: <a href="mailto:emma.jolley@nla.gov.au">emma.jolley@nla.gov.au</a>|t: 02 6262 1456|</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#17365D">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366"><a href="http://www.nla.gov.au/ms"><span lang="EN-US" style="font-size:10.0pt;font-family:"Century Gothic","sans-serif";color:#17365D">www.nla.gov.au/ms</span></a>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366"><a href="http://www.nla.gov.au/support-us/make-a-collection-offer-pictures-and-manuscripts">http://www.nla.gov.au/support-us/make-a-collection-offer-pictures-and-manuscripts</a>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#993366"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> archivesspace_users_group-bounces@lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org]
<b>On Behalf Of </b>Dougherty, Laurel<br>
<b>Sent:</b> Thursday, 18 February 2016 6:34 AM<br>
<b>To:</b> 'Archivesspace Users Group'<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Collection management - processing status disappeared...<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">I think Kate’s approach sounds good. If the
<span style="background:white">processing_status_id / cataloged fields and their related dates that are currently showing as Events can simply be made to reappear (populated with the data they contain) in the Collection Management subrecord (and Kate implies
it’s actually already there in the tables), then we’re not necessarily proposing a sweeping deletion of folks’ data or a change to the data model—just a restoration of functionality that has been the focus of this conversation.<o:p></o:p></span></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";background:white"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";background:white">Perhaps this could happen in a sequence of events like this:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">1)</span><span lang="EN-US" style="font-size:7.0pt">
</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";background:white">Following a pull request and prioritization/acceptance, a future version of ASpace is released with processing and cataloged status options (pull-down menus)
and the other requisite fields that go along with them back in the Collection Management subrecord. Updating to this version doesn’t cause anyone to lose data—it just reappears as it was originally migrated.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">2)</span><span lang="EN-US" style="font-size:7.0pt">
</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";background:white">The migration tool is re-configured, for those who aren’t in production yet, to have their AT processing status data mapped to the Collections Management
subrecord<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">3)</span><span lang="EN-US" style="font-size:7.0pt">
</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";background:white">Institutions that want to wipe out their processing-related events can do so; if a plug-in is required to transfer data added to the Events module (post-migration),
that is developed as a final step<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";background:white"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";background:white">It’s easy to configure the events by adding and deleting fields to fit your needs. So I wouldn’t propose a reverse migration that wipes out
processing events for everyone—after all, while re-reading Brad’s post on this topic from November, this change was done with good intentions and was a deliberate extension of the PREMIS events model. I quote Brad here:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";background:white"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#2E75B6">“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.”<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Some repositories may very well want to continue adding processing actions as events (i.e. “partially processed” by [agent] on [date]) to allow for granular
reports on these types of events and agents in the future. But it seems, <i>in addition</i>, institutions simply want an option via Collection Management to say: is this stuff processed, or not? Because an event is not necessarily the same as a status. As
others have pointed out, a status is just easier for querying and on-the-ground collection management.
<span style="background:white">A one-time version change that exposes those relevant fields that were moved to Events and plops them back into the Collection Management subrecord might be a suitable minimum “do no harm” approach. Plug-ins to migrate data between
the Events and Collections Management subrecords might be a slightly different issue.<o:p></o:p></span></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";background:white"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";background:white">Respectfully,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";background:white">Laurel<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Laurel McPhee Dougherty<o:p></o:p></span></b></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Supervisory Archivist, Special Collections & Archives Program<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">UC San Diego Library |
</span><span lang="EN-US" style="font-size:10.0pt;font-family:Wingdings">(</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif"">
</span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">858-534-5619 |</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif"">
</span><span lang="EN-US" style="font-size:10.0pt;font-family:Wingdings">*</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif"">
</span><span lang="EN-US"><a href="mailto:l1dougherty@ucsd.edu"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#2E74B5">l1dougherty@ucsd.edu</span></a></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-bounces@lyralists.lyrasis.org</a> [<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</a>]
<b>On Behalf Of </b>Bowers, Kate A.<br>
<b>Sent:</b> Wednesday, February 17, 2016 8:30 AM<br>
<b>To:</b> Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a>><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Collection management - processing status disappeared...<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I’m not sure that incorporating “reverse migration” for all into re-establishing the disappeared functionality would be wise. Rather a one-time
“reversion helper” plug-in, that can be optionally executed by an ArchivesSpace repository, is better.</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Here’s my thinking</span><span lang="EN-US"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">1) Less work means more likelihood of getting the basic, vital functionality of “processing status” back into collection management records
more quickly. By this I mean: the table is still there with the data in it (at least for AT migrations). Just put it back into the interface and for users and admins.</span><span lang="EN-US"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">2) Status does not equal event. Status *<b>may</b>* be inferred from *<b>some</b>* events.
</span><span lang="EN-US"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">3) Individual implementers have control over their drop-down lists, thus, each type of event would have to be evaluated for its real-world
meaning vis-a-vis processing status. Automated monkeying might obfuscate the actual processing status. There is no way to know what can be automated across the board. Ergo, individual repositories have to govern these changes.</span><span lang="EN-US"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">4) Individual implementers may not need “reverse migration” and the labor might be in excess of the work needed to simply apply processing
statuses to accessions by hand. Questions to evaluate the need include: a) How much work would be involved in creating “reverse migration”? b) As far as I can tell, processing statuses that migrated from AT are still there. For many repositories, changing
processing status may not be that labor-intensive—it could be that not many accessions have been processed between migration and implementation. c) Did Archon have processing status? If so, were they also retained? d) How many repositories changed the
default drop-downs for event records?</span><span lang="EN-US"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Kate</span><span lang="EN-US"><o:p></o:p></span></p>
<p style="background:white"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span lang="EN-US"><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Kate Bowers</span></b><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Collections Services Archivist for Metadata, Systems, and Standards</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Harvard University Archives</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><a href="mailto:megan_sniffin-marinoff@harvard.edu"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">kate_bowers@harvard.edu</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">617.496.2713</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">voice: (617) 384-7787
</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">fax: (617) 495-8011</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">web:
</span><span lang="EN-US"><a href="http://nrs.harvard.edu/urn-3:hul.eresource:archives"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">http://nrs.harvard.edu/urn-3:hul.eresource:archives</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Twitter: @k8_bowers</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span lang="EN-US"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
</span><span lang="EN-US"><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a></span><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
[</span><span lang="EN-US"><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</span></a></span><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">]
<b>On Behalf Of </b>Runyon, Carolyn<br>
<b>Sent:</b> Tuesday, February 16, 2016 4:18 PM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Collection management - processing status disappeared...</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">Chris, I’m going to answer two of the questions you posed in yesterday’s email according to UTC’s preference.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
<div>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span lang="EN-US">Yes, we would like to see processing event records migrated back to their original collection_management records and then removed.<o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span lang="EN-US">Yes, we like to see processing tracked in collection_management only and have it removed as an option in events.<o:p></o:p></span></li></ul>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Cheers,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Carolyn<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="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>
</span><span lang="EN-US"><a href="mailto:Carolyn-Runyon@utc.edu">Carolyn-Runyon@utc.edu</a><span style="color:black">, (423) 425-4503<br>
Dept. 6456, LIB 439D</span><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span lang="EN-US">On Feb 15, 2016, at 1:15 PM, Chris Fitzpatrick <<a href="mailto:Chris.Fitzpatrick@lyrasis.org">Chris.Fitzpatrick@lyrasis.org</a>> wrote:<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-family:"Calibri","sans-serif";background:white">One thing I am curious about is are people wanting to have this processing_status_id field added to the collection_management table, but are you wanting to have
these event records migrated back to collection_management records and then removed ( the migration to make this change moved the data from the collection_management table into events) ? Are you wanting to do away with the processing status in events completely?</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
</div>
</body>
</html>