<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 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@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;}
/* 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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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">
<div class="WordSection1">
<p class="MsoNormal">Hello ArchivesSpace members,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As mentioned in last week’s monthly update, Georgia Tech co-op student Sarah Morrissey is working closely with Laney on various projects, including an update to the Archivists’ Toolkit migration tool, to be followed soon afterward by an
update to the Archon tool. The aim is to make it possible to migrate data from the last version of each of these systems into the current version of ArchivesSpace. (Currently migration is only supported through ArchivesSpace 1.4.2 and then users must upgrade
to later versions of ArchivesSpace from there.)<span style="color:#0070C0"> We’re really excited about this update but we need your insight to move forward.</span><span style="color:#7030A0"><o:p></o:p></span></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">As you may imagine, one of the more complex pieces of the update is mapping container information from Toolkit to the ArchivesSpace container model. One discrepancy we have found is that Toolkit allowed locations to be linked directly to
accessions, with no intervening instances or containers. In ArchivesSpace locations have to be linked to a top container, which is in turn linked to an instance. So locations that were attached directly to accessions in Toolkit need to be translated into instance
records, and now into instances with top containers, and then attached to the top container.
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">We’re curious how people who used locations with accessions in Toolkit have translated this data into ArchivesSpace to this point. Sarah is analyzing whether there is any way to determine what top containers should be created when, due
to the use of locations, there seem to be implied containers linked to accessions. One top container per location? We are thinking the indicator would be something like the accession number plus the location with a sequential “unknown container” or similar.
Does anyone have a better suggestion, or want to voice support for that idea? <o:p>
</o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="color:black">We see there’s also an optional Note/Container Information field that is part of the linking information that may be useful in some cases in determining container information, but since it’s optional, it wouldn’t
be there in all cases, and even, if data is present, it may not always provide information that could be used to determine the appropriate top container data.
</span>If you used locations with accessions in AT, did you use this note field to record such information? Could it be parsed out into useful container type or indicator information?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks for any suggestions and feedback you can provide. And looking ahead to the update of the Archon migration tool, if you have any suggestions for identifying top containers from Archon data, we’d be very interested to have them.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Christine<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#1F497D">Christine Di Bella<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#1F497D">ArchivesSpace Program Manager<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#1F497D"><a href="mailto:christine.dibella@lyrasis.org"><span style="color:#0563C1">christine.dibella@lyrasis.org</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#1F497D">800.999.8558 x2905<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#1F497D">678-235-2905<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#1F497D">cdibella13 (Skype)</span><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><img border="0" width="267" height="61" style="width:2.7777in;height:.6388in" id="Picture_x0020_1" src="cid:image003.jpg@01D33781.9F026700" alt="ASpaceOrgHomeMedium"><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>