<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Arial Narrow";
panose-1:2 11 6 6 2 2 2 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
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.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle23
{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;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>Hi Linda,</p>
<p><br>
</p>
<p>Sorry for not replying earlier. With versions 1.5 of ArchivesSpace, we are no longer using any plugins for container and location management at Yale. In addition to the features added to the core code from Yale's plugin for container management (described
here <a href="http://guides.library.yale.edu/archivesspace/ASpaceContainerManagement" class="OWAAutoLink" id="LPlnk244818">http://guides.library.yale.edu/archivesspace/ASpaceContainerManagement</a>), versions 1.5 of ArchivesSpace also include some nifty new
methods for location management, which were developed by our colleagues at NYU (described here <a href="http://guides.nyu.edu/archivesspace/development#s-lg-box-10702482" class="OWAAutoLink" id="LPlnk463770">http://guides.nyu.edu/archivesspace/development#s-lg-box-10702482</a>). </p>
<p><br>
</p>
<p>All of which is to say that I don't think that a separate plugin for container/location management is required. There are still some additional features that are desired (e.g. the ability to merge containers, including when staff users use the resource
merge function), but I expect that such features and other enhancements will be added directly to the core code moving forward.</p>
<p><br>
</p>
<p>Mark</p>
<br>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of Avetta, Linda
<lavetta@pa.gov><br>
<b>Sent:</b> Thursday, October 13, 2016 8:10:35 AM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Data migration problem ATK - ArchivesSpace only specific Resource records not transferred</font>
<div> </div>
</div>
<div>
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Mark,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I’m curious to know what container management plug-in you use at Yale, and if you will still be using the same plug-in in AS. Or do you think AS has sufficient location/barcode/space management that a separate
plug-in is not needed. Any feedback would be appreciated.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Linda <o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#033668">Linda Avetta</span></b><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#033668"> | </span><span style="font-size:9.0pt;font-family:"Verdana","sans-serif";color:#033668">Division
Chief </span><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Verdana","sans-serif";color:#033668">Digital Archives & Records Division</span><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Verdana","sans-serif";color:#033668">Pennsylvania State Archives<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Verdana","sans-serif";color:#033668">PA Historical & Museum Commission</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Verdana","sans-serif";color:#033668">The Commonwealth of Pennsylvania</span><span style="font-size:9.0pt;font-family:"Verdana","sans-serif";color:#033668"><br>
</span><span style="font-size:9.0pt;font-family:"Verdana","sans-serif";color:#033668">1825 Stanley Drive | Harrisburg, PA 17103<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Verdana","sans-serif";color:#033668">Phone: 717.705.6923</span><span style="font-size:9.0pt;font-family:"Verdana","sans-serif";color:#033668"><br>
</span><span style="color:#1F497D">Visit us on the web at <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.phmc.state.pa.us_&d=CwMFAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=ocDmVxLGTIl3XCIWNtmmSP1vh96Z0r-hkqodUzf7hdQ&s=NsXWtrKBYrLHCVB4iJ5NiGKr29Z2DlWM_OjCF6MtpRo&e=">
<span style="color:blue">PHMC.state.pa.us</span></a> and <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.digitalarchives.state.pa.us_&d=CwMFAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=ocDmVxLGTIl3XCIWNtmmSP1vh96Z0r-hkqodUzf7hdQ&s=740yfwjw57gZhC04Vk5w8GWaCFjTpYbv21AnaIKmWzg&e=">
<span style="color:blue">DigitalArchives</span></a></span><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></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""> archivesspace_users_group-bounces@lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org]
<b>On Behalf Of </b>Custer, Mark<br>
<b>Sent:</b> Wednesday, October 12, 2016 3:59 PM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Data migration problem ATK - ArchivesSpace only specific Resource records not transferred<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Just a quick reply to say that we chose option 1, too, here at Yale. We tested the migration process many times before we performed the official migration. Maureen Callahan provided a window into the fun in
the following blog post: <a href="http://campuspress.yale.edu/yalearchivesspace/2015/04/23/reading-migration-bugs-and-fixing-our-data/">
http://campuspress.yale.edu/yalearchivesspace/2015/04/23/reading-migration-bugs-and-fixing-our-data/</a> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Mark<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> <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>Noah Huffman<br>
<b>Sent:</b> Wednesday, 12 October, 2016 2:50 PM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Data migration problem ATK - ArchivesSpace only specific Resource records not transferred<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Hi Kari,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I’m not aware of a way to run the AT migration tool on a subset of resource records.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I think your options are:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="color:#1F497D">1.</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#1F497D">
</span><span style="color:#1F497D">Figure out why the 6 records did not migrate (did you see any issues reported in the migration error log?), fix the issues, and run the entire ATK to ASpace migration again<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="color:#1F497D">2.</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#1F497D">
</span><span style="color:#1F497D">Export the 6 resources from ATK as EAD and import the EAD into ASpace.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">If you choose option 2, you’ll lose some of the relationships you may have established in ATK between the resource record and other record types, particularly accession records.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">We encountered a similar problem during our ATK to ASpace migration and chose option 1, iteratively solving the problems reported in the migration error log and then re-running the migration tool.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">-Noah<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial Narrow","sans-serif";color:#404040">================<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial Narrow","sans-serif";color:#404040">Noah Huffman<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial Narrow","sans-serif";color:#404040">Archivist for Metadata, Systems, and Digital Records<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial Narrow","sans-serif";color:#404040">David M. Rubenstein Rare Book & Manuscript Library<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial Narrow","sans-serif";color:#404040">Duke University | 919-660-5982<o:p></o:p></span></p>
<p class="MsoNormal"><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=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=kCFtHMS6FHGe35dhJfwb63t9TdWkUzsrgc_BkKPo41U&s=QdzD5U5IFhYpcpYq7VZjIT37qoal_k_raX05oP2g57Q&e="><span style="color:#404040">http://library.duke.edu/rubenstein/</span></a>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> <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>Kari R Smith<br>
<b>Sent:</b> Wednesday, October 12, 2016 11:01 AM<br>
<b>To:</b> Archivesspace Users Group (<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a>) <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a>><br>
<b>Subject:</b> [Archivesspace_Users_Group] Data migration problem ATK - ArchivesSpace only specific Resource records not transferred<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hello,<o:p></o:p></p>
<p class="MsoNormal">In our recent data migration from ATK to ArchivesSpace there were 6 Resource records that did not transfer. We have the IDs of the records. The components, Names, Accession records associated all transferred.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Is there a way to run the migrator tool for just the 6 specific collections? Or am I best off doing an EAD XML export from ATK and then Importing those into ArchivesSpace?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Kari R. Smith<o:p></o:p></p>
<p class="MsoNormal">Digital Archivist, Institute Archives and Special Collections<o:p></o:p></p>
<p class="MsoNormal">Massachusetts Institute of Technology Libraries<o:p></o:p></p>
<p class="MsoNormal">617.253.5690 smithkr at mit.edu <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__libraries.mit.edu_archives_&d=CwMFAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=kCFtHMS6FHGe35dhJfwb63t9TdWkUzsrgc_BkKPo41U&s=n2vPc-OJ2GbEHRLGv9-KOoN45SgcEpLIpu9rzrj4pxI&e=">
http://libraries.mit.edu/archives/</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>