ArchivesSpace EAD outputs have invalid "ns2" namespace references (imported from Archivists' Toolkit-era finding aids)

Description

Hi ASpace team,

We're writing to re-open an EAD validation issue that our colleagues at UCI Library Special Collections & Archives have noticed. It appears to be a long-standing bug, related to this older JIRA ticket:

https://archivesspace.atlassian.net/browse/AR-978

In a nutshell, Archivists' Toolit-era EADs that were imported into ASpace have vestigal "ns2" namespace references, pre-pended to various EAD tag attributes. When those EADs were imported into ASpace, those vestigal "ns2"'s were carried over into ASpace – and they come through the EADs exported from ASpace. This is producing validation errors, as the root <ead> tag doesn't declare the "ns2" namespace.

Example references, provided below.

Can the ASpace EAD output be updated to include that namespace – or alternatively, provide a solution to bulk delete those "ns2" references within Resource records (without having to programmatically work directly with the raw data, in the backend database)?

Many institutions such as UCI Library imported or migrated legacy Archivists' Toolkit-era finding aids into ASpace, years ago – so it's not really an option to go back and clean up the data prior to import.

Thanks!

– Adrian

__________________________________________

Adrian Turner
Senior Product Manager
California Digital Library
(510) 287-3390
adrian.turner@ucop.edu
http://www.cdlib.org

==

[#1] Version of EAD, as exported from Archivists' Toolkit
https://voro.cdlib.org/oac-dav/uci/spcoll/r88.xml

[#2] Successfully imported result of #1 in ASpace 2.6.0 sandbox
http://sandbox.archivesspace.org/resources/10#tree::resource_10

[#3] Version of EAD, as exported from ASpace 2.6.0 sandbox (see attached)

Environment

None

Status

Assignee

Unassigned

Reporter

Adrian Turner

Affects versions

2.6.0

Priority

Major
Configure