[Archivesspace_Users_Group] DAO tags missing from EAD exports using API?
noah.huffman at duke.edu
Tue Oct 3 14:24:38 EDT 2017
So this is strange. I tried several different combinations of parameters. Now I'm getting daos, but only if I put the "include_daos=true" parameter as the first parameter in the request.
But, if I have "include_daos=true&?numbered_cs=true" I'm getting daos, but NOT numbered components like I should.
It seems like something has changed in this version that affects the order of parameters?
From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven (sdm7g)
Sent: Tuesday, October 3, 2017 1:44 PM
To: Archivesspace Users Group <Archivesspace_Users_Group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] DAO tags missing from EAD exports using API?
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<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Noah Huffman <noah.huffman at duke.edu<mailto: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?
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?
Archivist for Metadata, Systems, and Digital Records
David M. Rubenstein Rare Book & Manuscript Library
Duke University | 919-660-5982
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Archivesspace_Users_Group