<html 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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (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:PMingLiU;
panose-1:2 2 5 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Apple Color Emoji";
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"\@PMingLiU";
panose-1:2 1 6 1 0 1 1 1 1 1;}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
/* 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;}
span.EmailStyle25
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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:593518572;
mso-list-type:hybrid;
mso-list-template-ids:1175863778 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1
{mso-list-id:2004357040;
mso-list-template-ids:174092678;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Hi Corey, <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I wanted to make sure that you knew that the current version of the AT Migration Tool will only work up to ArchivesSpace version 2.6.0 so, when testing and for production, make sure you migrate into ArchivesSpace version 2.6.0 and then
upgrade into 2.7.0 or higher from there.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best,<o:p></o:p></p>
<p class="MsoNormal">Laney<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black"><archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of Corey Schmidt <Corey.Schmidt@uga.edu><br>
<b>Reply-To: </b>Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Date: </b>Wednesday, December 11, 2019 at 12:51 PM<br>
<b>To: </b>Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Subject: </b>Re: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">Noah,<br>
<br>
Thank you for the advice!<br>
<br>
I have copies of databases made, but I do not have access to the MySQL databases directly, as that is being hosted by a third-party. If I can get access to them, I should be able to experiment with cleaning them up directly with SQL. I have some experience
working with SQLite, so it shouldn’t be too hard to learn. I’ll look into using Navicat too, as it seems like a pretty handy tool.
<br>
<br>
Thanks,<br>
<br>
Corey</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org>
<b>On Behalf Of </b>Noah Huffman<br>
<b>Sent:</b> Wednesday, December 11, 2019 12:13 PM<br>
<b>To:</b> Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#BA0C2F">[External Sender]</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D">Hi Corey,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">I’d highly recommend doing as much data cleanup as possible directly in your AT database, particularly extent type values, container type values, etc. Of course, be sure to back up your database</span><span style="font-family:Wingdings;color:#1F497D">J</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">If you’re comfortable writing/running SQL queries, you can connect a free database management tool like MySQL Workbench to your AT backend database to review/clean your data in bulk.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Alternatively, there are other database management tools like Navicat that let you review and edit the backend database tables in a graphical spreadsheet-like editor (without having to write SQL). I used Navicat
to clean up a lot of AT data prior to migrating to ASpace. If you can do all your cleanup in the 14-day trial period, then you don’t have to buy the software!</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Best of luck,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">-Noah</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif;color:#404040">================</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif;color:#404040">Noah Huffman</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif;color:#404040">Archivist for Metadata, Systems, and Digital Records</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif;color:#404040">David M. Rubenstein Rare Book & Manuscript Library</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif;color:#404040">Duke University | 919-660-5982</span><o:p></o:p></p>
<p class="MsoNormal"><a href="http://library.duke.edu/rubenstein/"><span style="font-size:10.0pt;font-family:"Georgia",serif;color:#404040">http://library.duke.edu/rubenstein/</span></a><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></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">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>>
<b>On Behalf Of </b>Corey Schmidt<br>
<b>Sent:</b> Wednesday, December 11, 2019 10:20 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] Archivists' Toolkit to ArchivesSpace Migration Workflow<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">Mark,<br>
<br>
Thank you so much for the wonderful info!<br>
<br>
I am just beginning to dive into the data, but I will look out for linked cross references and the creation of new data in ArchivesSpace. We don’t have any EADs that exist outside of AT so far as I’m aware, so the process of exporting from AT, cleaning up,
then reimporting might be unnecessary as you pointed out. If it’s possible to update the AT database directly, that would save so much time and effort. The articles you linked were very helpful and should give me a basis for how to approach this and other
potential problems.<br>
<br>
Thanks again!<br>
<br>
Corey</span><o:p></o:p></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">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>>
<b>On Behalf Of </b>Custer, Mark<br>
<b>Sent:</b> Tuesday, December 10, 2019 6:33 PM<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] Archivists' Toolkit to ArchivesSpace Migration Workflow<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#BA0C2F">[External Sender]</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><o:p></o:p></p>
<div>
<p class="MsoNormal">Corey,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">First of all, welcome to the ArchivesSpace community! Your project will definitely make you an ArchivesSpace expert in no time.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Glancing at your workflow document, it looks like you’ve got all of your bases covered. I would strongly suggest running the AT to ASpace migration a couple of times (just to get familiar with it), and also to get a few other folks to
help spot-check the results (the more eyes / institutional experience the better), before you go ahead and do the final migration. It’s a been a long while since I used that tool. I do remember, though, that when we started testing it out, the tool couldn’t
be used to migrate multiple AT databases into a single ASpace database. That feature was added a long time back, though, so you *<b>should</b>* be good to go with migrating your two AT databases into a single version of ASpace, which I would highly recommend.
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Regarding the AT to ASpace migration tool, just off the top of my head, I’d also add:<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="mso-list:l0 level1 lfo3">if you have linked cross references in your current EAD files, you’ll either want to make sure to run the migration with the “-refid_original” parameter, or set aside some time after the migration to go
back and update those linked cross references (during the migration, all of the IDs in the AT for the notes and components will be replaced with ASpace IDs, so if you have cross references embedded in your finding aids, those will be broken). We had a lot
of cross references in our source files in the AT, so we opted with that first option, as you can see here:
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__cpb-2Dus-2Dw2.wpmucdn.com_campuspress.yale.edu_dist_3_30_files_2015_06_Unknown-2D272cqj2.png&d=DwMGaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=F0JE8U9-xhxe_nE7d7aEUi-uqfKqvYJ222bS0oz9mko&m=vo2cEUnvLpW5VnkjGgT51bFLOVXx20ZT_riutVaGWdk&s=wAFpobhQCHykVKaA3PvxMD1LV9nuhYN6NlBik8fLndQ&e=">
https://cpb-us-w2.wpmucdn.com/campuspress.yale.edu/dist/3/30/files/2015/06/Unknown-272cqj2.png</a> (that screenshot was taken by Maureen Callahan, and described in a lot of more detail and other invaluable advice in this blog post:
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__campuspress.yale.edu_yalearchivesspace_2015_06_14_migration-2Dstep-2Dby-2Dstep_&d=DwMGaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=F0JE8U9-xhxe_nE7d7aEUi-uqfKqvYJ222bS0oz9mko&m=vo2cEUnvLpW5VnkjGgT51bFLOVXx20ZT_riutVaGWdk&s=j8ov-2Tv_zGRR7Hv0uGKmvXsigJAHo14quVlYe2hYTQ&e=">
https://campuspress.yale.edu/yalearchivesspace/2015/06/14/migration-step-by-step/</a>)<o:p></o:p></li><li class="MsoNormal" style="mso-list:l0 level1 lfo3">unless things have changed, be prepared for that migration tool to occasionally add data where no data existed before (even when it’s not required to do so). E.g. for our lists in the AT that did not have
a title, after the migration we wound up with lists in ASpace that had a title of “Missing Title”. That was something we missed early on, but later on we were able to delete all of those values from ASpace. Ditto for other unexpected things, like if in the
AT someone selected a container type of “Box” but level the container value blank, the AT to ASpace migration would create an auto-generated container number so that it could keep that container type of “Box” around without dropping it during the migration.
We had quite a few instances in the AT where someone would add “Box X, Folder”. That behaved fine in the AT, but once we migrated, that would turn into something like “Box X, Folder someweirdnumber” (ideally it would’ve just come over as “Box X”).<o:p></o:p></li></ol>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">And unless you have EAD files that aren’t in the AT already, I don’t think that you should need to go the route of importing EAD into ASpace. If you do, there are more issues and tricks involved there, not to mention the fact that the
more import options you allow during the migration, the more variety you’ll have in the results. That’s not to say that EAD imports are bad ASpace, since they’ve actually improved on the AT’s EAD import process. Also, long after our migration, we still import
EAD files into ASpace, especially when adding newly-created finding aids that are so large or complex that they’d be hard to create directly in ASpace. However, you’ll have to be mindful of all of the ways that those EAD imports can muddy up your database
(the primary offender being the fact that the importer will add values to controlled value lists during the import process when it tries to parse them from free text data…. See the comment here
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_archivesspace_archivesspace_blob_bc675bc12b72f6fb7818aae646958c80d54ff4de_backend_app_model_backend-5Fenum-5Fsource.rb-23L16&d=DwMGaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=F0JE8U9-xhxe_nE7d7aEUi-uqfKqvYJ222bS0oz9mko&m=vo2cEUnvLpW5VnkjGgT51bFLOVXx20ZT_riutVaGWdk&s=Ye49b0aqHVOMrCWJkMs8rMyxwWVhfMgMtHgnIpr4dTw&e=">
https://github.com/archivesspace/archivesspace/blob/bc675bc12b72f6fb7818aae646958c80d54ff4de/backend/app/model/backend_enum_source.rb#L16</a>… In other words, free text like “<span style="color:black;background:white">2.5 Linear feet (4 boxes)”</span> would
result in a new extent type with a value of “Linear Feet (4 boxes)”, which is not a controlled extent type that anyone wants to have around.
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Okay, that’s probably more info than you wanted, but hopefully some of it’s helpful
<span style="font-family:"Apple Color Emoji"">😊</span> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">There are lots of others who have been through the same journey, so lots of folks to get advice from, including this recent article in the code4lib journal,
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__journal.code4lib.org_articles_14871&d=DwMGaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=F0JE8U9-xhxe_nE7d7aEUi-uqfKqvYJ222bS0oz9mko&m=vo2cEUnvLpW5VnkjGgT51bFLOVXx20ZT_riutVaGWdk&s=qVHP4W8r7zhBScX6X5JXP077O3J_1CSgOY6NYJKX7Pk&e=">
https://journal.code4lib.org/articles/14871</a>, which describes the migration to ASpace at Columbia University.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Keep us posted with how everything goes,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Mark<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></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>Corey Schmidt<br>
<b>Sent:</b> Tuesday, 10 December, 2019 2:09 PM<br>
<b>To:</b> <a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a><br>
<b>Subject:</b> [Archivesspace_Users_Group] Archivists' Toolkit to ArchivesSpace Migration Workflow<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">Dear ArchivesSpace Community,<br>
<br>
Hello, my name is Corey Schmidt. I am the ArchivesSpace Project Manager at the University of Georgia Libraries. I am responsible for managing the migration from Archivists’ Toolkit to ArchivesSpace and revamping our public interface to include resources from
both the Hargrett Rare Book and Manuscript Library and the Richard B. Russell Library for Political Research and Studies.<br>
<br>
I created a project workflow of how I expect the project to unfold over the next year and I was hoping to get people’s feedback on it. Specifically, I’m looking for help identifying any missing processes, changing the order of the steps involved, or anything
else that should be advised moving forward. I derived a lot of information from publications by the University of Minnesota, Harvard University, Yale University, the Rockefeller Archive Center, and the Bentley Historical Library at the University of Michigan.<br>
<br>
Thank you for your time and assistance! I have attached the workflow to this email.<br>
<br>
Sincerely,<br>
<br>
Corey</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Verdana",sans-serif">Corey Schmidt</span><span style="font-family:"Verdana",sans-serif"><br>
</span><i><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">ArchivesSpace Project Manager</span></i><span style="font-size:10.0pt;font-family:"Verdana",sans-serif"> | University of Georgia Libraries</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#3B3838">Email:
</span><a href="mailto:Corey.Schmidt@uga.edu"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">Corey.Schmidt@uga.edu</span></a><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#3B3838">Phone</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">: +1-706-542-8151</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>