[Archivesspace_Users_Group] EAD export not including dao tags

Seth Shaw seth.shaw at unlv.edu
Thu Mar 15 14:23:11 EDT 2018

Okay, this is beginning to be like the boy who cried wolf. Please disregard
my last email. Another local plugin that I somehow didn't notice on my
first look for a culprit. (A fresh install worked properly and prompted
another look.)

On Thu, Mar 15, 2018 at 10:56 AM, Seth Shaw <seth.shaw at unlv.edu> wrote:

> Using 2.3.1, I created a digital object instance for an archival object
> however the resource's EAD export is not including the dao tag.
> I've ensured that the "Include <dao> tags" option IS selected (I tested
> both on and off, just to be sure). The archival object, all parents, and
> the digital object are set to publish. I've included relevant screenshots
> below.
> Using the EAD3 *does* include the dao tag but produces an unrelated error
> (for the curious, in place of the abstract we get an error stating "incompatible
> encoding regexp match (UTF-8 regexp with ASCII-8BIT string)") so the
> problem is certainly with the EAD 2002 export. It is a problem because the
> PDF export relies on the EAD 2002 export.
> Anyone else running into this?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20180315/e2402b98/attachment.html>

More information about the Archivesspace_Users_Group mailing list