<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""></div>There is only one index for staff and pui.<div class=""><br class=""></div><div class="">From memory the ids of the pui docs have #pui appended.</div><div class=""><br class=""></div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Nov 8, 2019, at 11:13 AM, Seth Shaw <<a href="mailto:seth.shaw@unlv.edu" class="">seth.shaw@unlv.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">That might be it. We don't use the PUI for patron access; but we do still have it left on as the staff occasionally look at it. Certainly something to investigate.<div class=""><br class=""></div><div class="">Regardless, either the API should use <i class="">one</i> index consistently, have a documented filter (I don't see one there) and/or give some other obvious indication as to where a result came from.</div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Nov 8, 2019 at 8:02 AM James Bullen <<a href="mailto:james@hudmol.com" class="">james@hudmol.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;" class=""><div class=""><br class=""></div>Hi Seth,<div class=""><br class=""></div><div class="">I’m not seeing that. Could it be you’re seeing pui docs as well - the instance I’m testing on has the pui turned off.<br class=""><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Cheers,</div><div class="">James</div><div class=""><br class=""></div><div class=""><br class=""><blockquote type="cite" class=""><div class="">On Nov 8, 2019, at 10:51 AM, Seth Shaw <<a href="mailto:seth.shaw@unlv.edu" target="_blank" class="">seth.shaw@unlv.edu</a>> wrote:</div><br class=""><div class=""><div dir="ltr" class="">James, I was hoping using the filter as you described would remove the duplicate results issue I was having by using the advanced query compound search; but I'm seeing the same thing as before. <div class=""><br class=""></div><div class="">Running the search via the API: 'archivestest:8089/search?type[]=archival_object&page=1&filter={"query":{"comparator":"greater_than","field":"system_mtime","value":"2019-10-02","jsonmodel_type":"date_field_query"}}' returns, in part, `{"page_size":10,"first_page":1,"last_page":874,"this_page":1,"offset_first":1,"offset_last":10,"total_hits":8732,` ...</div><div class=""><br class=""></div><div class="">Whereas the SQL query `SELECT count(*) FROM archival_object WHERE system_mtime > '2019-10-02';` is returning "4369" (half the results of the REST query).</div><div class=""><br class=""></div><div class="">Have you run into this issue before?<div class=""><br class=""></div><div class=""><br class=""></div></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Nov 8, 2019 at 7:34 AM James Bullen <<a href="mailto:james@hudmol.com" target="_blank" class="">james@hudmol.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class=""><div class=""><br class=""></div>Something like this works for me:<div class=""><br class=""></div><div class="">/search type[]=resource type[]=archival_object page=1 filter={"query":{"comparator":"greater_than","field":"system_mtime","value":"2019-10-02","jsonmodel_type":"date_field_query"}}<br class=""><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><blockquote type="cite" class=""><div class="">On Nov 8, 2019, at 10:24 AM, Seth Shaw <<a href="mailto:seth.shaw@unlv.edu" target="_blank" class="">seth.shaw@unlv.edu</a>> wrote:</div><br class=""><div class=""><div dir="ltr" class="">To do this you need to use the advanced query parameter which, unfortunately, is not well documented. There are a few email threads that describe using the advanced search though:<div class=""><br class=""></div><div class=""><a href="http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2015-June/001734.html" target="_blank" class="">http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2015-June/001734.html</a></div><div class=""><div class=""><br class=""></div><div class="">I've formulated queries like you describe before (I'll have to dig through my notes to see if I can find it again); but the result set was consistently giving me back duplicate results for some unknown reason; so I stopped using it. </div></div><div class=""><br class=""></div><div class="">Ideally, we would be able to add a 'modified_since' parameter to each entity's endpoint to get the most recent set. The capability exists in the code, but hasn't been exposed to the REST end-point. I've submitted a ticket that will hopefully lead to this being resolved: <a href="https://archivesspace.atlassian.net/browse/ANW-962?filter=-2" target="_blank" class="">https://archivesspace.atlassian.net/browse/ANW-962?filter=-2</a>.</div><div class=""><br class=""></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Nov 8, 2019 at 7:07 AM Steve Mattison <<a href="mailto:smattiso@nd.edu" target="_blank" class="">smattiso@nd.edu</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr" class=""><a href="https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=archivesspace_users_group@lyralists.lyrasis.org" style="font-family:Times;font-size:inherit" target="_blank" class=""></a><div class="">Community,</div><div class=""><br class=""></div><div class="">I'm new to using ArchivesSpace, and new to using the AS API. I need to use the API to search within a given repository to find records that have been modified after a particular time (e.g. modified within the last 48 hours). (We then want to export metadata related to those resources or archival_objects for a project we're working on.)</div><div class=""><br class=""></div><div class="">I have found the documentation for <a href="http://archivesspace.github.io/archivesspace/api/?shell#search-this-repository" target="_blank" class="">search-this-repository</a>, but don't know how to formulate a query to find all resources and/or archival_objects where the system_mtime is after a particular time. I would be fine with performing two searches, one for resources and one for archival_objects, if that is required.</div><div class=""><br class=""></div><div class="">Any help with the syntax for the query would be much appreciated.</div><div class=""><br class=""></div><div class="">Thanks for your help.</div><div class=""><div class=""><br class=""></div>-- <br class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class=""><b class=""><font face="arial, sans-serif" class="">Steve Mattison</font></b><div class=""><i class=""><font face="arial, sans-serif" class="">Lead Software Engineer, Digital Library Technologies</font></i></div><div class=""><i class=""><font face="arial, sans-serif" class="">Hesburgh Libraries</font></i></div><div class=""><i class=""><font face="arial, sans-serif" class=""><br class=""></font></i><div class=""><div class=""><b class=""><font face="arial, sans-serif" class="">University of Notre Dame</font></b></div><div class=""><font face="arial, sans-serif" class="">271 Hesburgh Library</font></div><div class=""><font face="arial, sans-serif" class="">Notre Dame, IN 46556-5629</font></div><div class=""><font face="arial, sans-serif" class=""><b class="">o:</b> 574-631-8559</font></div><div class=""><font face="arial, sans-serif" class=""><b class="">e: </b><a href="mailto:steve.mattison@nd.edu" style="color:rgb(17,85,204)" target="_blank" class="">steve.mattison@nd.edu</a></font></div></div></div></div><div class=""><font face="arial, sans-serif" class=""><br class=""></font></div><div class=""><font face="arial, sans-serif" class=""><img src="https://docs.google.com/uc?export=download&id=1eLUXKKJMijoIFzQtpJutmM1uLHON9ZDt&revid=0B-gl36FdlSuTV2ZPM1NBek5HamNiOWN1UllhT3d2VWtCU3hjPQ" class=""></font></div></div></div></div></div></div></div></div></div></div></div>
_______________________________________________<br class="">
Archivesspace_Users_Group mailing list<br class="">
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" target="_blank" class="">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br class="">
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank" class="">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br class="">
</blockquote></div>
_______________________________________________<br class="">Archivesspace_Users_Group mailing list<br class=""><a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" target="_blank" class="">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br class=""><a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" target="_blank" class="">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br class=""><br class=""><br class=""><br class=""></div></blockquote></div><br class=""></div></div>_______________________________________________<br class="">
Archivesspace_Users_Group mailing list<br class="">
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" target="_blank" class="">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br class="">
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank" class="">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br class="">
</blockquote></div>
!DSPAM:5dc58f16257571993821028!
_______________________________________________<br class="">Archivesspace_Users_Group mailing list<br class=""><a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" target="_blank" class="">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br class=""><a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" target="_blank" class="">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br class=""><br class=""><br class="">!DSPAM:5dc58f16257571993821028!<br class=""></div></blockquote></div><br class=""></div></div>_______________________________________________<br class="">
Archivesspace_Users_Group mailing list<br class="">
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" target="_blank" class="">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br class="">
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank" class="">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br class="">
</blockquote></div>
!DSPAM:5dc59426273611268720720!
_______________________________________________<br class="">Archivesspace_Users_Group mailing list<br class=""><a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" class="">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br class="">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<br class=""><br class=""><br class="">!DSPAM:5dc59426273611268720720!<br class=""></div></blockquote></div><br class=""></div></body></html>