<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">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?
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Eric Hanson<o:p></o:p></p>
<p class="MsoNormal">Digital Content Metadata Specialist<o:p></o:p></p>
<p class="MsoNormal">The Sheridan Libraries<o:p></o:p></p>
<p class="MsoNormal">Johns Hopkins University<o:p></o:p></p>
<p class="MsoNormal">3400 North Charles Street<o:p></o:p></p>
<p class="MsoNormal">Baltimore, MD 21218<o:p></o:p></p>
<p class="MsoNormal">410-516-7756<o:p></o:p></p>
<p class="MsoNormal">ehanson8@jhu.edu<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>