Hi Jane, You might check out this Digitization Work Order plugin: https://github.com/hudmol/digitization_work_order
It's designed for a more specific use case (generating scan list spreadsheets), but generally it does what you want and once you install the plugin you can run it from within the staff interface. Only a subset of the archival object metadata is exported as TSV (titles, dates, containers, barcodes, etc.). If I remember right, it does not export notes. Alternatively, there are some XSLT scripts in the wild that can produce CSV from EAD. So, to get a spreadsheet of archival object information for a resource you can: 1) Export EAD from ASpace 2) Transform EAD with XSLT to produce CSV of archival objects Here's one that I use occasionally for roundtripping archival object metadata in ASpace: https://github.com/duke-libraries/archivesspace-duke-scripts/blob/master/xslt/aspaceEAD_to_SteadyCSV.xsl There are probably some python scripts floating around as well that use the API to create CSVs of all of the archival objects in a collection/resource. A third option would be to run an SQL query against the backend database, but I find the two options above a bit easier as you'd probably have to join lots of tables in your query to get all of the metadata you'd want in your CSV. Hope this helps, -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/ From: [email protected] <[email protected]> On Behalf Of Jane LaBarbara Sent: Wednesday, March 28, 2018 2:59 PM To: '[email protected]' <[email protected]> Subject: [Archivesspace_Users_Group] Export of archival objects / contents lists? Does anyone have a recommended way of exporting archival object information from a specific resource record in a way that results in a contents list spreadsheet? We have a lot of legacy contents list spreadsheets here, and we're working on converting and uploading them into ASpace. We don't want to have to enter data into both the spreadsheet and the ASpace record for every addendum, but we're reluctant to get rid of the spreadsheets if we can't get that information back out again in spreadsheet form should we ever need it for a future project. Thanks for your advice, Jane / Jane Metters LaBarbara Assistant Curator, West Virginia & Regional History Center<https://urldefense.proofpoint.com/v2/url?u=https-3A__wvrhc.lib.wvu.edu_&d=DwMFAg&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=F0JE8U9-xhxe_nE7d7aEUi-uqfKqvYJ222bS0oz9mko&m=OulrLuJ58_Q0dk9C7cv88I0yrxw1KVzOfUc1xLvTnWA&s=SmPrHzBegHJAbHWfH1oawTxQATcfR3ZQ2UjIDU7qAu8&e=> West Virginia University Libraries (304) 293-0352 office [email protected]<mailto:[email protected]>
_______________________________________________ Archivesspace_Users_Group mailing list [email protected] http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
