Review display of holdings info when all items are in a temp loc (especially reserves)

[saseestone]

Probably needs some discussion and design review -

Currently we're displaying a holdings statement associated with a permanent location, even when all the items associated with that holdings statement are in a temporary location. This seems confusing for the user. It happens most often when all the items on a holding are on Course reserve, but might occur in other cases (i.e. out on exhibit?)

Example record: https://searchworks.stanford.edu/view/4668197

Questions we might need to ask gryphon search:

1. What is the usefulness of the statement?
2. How should the display change if there are large chunks of items in a temporary location but also in the permanent location?

UX research could help us figure out how holdings information is used by users of the catalog, and it's overall value.

[dnoneill]

This is a searchworks_traject_indexer issue. The issue is for some reason pieces doesn't include the location id because we could easily do a filter here: https://github.com/sul-dlss/searchworks_traject_indexer/blob/66471d74c6b9b97620b117a43a8677b2da783fe5/lib/folio/mhld_builder.rb#L82. For some reason the locationId isn't present even though the api indicates it is a field https://s3.amazonaws.com/foliodocs/api/mod-orders/r/pieces.html#orders_pieces_get