[Archivesspace_Users_Group] Batch extraction of Agent records through the API

[Kevin Clair]

Hi Eric,

At Denver we do this by passing ‘all_ids=true’ as a parameter to get the array of all records of a certain type, then iterating over the array to download each record one by one. Code: https://github.com/duspeccoll/as_utils/blob/master/reports.rb

I haven’t found another way to do it but possibly others on the list have?  -k

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Eric Hanson <ehanson8 at jhu.edu<mailto:ehanson8 at jhu.edu>>
Reply-To: Archivesspace Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Date: Friday, April 1, 2016 at 8:34 AM
To: Archivesspace Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Batch extraction of Agent records through the API

During some recent experimentation with the ArchivesSpace API, we found while that while you can use an array to remove multiple records for a DELETE request via the API, it seems like you can’t use an array with a GET request to retrieve multiple records as JSON.  Has anyone found a method for extracting multiple records through the API?

The reason we’re trying to do this is that we would like to download our Agent records and run them through an OpenRefine batch process to find potential VIAF identifiers based on the authorized name, review the VIAF identifiers for accuracy, and then push the VIAF labels and  identifiers back into the Agent records as alternate names.

Thanks!

Eric Hanson
Digital Content Metadata Specialist
The Sheridan Libraries
Johns Hopkins University
3400 North Charles Street
Baltimore, MD 21218
410-516-7756
ehanson8 at jhu.edu<mailto:ehanson8 at jhu.edu>

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