[Archivesspace_Users_Group] DAO tags missing from EAD exports using API?

[Majewski, Steven (sdm7g)]

Backend API export is working for me on both 2.1.2 and current master devserver .

( I didn't currently have any digital objects with multiple file_versions that would produce daogrp/daoloc  output to test, only single file_versions -> dao. )


If I use the same params on the backend resource_descriptions  API export as the frontend export, I seem to get the same output.  Does it work for you with "include_unpublished=true" added along with "include_daos=true" ?


-- Steve Majewski / UVA Alderman Library
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Noah Huffman <noah.huffman at duke.edu>
Sent: Tuesday, October 3, 2017 12:24:04 PM
To: 'Archivesspace_Users_Group at lyralists.lyrasis.org'
Subject: [Archivesspace_Users_Group] DAO tags missing from EAD exports using API?

Hi all,

Sorry for so many subject line acronyms…

I’ve noticed that <dao> elements are no longer appearing in EAD exports that are initiated through the API in version 2.1.2, even when using the “include_daos=true” parameter in the request.  I’ve confirmed this on test.archivesspace.org

The <dao> elements do appear when exporting EAD directly from the staff interface and selecting the appropriate “include dao tags” option.

Has anyone else experienced this?

-Noah

================
Noah Huffman
Archivist for Metadata, Systems, and Digital Records
David M. Rubenstein Rare Book & Manuscript Library
Duke University | 919-660-5982
http://library.duke.edu/rubenstein/




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171003/1b865a4a/attachment.html>