<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div>Mark,<br></div><div><br></div><div>Thank you so much for providing this, as it does provide us an effective work around for our current workflow issues. I also have to say this whole conversation has been fascinating to follow, and seeing that we are not the only community member who has made extensive use of Steady I do hope that there will be an opportunity to further align these tools. </div><div><br></div><div>Thanks again for the help, it is greatly appreciated.</div><div><br></div><div>-Matt</div><div><br></div><div><span></span><span style="font-family: georgia, serif; font-size: small;">Matt Francis</span><div><span style="font-family: georgia, serif; font-size: small;">Archivist for Collection Management</span></div><div><span style="font-family: georgia, serif; font-size: small;">Special Collections Library<br>Penn State University</span></div><div><span style="font-family: georgia, serif; font-size: small;"><br></span></div><div><span style="font-family: georgia, serif; font-size: small;">Twitter: @archivingmatt</span></div><div><span style="font-family: georgia, serif; font-size: small;">http://www.archivingmatt.com</span></div><span></span><br></div><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Mark Custer" <mark.custer@yale.edu><br><b>To: </b>"Archivesspace Users Group" <archivesspace_users_group@lyralists.lyrasis.org><br><b>Sent: </b>Tuesday, February 24, 2015 8:49:42 PM<br><b>Subject: </b>Re: [Archivesspace_Users_Group] EAD instance issue<br><div><br></div>
<style>
<!--
@font-face
{font-family:Helvetica}
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
@font-face
{font-family:Georgia}
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
{color:blue;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline}
p
{margin-right:0in;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif}
span.EmailStyle18
{font-family:"Calibri",sans-serif;
color:#1F497D}
span.EmailStyle19
{font-family:"Calibri",sans-serif;
color:#1F497D}
.MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
-->
</style><style id="owaParaStyle"></style>
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Matt,
<div><br>
</div>
<div>Here's another option in the interim. You could transform the EAD output from Steady with the following XSLT 1.0 file, which will add @id and @parent attributes if those aren't already present in the EAD so that the ASpace importer will pick them up as
a single "container group":</div>
<div><br>
</div>
<div>
<div><?xml version="1.0" encoding="UTF-8"?></div>
<div><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"</div>
<div> xmlns:xlink="http://www.w3.org/1999/xlink"</div>
<div> xmlns:ead="urn:isbn:1-931666-22-9"</div>
<div> version="1.0"></div>
<div> </div>
<div> <!--standard identity template, which does all of the copying--></div>
<div> <xsl:template match="@*|node()"></div>
<div> <xsl:copy></div>
<div> <xsl:apply-templates select="@*|node()"/></div>
<div> </xsl:copy></div>
<div> </xsl:template></div>
<div> </div>
<div> <!--adds an @id attribute to the first container element that doesn't already have an @id or @parent attribute--></div>
<div> <xsl:template match="ead:container[not(@id|@parent)][1]"></div>
<div> <xsl:copy></div>
<div> <xsl:attribute name="id"></div>
<div> <xsl:value-of select="generate-id()"/></div>
<div> </xsl:attribute></div>
<div> <xsl:apply-templates select="@*|node()"/></div>
<div> </xsl:copy></div>
<div> </xsl:template></div>
<div> </div>
<div> <!--adds a @parent attribute to the following container elements that don't already have an @Id or @parent attribute--></div>
<div> <xsl:template match="ead:container[not(@id|@parent)][position() > 1]"></div>
<div> <xsl:copy></div>
<div> <xsl:attribute name="parent"></div>
<div> <xsl:value-of select="generate-id(../ead:container[not(@id|@parent)][1])"/></div>
<div> </xsl:attribute></div>
<div> <xsl:apply-templates select="@*|node()"/></div>
<div> </xsl:copy></div>
<div> </xsl:template></div>
<div> </div>
<div></xsl:stylesheet></div>
<div><br>
</div>
<div>If you have any issues getting this solution to work, just let me know. I just did a quick test, but with the following input:</div>
<div><br>
</div>
<div>
<div> <did></div>
<div> <unittitle>Council Members Lists</unittitle></div>
<div> <unitdate>undated</unitdate></div>
<div> <container type="box" label="Text">1</container></div>
<div> <container type="folder" label="Text">20</container></div>
<div> </did></div>
</div>
<div><br>
</div>
<div>Here's the output that the above transformation supplied for me:</div>
<div><br>
</div>
<div>
<div> <did></div>
<div> <unittitle>Council Members Lists</unittitle></div>
<div> <unitdate>undated</unitdate></div>
<div> <container id="d1e109" type="box" label="Text">1</container></div>
<div> <container parent="d1e109" type="folder" label="Text">20</container></div>
<div> </did></div>
</div>
<div><br>
</div>
<div><span style="font-size: 13.3333330154419px;">That "d1e109" value will likely be different, but it should always be a unique value within the file, and the value really won't matter; it's just needed to group the containers.</span></div>
<div><span style="font-size: 13.3333330154419px;"><br>
</span></div>
<div><span style="font-size: 13.3333330154419px;">I hope that helps,</span></div>
<div><span style="font-size: 13.3333330154419px;"><br>
</span></div>
<div><span style="font-size: 13.3333330154419px;">Mark</span></div>
<div><span style="font-size: 13.3333330154419px;"><br>
</span></div>
<div><br>
</div>
<div><br>
</div>
<div><span style="font-size: 13.3333330154419px;"><br>
</span></div>
<div><span style="font-size: 13.3333330154419px;"><br>
</span></div>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr>
<div id="divRpF315989" style="direction: ltr;"><span style="color: #000000; font-family: Tahoma; font-size: small;"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org [archivesspace_users_group-bounces@lyralists.lyrasis.org] on behalf of Custer, Mark [mark.custer@yale.edu]<br>
<b>Sent:</b> Tuesday, February 24, 2015 2:58 PM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] EAD instance issue<br>
</span><br>
</div>
<div></div>
<div>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D">All,</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span></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></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span></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></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:black"> </span></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=PFwumEcW50QlHdQTKuDJyESPPx1BuZfohYxwCKJ7E-k&s=KLI_7Degdg7EGUPNgHdelyCIZdG_ELV0lvihQM7I3r8&e=" target="_blank">
http://www.loc.gov/ead/tglib/elements/container.html</a>)</span><span style="font-size:10.0pt; font-family:"Calibri",sans-serif; color:#1F497D"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span></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></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D">All my best,</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D">Mark</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span></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"> archivesspace_users_group-bounces@lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org]
<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></p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal"><span style="color:black">Noah,</span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> </span></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></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Cheers and thanks again.</span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">-Matt</span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia",serif; color:black">Matt Francis</span><span style="color:black"></span></p>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia",serif; color:black">Archivist for Collection Management</span><span style="color:black"></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia",serif; color:black">Special Collections Library<br>
Penn State University</span><span style="color:black"></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia",serif; color:black"><br>
<br>
</span><span style="color:black"></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia",serif; color:black">Twitter: @archivingmatt</span><span style="color:black"></span></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=PFwumEcW50QlHdQTKuDJyESPPx1BuZfohYxwCKJ7E-k&s=ucWmqmxEfGElNa2bswKf77KGcRG2BjF_csblAOLJVsk&e=" target="_blank">http://www.archivingmatt.com</a></span><span style="color:black"></span></p>
</div>
<p class="MsoNormal"><span style="color:black"> </span></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="color:black">
<hr size="2" width="100%" align="center" id="zwchr">
</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></p>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica",sans-serif; color:black"> </span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D">Hi Matthew,</span><span style="color:black"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span><span style="color:black"></span></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><span style="color:black"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span><span style="color:black"></span></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><span style="color:black"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span><span style="color:black"></span></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><span style="color:black"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span><span style="color:black"></span></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><span style="color:black"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span><span style="color:black"></span></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><span style="color:black"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span><span style="color:black"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D">Something like:</span><span style="color:black"></span></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><span style="color:black"></span></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><span style="color:black"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span><span style="color:black"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D">-Noah</span><span style="color:black"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span><span style="color:black"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#404040">================</span><span style="color:black"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#404040">Noah Huffman</span><span style="color:black"></span></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><span style="color:black"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#404040">Duke University</span><span style="color:black"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span><span style="color:black"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span><span style="color:black"></span></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><span style="color:black"></span></p>
</div>
</div>
<p class="MsoNormal"><span style="color:black"> </span></p>
<div>
<div>
<p class="MsoNormal"><span style="color:black">All,</span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> </span></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></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> </span></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></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> </span></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></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> </span></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></p>
<p style="margin:0in; margin-bottom:.0001pt"><span style="color:black"> </span></p>
<p style="margin:0in; margin-bottom:.0001pt"><span style="color:black">And when imported into ASpace the instance is now displaying as:</span></p>
<p style="margin:0in; margin-bottom:.0001pt"><span style="color:black"> </span></p>
<p style="margin:0in; margin-bottom:.0001pt"><span style="color:black"><img id="_x0000_i1026" src="cid:image001.png@01D05040.73508450" height="181" width="870" border="0"></span></p>
<p style="margin:0in; margin-bottom:.0001pt"><span style="color:black"> </span></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></p>
<p style="margin:0in; margin-bottom:.0001pt"><span style="color:black"> </span></p>
<p style="margin:0in; margin-bottom:.0001pt"><span style="color:black">Thanks for the help and information.</span></p>
<p style="margin:0in; margin-bottom:.0001pt"><span style="color:black"> </span></p>
<p style="margin:0in; margin-bottom:.0001pt"><span style="color:black">-Matt </span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia",serif; color:black">Matt Francis</span><span style="color:black"></span></p>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia",serif; color:black">Archivist for Collection Management</span><span style="color:black"></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia",serif; color:black">Special Collections Library<br>
Penn State University</span><span style="color:black"></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia",serif; color:black"> </span><span style="color:black"></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia",serif; color:black">Twitter: @archivingmatt</span><span style="color:black"></span></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><span style="color:black"></span></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=PFwumEcW50QlHdQTKuDJyESPPx1BuZfohYxwCKJ7E-k&s=Nq50GY02r5ahg0nGUDGH2KMc4NXiamSMcjrH6OeLIec&e=" target="_blank">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> </span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>_______________________________________________<br>Archivesspace_Users_Group mailing list<br>Archivesspace_Users_Group@lyralists.lyrasis.org<br>http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<br></div><div><br></div></div></body></html>