Hide transcendent records from location group searches
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
This will certainly fall under a wishlist item.
We use transcendent bib sources for our electronic holdings, since they are available to all of our locations it eliminates the need for located URIs. Unfortunately, they show up even when we limit by location groups.
This seems counterintuitive, as limiting by a shelving location should certainly exclude items that are not shelved in that area. By simply replicating line 219 of 300.schema.
183 JOIN config.bib_source s ON (b.source = s.id)
184 WHERE s.transcendant
+ AND ( param_locations IS NULL OR array_upper(
185 AND b.id IN ( SELECT * FROM unnest( core_result.records ) );
186
Changed in evergreen: | |
importance: | Undecided → Wishlist |
milestone: | none → 2.next |
Changed in evergreen: | |
status: | New → Confirmed |
Changed in evergreen: | |
milestone: | 3.next → none |
I agree that it's a wishlist item and have marked it as such. The use case makes sense to me, but I wonder if we will need to add some switches. It makes sense to say that since transcendent bibs belong to no particular location, a search that filters on specific locations should exclude them. However, I could also imagine—possibly incorrectly—a view that transcendent bibs belong to *all* locations.
Another consideration: if we exclude transcendent bibs (and located URI results) if param_locations is set, should we also do the same when param_statuses is set?