Research: Optimization For Nested Semantic Queries - Time out Issue in Advanced Search

[roamye]

Problem Description: There is a time out issue which occurs in advanced search for a query which has a small amount of results. For example, before adding another line to this query it returns 25 results. However, if we add to this query to look for results which include NO online images in objects it will have a time out issue which can be seen in the link in UAT.

This happens because the nested query does not search for online images from the 25 results, but instead it searches from all the records which have online images which causes the time out issue.

Expected Behavior/Solution: Research adding in an optimization to reduce the number of results for nested semantic queries using criteria from higher up in the query.

Example - turning this broken search into this optimized search

Other possible things that could help this problem Possible solutions from the teams thread is to:

• increase timeout
• switch to optic.
• optimize the current CTS approach by moving some of the criteria within the call to cts.triples. In this case, it meant we were no longer asking cts.triples to return over 9 million values. Note it is not necessarily a straightforward optimization, but is one we can consider. (from brents comment below)

Requirements:

• TBD based on research.

Needed for promotion: If an item on the list is not needed, it should be crossed off but not removed.

• [ ] ~Wireframe/Mockup - Mike~
• [ ] ~Committee Discussion~
• [x] Feasibility/Team discussion - Sarah
• [ ] Backend requirements - TBD
• [ ] ~Frontend requirements- TBD~
• [ ] Questions
• List of questions for discussions. Answers should be documented within the issue.

UAT/LUX Examples:

• https://lux-front-tst.collections.yale.edu/view/results/works?q=%7B%22AND%22%3A%5B%7B%22text%22%3A%22Bonaccorsi%22%2C%22_lang%22%3A%22en%22%7D%2C%7B%22publishedDate%22%3A%221500%22%2C%22_comp%22%3A%22%3C%3D%22%7D%2C%7B%22carriedBy%22%3A%7B%22isOnline%22%3A0%7D%7D%5D%7D (tst)

Dependencies/Blocks:

• Blocked By: Issues that are blocking the completion of the current issue.
• Blocking: Issues being blocked by the completion of the current issue.

Related Github Issues:

• Issues that contain similar work but are not blocking or being blocked by the current issue.

Related links:

• Teams Thread | Timeout Issue

Wireframe/Mockup: Place wireframe/mockup for the proposed solution at end of ticket.

[roamye]

should brent also be added to this issue? He was part of the original thread convo but unsure of what his workload looks like.

cc: @prowns @clarkepeterf

[brent-hartwig]

@roamye, a third possible solution was discussed (and proven). It would have us optimize the current CTS approach by moving some of the criteria within the call to cts.triples. In this case, it meant we were no longer asking cts.triples to return over 9 million values. Note it is not necessarily a straightforward optimization, but is one we can consider.