<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)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 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;}
/* 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.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
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:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle21
{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">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Hi Adrien,<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">The UCSD EAD stylesheets are here:
<a href="https://github.com/mdpeters/EAD_stylesheets">https://github.com/mdpeters/EAD_stylesheets</a>. You’ll see the ead_to_csv template (as well as some local-use stuff).<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">The ead to csv script is just an XSLT script, you can use it with any XSLT 2.0 capable processor. Matt Peters, who create it, has tied it into our ASpace export tool but that’s not necessary for its use. This
allows archivists and processors, whenever they want to “harvest” a container list, to simply run a command from the command line and basically pull a container list straight from ASpace into a CSV (and from there, Excel). It’s really useful, especially for
fixing weird legacy finding aids. We do the fixing in Excel and then re-import the updated container list with a stub of dummy front matter, and merge it into the parent resource record from whence it came (and delete the old stuff).<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">Laurel<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> archivesspace_users_group-bounces@lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org]
<b>On Behalf Of </b>Hilton, Adrien<br>
<b>Sent:</b> Monday, September 10, 2018 1:34 PM<br>
<b>To:</b> Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Issue with importing EAD into ArchivesSpace: <unittitle> elements with ID attributes<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi Laurel, <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This is probably a dumb question, but what mechanism do you use to convert the EAD to CSV. That would be helpful for me as well.
<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">Adrien<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">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>>
<b>On Behalf Of </b>McPhee, Laurel<br>
<b>Sent:</b> Monday, September 10, 2018 3:14 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] Issue with importing EAD into ArchivesSpace: <unittitle> elements with ID attributes<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Hi Jeff,<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">Other folks might have smarter solutions than I (or more directly answer to why this is happening) but I would suggest this work-around:<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">Don’t round-trip your whole finding aids (export, add data, re-import). I would do the following: take your exported EAD files, convert them to CSV, make sure the new ID elements you want are in a column of the
CSV. Then, take that CSV file, using the ASpace-generated item or folder-level REFIDs as “hooks,” to make ASpace generate the ID attribute you want directly in the resource record via the API. We haven’t done that exact task, so I can’t promise it would work,
but we’ve done very similar things (mass additions/creations of data and linking of digital objects) to records using CSVs and the API. Takes some scripting knowledge, and familiarity with using the API—but it sounds like you have that ability.<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">Hope this is helpful, let me know off-list if you need more details.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Laurel<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b>Laurel McPhee<o:p></o:p></b></p>
<p class="MsoNormal">Supervisory Archivist, Special Collections & Archives Program<o:p></o:p></p>
<p class="MsoNormal">UC San Diego Library | <span style="font-size:10.0pt;font-family:Wingdings">
(</span><span style="font-size:10.0pt"> </span>858-534-5619 |<span style="font-size:10.0pt">
</span><span style="font-size:10.0pt;font-family:Wingdings">*</span><span style="font-size:10.0pt">
</span><a href="mailto:lmcphee@ucsd.edu">lmcphee@ucsd.edu</a><o:p></o:p></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>Suszczynski, Jeffrey<br>
<b>Sent:</b> Monday, September 10, 2018 11:54 AM<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] Issue with importing EAD into ArchivesSpace: <unittitle> elements with ID attributes<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hello, all – <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’ve searched through the listserv archives and didn’t find anything directly related to the issue I am about to describe; apologies in advance if I’ve missed something and this topic has already been discussed.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">At the University of Rochester, we have some finding aids that I’ve programmatically exported from ArchivesSpace, then modified, adding the attribute ‘ID’ to our <unittitle> elements so that we can use unique identifiers as a means of linking
from our finding aids to digital objects in our instance of Islandora… <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">From everything that I can see, this ID attribute for <unittitle> is valid EAD, and the XML does, in fact, validate in oXygen when I test. However, when I import the finding aid into ArchivesSpace using either the API or the web admin
interface of ArchivesSpace, the EAD imports but the ID attributes are stripped out. I discovered this when later exporting the finding aid (either via the web admin interface or the API) – all of the <unittitle> elements were intact, but no longer had ID
attributes… I’ve tried several tactics in attempts to preserve those ID attributes, thus far to no avail.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Is there a configuration tweak or workaround that anyone is using to accomplish something similar? It seems strange that ArchivesSpace would silently remove valid EAD attributes upon import, so hopefully this is something with an obvious
solution that I’ve overlooked somehow.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Many thanks in advance for any ideas you may have!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Jeff<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Jeff Suszczynski<o:p></o:p></p>
<p class="MsoNormal">Web Developer, River Campus Libraries<o:p></o:p></p>
<p class="MsoNormal">University of Rochester<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>
</body>
</html>