[Archivesspace_Users_Group] Unpublished URI appearing in EAD 2002 export from 3.4.1

[Michael G Olson]

Hi Brian,

Thanks for the information and confirmation that it is a feature.  I would like to start a discussion about the potential of putting in a request that this be optional for EAD output.  That said, it makes perfect sense why some institutions would want this feature.

We discovered the URIs while test loading a EAD2002 on the Online Archive of California test server.  I'm curious if other OAC contributors have noticed similar?

In the meantime, we might version back to 3.3.1 for production to avoid the URIs displaying via OAC.  We want to avoid having our Archivists strip out the URIs as a workflow step if at all possible.

As always the communities thoughts on this topic are appreciated.

best,

Michael
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Brian Harrington <brian.harrington at lyrasis.org>
Sent: Thursday, October 26, 2023 9:17 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Unpublished URI appearing in EAD 2002 export from 3.4.1


Hi Michael,



This was added in 3.4.0 (see https://archivesspace.atlassian.net/browse/ANW-1489).  I don’t think that there is an option to turn it off.



I hope this helps.



Brian



--

Brian Harrington (he/him)

Data Migration Specialist

Lyrasis

brian.harrington at lyrasis.org



From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Michael G Olson <mgolson at stanford.edu>
Date: Wednesday, October 25, 2023 at 8:09 PM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Unpublished URI appearing in EAD 2002 export from 3.4.1

Hi All,



Stanford Libraries is upgrading its ArchivesSpace server from 2.6 to 3.4.1.  In our testing we’ve found that our exported EAD 2002 the  aspace_uri tag gets made public. We didn’t see this before when we exported ead2002 from version 2.6.  Is this expected behavior?  Are there some settings we’re missing.



Thank you,



Michael Olson







____________



Michael Olson

Service Manager, Born-Digital Preservation Lab

Stanford Libraries
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20231026/4d4e263b/attachment.html>