I'm not seeing it here, and AFAIK there was no change in the parameter passing -- only in the serialization code.
Are you using the curl_as | curl_as_os scripts ? ( or some other method? ) And quoting the URL or escaping the "&" as \& ? -- Steve Majewski / UVA Alderman Library ________________________________ From: [email protected] <[email protected]> on behalf of Noah Huffman <[email protected]> Sent: Tuesday, October 3, 2017 2:24:38 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] DAO tags missing from EAD exports using API? Hi Steve, 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: [email protected] [mailto:[email protected]] On Behalf Of Majewski, Steven (sdm7g) Sent: Tuesday, October 3, 2017 1:44 PM To: Archivesspace Users Group <[email protected]> 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: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of Noah Huffman <[email protected]<mailto:[email protected]>> Sent: Tuesday, October 3, 2017 12:24:04 PM To: '[email protected]' 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/
_______________________________________________ Archivesspace_Users_Group mailing list [email protected] http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
