Hide transcendent records from location group searches

[Bill Ott]

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.staged_search and including it in the WHERE of search.query_parser_fts() on line 184, it effectively does this.

 183 JOIN config.bib_source s ON (b.source = s.id)
 184 WHERE s.transcendant
+ AND ( param_locations IS NULL OR array_upper(param_locations, 1) IS NULL )
 185 AND b.id IN ( SELECT * FROM unnest( core_result.records ) );
 186

[Galen Charlton (gmc)]

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?

[Mike Rylander (mrylander)]

Just to provide some background, traditionally transcendent bibs show up in all searches that don't include copy-specific filters, such as status. With regard to copy locations, the thinking is that those are a subset of an org unit and carry the same (lack of) restrictions for transcendent bibs. We can certainly redefine that, though.

[Terran McCanna (tmccanna)]

I believe this should be fixed by the fix for https://bugs.launchpad.net/evergreen/+bug/1746800

[Michele Morgan (mmorgan)]

Tested this in master after the fix for bug 1746800 was committed. This issue is not resolved. Transcendent records continue to appear in location group searches in the opac.