<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Kate,
<div class=""><br class="">
</div>
<div class="">To answer the archon specific question, it did not have that a processing status field (although I agree it would have been very helpful if it had!) </div>
<div class=""><br class="">
</div>
<div class="">Archon has a ‘processing priority value and the ‘processing status’ could be inferred, to a certain extent from the relationship between the ‘received extent’ and ‘unprocessed extent’ fields on Archon's accession record. For example, if the
former was set to 10 CF and the latter to 0 CF, you could infer it was processed. But these latter values were never heavily used in Archon even here at Illinois, and the migration tool does not migrate them, since at the time I developed the mapping I could
not figure out a good way to handle them. Since no one has never asked me why they are missing, I assume the strategy of not migrating them made a certain amount of sense ;)
<div class=""><br class="">
</div>
<div class="">Chris Prom<br class="">
<div class=""><br class="">
</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Feb 17, 2016, at 10:29 AM, Bowers, Kate A. <<a href="mailto:kate_bowers@harvard.edu" class="">kate_bowers@harvard.edu</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)" class="">
<style class=""><!--
/* 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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
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:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:2044985699;
mso-list-template-ids:-1167453858;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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]-->
<div lang="EN-US" link="blue" vlink="purple" class="">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D" class="">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.<o:p class=""></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D" class=""> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D" class="">Here’s my thinking<o:p class=""></o:p></span></p>
<p style="background:white" class=""><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D" class=""> </span></p>
<p style="background:white" class=""><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D" class="">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.<o:p class=""></o:p></span></p>
<p style="background:white" class=""><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D" class="">2) Status does not equal event. Status *<b class="">may</b>* be inferred from *<b class="">some</b>* events.
<o:p class=""></o:p></span></p>
<p style="background:white" class=""><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D" class="">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.<o:p class=""></o:p></span></p>
<p style="background:white" class=""><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D" class="">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?<o:p class=""></o:p></span></p>
<p style="background:white" class=""><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D" class=""> </span></p>
<p style="background:white" class=""><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D" class="">Kate<o:p class=""></o:p></span></p>
<p style="background:white" class=""><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D" class=""> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D" class=""> </span></p>
<div class="">
<p class="MsoNormal"><b class=""><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D" class="">Kate Bowers<o:p class=""></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D" class="">Collections Services Archivist for Metadata, Systems, and Standards<o:p class=""></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D" class="">Harvard University Archives</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D" class=""><o:p class=""></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D" class=""><a href="mailto:megan_sniffin-marinoff@harvard.edu" class=""><span style="color:blue" class="">kate_bowers@harvard.edu</span></a><o:p class=""></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D" class="">617.496.2713<o:p class=""></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D" class="">voice: (617) 384-7787
<o:p class=""></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D" class="">fax: (617) 495-8011<o:p class=""></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D" class="">web:
<a href="http://nrs.harvard.edu/urn-3:hul.eresource:archives" class="">http://nrs.harvard.edu/urn-3:hul.eresource:archives</a><o:p class=""></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D" class="">Twitter: @k8_bowers</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D" class=""><o:p class=""></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D" class=""> </span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D" class=""> </span></p>
<div class="">
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in" class="">
<p class="MsoNormal"><b class=""><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"" class="">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"" class="">
<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" class="">
archivesspace_users_group-bounces@lyralists.lyrasis.org</a> [<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" class="">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</a>]
<b class="">On Behalf Of </b>Runyon, Carolyn<br class="">
<b class="">Sent:</b> Tuesday, February 16, 2016 4:18 PM<br class="">
<b class="">To:</b> Archivesspace Users Group<br class="">
<b class="">Subject:</b> Re: [Archivesspace_Users_Group] Collection management - processing status disappeared...<o:p class=""></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p class=""> </o:p></p>
<div class="">
<p class="MsoNormal">Chris, I’m going to answer two of the questions you posed in yesterday’s email according to UTC’s preference.<o:p class=""></o:p></p>
</div>
<div class="">
<p class="MsoNormal"><o:p class=""> </o:p></p>
</div>
<div class="">
<ul type="disc" class="">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Yes, we would like to see processing event records migrated back to their original collection_management records and then removed.<o:p class=""></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Yes, we like to see processing tracked in collection_management only and have it removed as an option in events.<o:p class=""></o:p></li></ul>
<div class="">
<p class="MsoNormal"><o:p class=""> </o:p></p>
</div>
<div class="">
<p class="MsoNormal">Cheers,<o:p class=""></o:p></p>
</div>
<div class="">
<p class="MsoNormal">Carolyn<o:p class=""></o:p></p>
</div>
<div class="">
<p class="MsoNormal"><o:p class=""> </o:p></p>
</div>
<div class="">
<div class="">
<div class="">
<div class="">
<div class="">
<div class="">
<p class="MsoNormal"><span style="" class="">Carolyn Runyon<br class="">
Assistant Head of Collection Services and Director of Special Collections<br class="">
University of Tennessee at Chattanooga Library<br class="">
615 McCallie Ave., Chattanooga, TN 37403<br class="">
<a href="mailto:Carolyn-Runyon@utc.edu" class="">Carolyn-Runyon@utc.edu</a>, (423) 425-4503<br class="">
Dept. 6456, LIB 439D<o:p class=""></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p class=""> </o:p></p>
<div class="">
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt" class="">
<div class="">
<p class="MsoNormal">On Feb 15, 2016, at 1:15 PM, Chris Fitzpatrick <<a href="mailto:Chris.Fitzpatrick@lyrasis.org" class="">Chris.Fitzpatrick@lyrasis.org</a>> wrote:<o:p class=""></o:p></p>
</div>
<p class="MsoNormal"><o:p class=""> </o:p></p>
<div class="">
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";background:white" class="">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><o:p class=""></o:p></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p class=""> </o:p></p>
</div>
</div>
</div>
_______________________________________________<br class="">
Archivesspace_Users_Group mailing list<br class="">
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" class="">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br class="">
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</div>
</body>
</html>