<div dir="ltr">Hi Nancy,<div><br></div><div>The Migrator tool can do that, but it does involve the creation of custom migration scripts so you will need to decide based on your workflow if it's worth it.  We can setup a Skype call to discuss further if you would like?</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 25, 2015 at 10:21 AM, Kennedy, Nancy <span dir="ltr"><<a href="mailto:KennedyN@si.edu" target="_blank">KennedyN@si.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">





<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Mark,
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I just mean with regard to asking Jason R. to change the STEADY to ‘</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">include
 generated @id and @parent values on the container elements’</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">.  If the STEADY files are generated with @id, that’s fine for ASpace, but creates problems for AT users that
 rely on the BYU plugins.  We’d have to strip out the @id before import to our AT. And, for now, we need to keep our AT workflows working.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Using the XSLT temporary fix to add @id (i.e. outside of STEADY) is clearly preferable for us. Though Matt might have a different perspective on that : ) 
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Agreed too on the logic to fix the ASpace importer.  That seems necessary and like it ought to work.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Chris’s suggestion to incorporate Jason's stead into ASpace as a CSV importer is appealing on this end. Though, I think we would still need to fix the importer
 logic.  STEADY does a lot for us, but we have cases where the spreadsheet exceeds STEADY’s model and so we’d still be going from spreadsheet -> EAD -> AT/ASpace.  …  unless this ASpaceMigrator tool can do it.  Thanks, Nathan, for the heads up. 
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">nancy<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<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""> <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">archivesspace_users_group-bounces@lyralists.lyrasis.org</a> [mailto:<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>]
<b>On Behalf Of </b>Nathan Stevens<br>
<b>Sent:</b> Wednesday, February 25, 2015 10:14 AM</span></p><div><div class="h5"><br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] EAD instance issue<u></u><u></u></div></div><p></p><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">To further muddy the issue, If you are looking to construct ASpace Resource records from Excel data then you should also consider looking at the
<a href="https://github.com/ns96/ASpaceMigrator" target="_blank">ASpaceMigrator</a> tool the ASpace team has been slowly working on. It currently beta code, but it has been used successfully by a few groups to migrate data into ASpace.<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">On Wed, Feb 25, 2015 at 9:53 AM, Custer, Mark <<a href="mailto:mark.custer@yale.edu" target="_blank">mark.custer@yale.edu</a>> wrote:<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Nancy,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I’m not sure what you mean regarding the multiple date and extent plugins (although I do have experience
 using that, and I think that it was a great addition to the AT data model!).  This shouldn’t cause any problem at all.  The @id attribute is only applied to a container element with the stylesheet that I provided, and it should never be repeated in the file
 in this case. </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Also, I agree that it should be addressed by the ASpace importer.  I was just providing a temporary
 fix, which I thought would be much easier (not to mention much, much faster) than importing and exporting a file into the AT!
</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Lastly, I  wasn’t clear in one of my earlier emails.  To fix this in the ASpace importer, here’s
 what I think the logic should be:</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">1)</span><span style="font-size:7.0pt;color:#1f497d">     
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> If @id and @parent attributes are present on container elements, use that data to group and import multiple instances. Voilà, we can finally retain multiple instances, which
 we could only produce in the AT but not consume (this is now the current behavior in ASpace).</span><u></u><u></u></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">2)</span><span style="font-size:7.0pt;color:#1f497d">     
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">If @id and @parent attributes are NOT present on the container elements within any EAD did element, then treat all of those containers as a single instance, rather than multiple
 instances.  In this case, if there are more than 3 sibling container elements (which is exceedingly rare), then only the first 3 will be imported into ASpace as a single container group (which follows the AT’s import behavior).</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Mark</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">
archivesspace_users_group-bounces@lyralists.lyrasis.org</a> [mailto:<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>]
<b>On Behalf Of </b>Kennedy, Nancy<br>
<b>Sent:</b> Wednesday, February 25, 2015 9:34 AM</span><u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"><br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] EAD instance issue<u></u><u></u></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Mark,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Wouldn’t adding @id pairs to the STEADY output cause trouble for repositories that still need to
 use the AT multiple date and extent plugins (the BYU plugins)?  For the near term, we will still be using AT and the BYU plugins.  For us, @id pairs will throw errors on import.  Granted, we could incorporate workarounds to strip any STEADY created @id pairs. 
</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">But, since the @id is not required by the EAD and is being considered here primarily to support a
 feature (and a GREAT one! I’m so looking forward to being able to import multiple instances) for ArchivesSpace, I’d much rather see it addressed within ArchivesSpace importers ... rather than as a change to STEADY outputs.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">One of the nice things about STEADY is how (nearly) ready-to-go its EAD files are.  We have other
 methods for importing from spreadsheets, particularly when round-tripping, but STEADY is by far the easier option for new users and student projects. I’d really like to keep it as simple as possible!</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Nancy</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Nancy Kennedy</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">EAD Coordinator</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Smithsonian Institution
</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><a href="mailto:KennedyN@si.edu" target="_blank">KennedyN@si.edu</a></span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></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"">
<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">
archivesspace_users_group-bounces@lyralists.lyrasis.org</a> [<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</a>]
<b>On Behalf Of </b>Custer, Mark<br>
<b>Sent:</b> Tuesday, February 24, 2015 2:59 PM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] EAD instance issue</span><u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">All,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">So I fear that this is caused by my request to allow grouped containers to be imported into ArchivesSpace,
 since that was never possible with Archivists’ Toolkit. I’ll forward this message to the creator of Steady, Jason Ronallo, to see if it would just be a simple change to include generated @id and @parent values on the container elements.  So, in the example
 below, the EAD output could look like this, instead:</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in">
<span style="color:black"><container type="box" label="Text" <span style="background:yellow">
id=”c1”</span>>1</container><br>
<container type="folder" label="Text" <span style="background:yellow">parent=”c1</span>”>20</container></span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">(alternatively, if the @label attribute was only output once in this example, then that value could
 be used to do the grouping by the EAD importer, but I personally prefer to rely on the @parent and @id attributes since those are the examples given in the EAD tag library,
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.loc.gov_ead_tglib_elements_container.html&d=AwMGaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=TQmmzdQt9TEtFi4MyRDTt2mXhw0lj8a26EWCdRuOp6c&s=qasB18CQYeZyhBeEO7mLJyhn7J8M0VcUZOpLFbOCSmg&e=" target="_blank">
http://www.loc.gov/ead/tglib/elements/container.html</a>)</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Another option would be for the ASpace importer to
<i>only</i> group containers when @id and @parent attributes are available.  In other words, if those attributes aren’t part of the container elements, like they aren’t with the Steady-produced files, then those sibling containers should be considered a single
 group (and if there are more than 3 sibling container elements, only the first 3 would be imported, which also mimics the AT’s behavior).  I haven’t looked into the ASpace EAD importer yet, but I’ll see if I can’t find the relevant pieces of code that govern
 this behavior.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">All my best,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Mark</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">
archivesspace_users_group-bounces@lyralists.lyrasis.org</a> [<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</a>]
<b>On Behalf Of </b>MATTHEW R FRANCIS<br>
<b>Sent:</b> Tuesday, February 24, 2015 2:41 PM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] EAD instance issue</span><u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"> <u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"><span style="color:black">Noah,</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Thank you for the quick and helpful response, it is greatly appreciated.  I think your right about the cause for the change in behavior, and more importantly
 from my perspective your AT import/export WF recommendation looks like it will work as a stop-gap process for us until there is a better way to proceed.</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Cheers and thanks again.</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">-Matt</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia","serif";color:black">Matt Francis</span><u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia","serif";color:black">Archivist for Collection Management</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia","serif";color:black">Special Collections Library<br>
Penn State University</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="color:black"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia","serif";color:black">Twitter: @archivingmatt</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia","serif";color:black"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.archivingmatt.com&d=AwMGaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=TQmmzdQt9TEtFi4MyRDTt2mXhw0lj8a26EWCdRuOp6c&s=wCIhwm68gqzh_-QEuiVqQ_RAU4lDNkKOR_rcKgDqHYU&e=" target="_blank">http://www.archivingmatt.com</a></span><u></u><u></u></p>
</div>
<p class="MsoNormal"><span style="color:black"> </span><u></u><u></u></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="color:black">
<hr size="2" width="100%" align="center">
</span></div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Helvetica","sans-serif";color:black">From:
</span></b><span style="font-family:"Helvetica","sans-serif";color:black">"Noah Huffman" <<a href="mailto:noah.huffman@duke.edu" target="_blank">noah.huffman@duke.edu</a>><br>
<b>To: </b>"Archivesspace Users Group" <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" target="_blank">archivesspace_users_group@lyralists.lyrasis.org</a>><br>
<b>Sent: </b>Tuesday, February 24, 2015 2:25:55 PM<br>
<b>Subject: </b>Re: [Archivesspace_Users_Group] EAD instance issue</span><u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica","sans-serif";color:black"> </span><u></u><u></u></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hi Matthew,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I just tested and confirmed the issue you describe.  We use the same Excel->Steady->EAD->AT/ASpace
 workflow for large container lists, so this is also an issue for us.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I suspect the behavior is related to changes made in response to this ticket:
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_AR-2D751&d=AwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=fsFyKgFz0gzNJ4-L054MLtQb1rGgFEE3gczfb-PzjpE&s=aJPXDL4UOTUg7jAHm5x3t-foUC9_1wI735l3-gx7VaY&e=" target="_blank">
https://archivesspace.atlassian.net/browse/AR-751</a></span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">This isn’t a long term solution, but to achieve your desired result, you could import the XML output
 of Steady into Archivists Toolkit, then export EAD, then import to ArchivesSpace.  I just tested this and it works.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">The AT Importer will create a single instance record for the box/folder and on export AT will assign
 @id and @parent attributes to the containers that communicate the parent/child relationship.  The ArchivesSpace importer will use those attributes to create a single parent/child instance for the box/folder.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Alternatively, you could somehow process the XML to assign @id and @parent to each container prior
 to import.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Something like:</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><container id="cid1351138" type="Box" label="Mixed materials">1</container></span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><container parent="cid1351138" type="Folder">4</container></span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">-Noah</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#404040">================</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#404040">Noah Huffman</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#404040">David M. Rubenstein Rare Book & Manuscript Library</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#404040">Duke University</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">
<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">
archivesspace_users_group-bounces@lyralists.lyrasis.org</a> [<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</a>]
<b>On Behalf Of </b>MATTHEW R FRANCIS<br>
<b>Sent:</b> Tuesday, February 24, 2015 1:02 PM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> [Archivesspace_Users_Group] EAD instance issue</span><u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><span style="color:black"> </span><u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"><span style="color:black">All,</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Sending through the listserv as the "Send Feedback" link does not properly function for our instance of ArchivesSpace and apologies in advance if this
 has already been discussed.</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">We are currently running ASpace v1.1.2 and have recently run into an issue with our EAD imports that we were not experiencing under previous versions (for
 full context we were previously running v1.0.9 before migrating to the current version).  Historically some of our workflows have relied on converting Excel collection container listings into EAD XML files through Steady (<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__steady2.herokuapp.com_&d=AwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=fsFyKgFz0gzNJ4-L054MLtQb1rGgFEE3gczfb-PzjpE&s=x4gRIBeykmbWmcy1PGsfGBnRohA7DhS5fW_X9-7VlKA&e=" target="_blank">http://steady2.herokuapp.com/</a>) and
 then importing into AT/ASpace.  This is a workflow that we would like to remain an option moving into the future.</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">However, when importing one of these XML files in v1.1.2 we noticed that when there were two sets of container tags for an archival object in our XML that
 ASpace mapped the container data as two separate instances for the archival object instead of a singular instance with two container types.  For example here is the XML data for one of the archival objects:</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> </span><u></u><u></u></p>
</div>
<div>
<p style="margin:0in;margin-bottom:.0001pt"><span style="color:black"><c02 level="file"><br>
<did><br>
<unittitle>Council Members Lists</unittitle><br>
<unitdate>undated</unitdate><br>
<container type="box" label="Text">1</container><br>
<container type="folder" label="Text">20</container><br>
</did><br>
</c02></span><u></u><u></u></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="color:black"> </span><u></u><u></u></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="color:black">And when imported into ASpace the instance is now displaying as:</span><u></u><u></u></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="color:black"> </span><u></u><u></u></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="color:black"><img border="0" width="870" height="181" src="cid:image001.png@01D050E4.CFEFF700"></span><u></u><u></u></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="color:black"> </span><u></u><u></u></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="color:black">We are not sure what has caused this change with the current version, but from our workflows/resources perspectives it presents a challenge to our collection management practices.  Would
 appreciate any information on what might be causing this, if there is a recommended alternative approach to importing this type of EAD XML data, and/or if this is something that is pipeline to be worked on.</span><u></u><u></u></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="color:black"> </span><u></u><u></u></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="color:black">Thanks for the help and information.</span><u></u><u></u></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="color:black"> </span><u></u><u></u></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="color:black">-Matt </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia","serif";color:black">Matt Francis</span><u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia","serif";color:black">Archivist for Collection Management</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia","serif";color:black">Special Collections Library<br>
Penn State University</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia","serif";color:black"> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia","serif";color:black">Twitter: @archivingmatt</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia","serif";color:black"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.archivingmatt.com&d=AwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=fsFyKgFz0gzNJ4-L054MLtQb1rGgFEE3gczfb-PzjpE&s=8jkNk2Kz0syasZhQvYf1CDyOrgxJhMu47RAgCshMVGI&e=" target="_blank">http://www.archivingmatt.com</a></span><u></u><u></u></p>
</div>
</div>
</div>
<p class="MsoNormal"><span style="font-family:"Helvetica","sans-serif";color:black"><br>
_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" target="_blank">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwMGaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=TQmmzdQt9TEtFi4MyRDTt2mXhw0lj8a26EWCdRuOp6c&s=5hIsW4eWXaYbDfNBB3mgoObf-sWyDzzqjEmvVsRbGc0&e=" target="_blank">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a></span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> </span><u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" target="_blank">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" target="_blank">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><u></u><u></u></p>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal">-- <u></u><u></u></p>
<div>
<p class="MsoNormal">Nathan Stevens<br>
Programmer/Analyst<br>
Digital Library Technology Services<br>
New York University<br>
<br>
<a href="tel:1212-998-2653" value="+12129982653" target="_blank">1212-998-2653</a><br>
<a href="mailto:ns96@nyu.edu" target="_blank">ns96@nyu.edu</a><u></u><u></u></p>
</div>
</div>
</div></div></div>
</div>

<br>_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" target="_blank">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Nathan Stevens<br>Programmer/Analyst<br>Digital Library Technology Services<br>New York University<br><br>1212-998-2653<br><a href="mailto:ns96@nyu.edu" target="_blank">ns96@nyu.edu</a></div>
</div>