<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Dear Amanda,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
There's no way to do this in the staff interface. </div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
T<span style="color: rgb(0, 0, 0); font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; background: var(--white);">his could be accomplished with a plugin, however. Alternatively, you could add a transformation step after extracting the EAD
file from ArchivesSpace. At Yale, we rely on both approaches. I will usually only take the plugin approach when the data would not be available otherwise (e.g. changing how the default ASpace EAD export handles creators linked as "sources"), since I find
there is a lot more flexibility if you keep local transformations separate from the serialization process. So, in this case, if these attributes are required, and if you have the ability to modify the files after they are exported, then I would recommend adding
those sorts of transformation rules to a publication process outside of ArchivesSpace. If either of those approaches are possible to add on your end, though, then I could provide a brief proof-of-concept for how to do that.</span></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
All that said, I'm curious if you can say more about how you use the encodinganalog attribute right now? In my experience, people primarily use @encodinganalog in EAD to illustrate mappings to the MARC standard, following the examples in the EAD Tag Library
and EAD Cookbook, while at the same time, perhaps, keeping archival encodings in the shadow of MARC AMC. I'd be in favor of removing this attribute (and @relatedencoding) from future versions of EAD (it's not something I've seen in other schemas like MODS,
TEI, etc.), so I am especially curious on how it's being used. </div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Mark</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of Amanda Focke
<afocke@rice.edu><br>
<b>Sent:</b> Wednesday, September 2, 2020 5:16 PM<br>
<b>To:</b> Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Subject:</b> [Archivesspace_Users_Group] setting encodinganalog and other attributes related to XML export</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Hello -<br>
<br>
Is there a way in ArchivesSpace to set encodinganalog information and <br>
other attributes for XML export purposes, such as for basic notes like <br>
scopecontent, acqinfo,and accessrestrict?<br>
<br>
<br>
Thanks for any thoughts,<br>
<br>
Amanda<br>
<br>
-- <br>
Amanda Focke, CA, DAS<br>
Head of Woodson Research Center<br>
Fondren Library<br>
Rice University<br>
6100 Main St. MS-44<br>
Houston, TX 77005<br>
afocke@rice.edu | 713-348-2124<br>
<a href="https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Flibrary.rice.edu%2Fwoodson&data=02%7C01%7Cmark.custer%40yale.edu%7Ca1fa02bd727d4194035208d84f858522%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637346782189707991&sdata=e40zvKllsFpWYFvIxbhuUbFZcHH0v3PQ9vAlfxAcLYg%3D&reserved=0">https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Flibrary.rice.edu%2Fwoodson&data=02%7C01%7Cmark.custer%40yale.edu%7Ca1fa02bd727d4194035208d84f858522%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637346782189707991&sdata=e40zvKllsFpWYFvIxbhuUbFZcHH0v3PQ9vAlfxAcLYg%3D&reserved=0</a><br>
_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
Archivesspace_Users_Group@lyralists.lyrasis.org<br>
<a href="https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=02%7C01%7Cmark.custer%40yale.edu%7Ca1fa02bd727d4194035208d84f858522%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637346782189707991&sdata=lTW803fCRY31M63I3CAGD%2FIFOnh2M9kJWKfz0TqJgPM%3D&reserved=0">https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=02%7C01%7Cmark.custer%40yale.edu%7Ca1fa02bd727d4194035208d84f858522%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637346782189707991&sdata=lTW803fCRY31M63I3CAGD%2FIFOnh2M9kJWKfz0TqJgPM%3D&reserved=0</a><br>
</div>
</span></font></div>
</body>
</html>