It looks like your example got a little mangled along the way: I assume what’s 
between the “<…>” doesn’t belong. 
But the ‘-H’ switch sends “q:java” as a HTTP header, not as a search param, so 
with a null query string, you are asking for everything.  

Try maybe: " 

or if you want to send it as a POST instead of a GET request, use  -F or —form 

Also, when debugging search problems, it’s sometimes handy to go directly to 
the Solr console at port 8090, if you’re using the default Solr settings in 

— Steve.

> On Feb 14, 2018, at 11:45 AM, Tang, Lydia <> wrote:
> Good morning, all!
> I have a mystery…  My institution is trying to pull from the API to integrate 
> the results in our search discovery interface of our catalog.  The mystery is 
> that apparently, our API call seems to bring back bogus results whereas if we 
> scrape from the HTML of the PUI, the search results are as expected.
> Here is the API call
> curl -H "X-ArchivesSpace-Session: 
> c3a1ea6a48af5e9324a19bf1e79d284b921cbc97aed93b143d76b6b457f5b144 " -H 
> "q:java"   
> "<>
> <>"
> If you look closely I’m searching for java and I want the 1st page with 5 
> results

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Archivesspace_Users_Group mailing list

Reply via email to