<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: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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma",sans-serif;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma",sans-serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">I really like the approach taken by Michigan for this. Check out the “Creating Subjects and Agents” section that Dalles Pillen describes:
<a href="http://archival-integration.blogspot.com/2015/09/the-archivesspace-api.html">
http://archival-integration.blogspot.com/2015/09/the-archivesspace-api.html</a><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">In fact, I’d love if this tactic was added to the default ASpace EAD importer/exporter. The only change I’d suggest would be parking the ArchivesSpace linked record ID (e.g. /subjects/1746/”) in an altrender
element, just to keep the EAD valid (but still stealthy </span><span style="font-family:Wingdings;color:#1F497D">J</span><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">Mark<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">p.s. with EAD3, there will be a less hacky way to do this, with part elements. But even then, using the ASpace IDs in the import/export couldn’t hurt during the time that you’re using ASpace as your metadata
management system.<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>
<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>Brian Thomas<br>
<b>Sent:</b> Thursday, 12 May, 2016 3:12 PM<br>
<b>To:</b> archivesspace_users_group@lyralists.lyrasis.org<br>
<b>Subject:</b> [Archivesspace_Users_Group] Structuring ead subject terms in ead for import<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I am looking for a way to import the index terms as part of an ead finding aid where the DACS-compliant -- can be manipulated/replaced in a way that creates a subdivision instead of importing as a single line. (i.e. subject--subdivision1--subdivision2
imports in the same way as if I had created it in ArchivesSpace directly.) Not everything is in marcXML, so that is not an option, and I would like to avoid going back and manually correcting every subject term.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Suggestions?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Brian Thomas<o:p></o:p></p>
<p class="MsoNormal">Electronic Records Specialist<o:p></o:p></p>
<p class="MsoNormal">Texas State Library and Archives Commission<o:p></o:p></p>
<p class="MsoNormal">1201 Brazos Street<o:p></o:p></p>
<p class="MsoNormal">Austin, TX 78701<o:p></o:p></p>
<p class="MsoNormal">PH: (512) 475-3374<o:p></o:p></p>
<p class="MsoNormal">e-mail: <a href="bthomas@tsl.texas.gov">bthomas@tsl.texas.gov</a><o:p></o:p></p>
<p class="MsoNormal"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__tsl.texas.gov_&d=AwMFAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=s7ciGQfUJeaV_ryx908hbeXDoU9aqDwDN0Z0VbfsJ3Y&m=4gXBXD2jLww1n7MWZNJUOEcJDSQ60BtRQVi4z4I6A3w&s=aDGAcVcmmQi0dkwLkxXducLqGPp39OuD5ZJr1xdpowQ&e=">tsl.texas.gov</a><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"><img border="0" width="60" height="72" id="Picture_x0020_1" src="cid:image001.png@01D1AC62.6F3D35F0" alt="cid:image001.jpg@01D029A2.37194C70"></span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>