brent-hartwig
commented
7 months ago [!NOTE] The optimization identified herein was invalidated for this query (and YCBA's IRI was accidentally used twice). For more info, see this comment.
@roamye and @clarkepeterf,
Two responses:
- Was this criteria created using the advanced search form? As shown below, the IDs are missing the leading portion:
https://lux.collections.yale.edu/data/.
{
"AND":[
{
"produced":{
"memberOf":{
"curatedBy":{
"memberOf":{
"id":"group/0e8bc04a-6538-4792-b82a-9e0751857e7d"
}
}
}
}
},
{
"produced":{
"memberOf":{
"curatedBy":{
"memberOf":{
"id":"group/6086b58d-941d-41e3-87c1-e00e96952ffb"
}
}
}
}
}
]
}- Once corrected, the search and facet requests timeout after 20 seconds. Looks like a pretty broad (and odd?) search: agents that produced objects that are part of a set whereby the set is curated by a group that is a member of YCBA and YUAG. Are any sets co-curated? Or perhaps I'm misinterpreting the query.
Here's my first re-write off the query. Near-instance response of zero results:
{
"produced":{
"memberOf":{
"curatedBy":{
"memberOf":{
"AND":[
{
"id":"https://lux.collections.yale.edu/data/group/0e8bc04a-6538-4792-b82a-9e0751857e7d"
},
{
"id":"https://lux.collections.yale.edu/data/group/6086b58d-941d-41e3-87c1-e00e96952ffb"
}
]
}
}
}
}
}However, when I take the AND up a level, I quickly get the first 10 of an estimated 5,217 results:
{
"produced":{
"memberOf":{
"curatedBy":{
"AND":[
{
"memberOf":{
"id":"https://lux.collections.yale.edu/data/group/0e8bc04a-6538-4792-b82a-9e0751857e7d"
}
},
{
"memberOf":{
"id":"https://lux.collections.yale.edu/data/group/0e8bc04a-6538-4792-b82a-9e0751857e7d"
}
}
]
}
}
}
}So maybe the search makes sense after all and we identified another optimization: push AND and OR down to the extent the triple paths / search terms match.
roamye
prowns
Problem Description: In advanced search, a search query was done where one of the expected results should be "Trumbull & Wiley". Instead of the expected results the query generated the "Your search yielded no results. Please try another search." message. If we change the query to go down to the departmental level the search results work. However, the results should also work at the non-departmental level.
This ticket serves as a research ticket to understand why this is happening and how we can fix it.
Expected Behavior/Solution: TBD - research
Requirements: TBD - research
Needed for promotion: If an item on the list is not needed, it should be crossed off but not removed.
UAT/LUX Examples:
Dependencies/Blocks:
Related Github Issues:
Related links:
Wireframe/Mockup: Place wireframe/mockup for the proposed solution at end of ticket.