You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When your resource-instance node can reference multiple different instances (i.e. it's a resource-instance-list datatype), the advanced search lets you filter on specific references. See image:
If a user is searching for instances that refer to a set of instances, there's an implicit "AND", i.e. "I want resources that reference both A and B". However the way the search actually executes is an "OR", showing results that refer to either A or B or both.
This can be traced to the datatype-specific logic in ResourceInstanceDataType.append_search_filters() method here:
such that value["val"] is a list of resourceid strings for each "references" resource instance.
Suggested improvement:
We could rename the label "References" --> "References any of" and potentially create a new option for "References all of" to delineate the underlying "AND" vs "OR" choices.
This would save a user from creating an entirely new facet of the same node just to explicitly select the "AND"/"OR" in the UI (see image below)
The text was updated successfully, but these errors were encountered:
When your resource-instance node can reference multiple different instances (i.e. it's a resource-instance-list datatype), the advanced search lets you filter on specific references. See image:
If a user is searching for instances that refer to a set of instances, there's an implicit "AND", i.e. "I want resources that reference both A and B". However the way the search actually executes is an "OR", showing results that refer to either A or B or both.
This can be traced to the datatype-specific logic in ResourceInstanceDataType.append_search_filters() method here:
such that
value["val"]
is a list of resourceid strings for each "references" resource instance.Suggested improvement:
We could rename the label "References" --> "References any of" and potentially create a new option for "References all of" to delineate the underlying "AND" vs "OR" choices.
This would save a user from creating an entirely new facet of the same node just to explicitly select the "AND"/"OR" in the UI (see image below)
The text was updated successfully, but these errors were encountered: