[Archivesspace_Users_Group] Question Regarding the REST API batch_imports Operation

James R Griffin III jrg5 at princeton.edu
Thu May 7 10:44:05 EDT 2020

I am terribly sorry, I have now found that the payload is a JSON serialization of an array of  resource objects: https://github.com/archivesspace/archivesspace/blob/master/backend/spec/controller_batch_import_spec.rb#L41

Would one then model the payload as one of these arrays of JSON objects, each with a URI internal to the EAD file?
From: James R Griffin III
Sent: Thursday, May 7, 2020 10:30 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Question Regarding the REST API batch_imports Operation

Hello Everyone,

I have recently been reviewing the documentation for the REST API, and was looking to explore the possible usage of https://archivesspace.github.io/archivesspace/api/#import-a-batch-of-records

Please forgive for my ignorance, but does the body of the POST request contain a payload of EAD XML? Would this be a string of concatenated EAD documents?

Additionally, my understanding is that the response from this request contains an identifier for the created object. As the job for importing the records would be asynchronous, should one poll for the status of this new object by repeatedly transmitting a GET request against https://archivesspace.github.io/archivesspace/api/#find-resources-by-their-identifiers until it has been fully imported?

Thank you for your patience and assistance.




James R. Griffin III

Digital Infrastructure Developer

Princeton University Library<https://library.princeton.edu/>

Princeton, NJ 08544

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200507/3c306e1b/attachment.html>

More information about the Archivesspace_Users_Group mailing list