[Archivesspace_Users_Group] setting encodinganalog and other attributes related to XML export

[Custer, Mark]

Dear Amanda,

There's no way to do this in the staff interface.

This 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.

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.

Mark


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Amanda Focke <afocke at rice.edu>
Sent: Wednesday, September 2, 2020 5:16 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] setting encodinganalog and other attributes related to XML export

Hello -

Is there a way in ArchivesSpace to set encodinganalog information and
other attributes for XML export purposes, such as for basic notes like
scopecontent, acqinfo,and accessrestrict?


Thanks for any thoughts,

Amanda

--
Amanda Focke, CA, DAS
Head of Woodson Research Center
Fondren Library
Rice University
6100 Main St. MS-44
Houston, TX 77005
afocke at rice.edu | 713-348-2124
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
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20201011/a65b9b35/attachment.html>