William Denton schrieb:
> I'm curious how other places are handling something we're working on: how
> to show users that all eresources are still available even after they've
> narrowed to one physical library in the locatipn facet.
Do those eresources have a special value in the data field used for the
location facet? If so, it might just be an issue of adding an additional
ORed value to the filter query. If those eresources should show up
ALWAYS (really ALWAYS) a static "OR location:eresources" (assuming
"eresources" is the value matching those eresources in the "location"
index field) injected whenever a location filter is present, might do.
With the new SearchObject the best place to hack that would be method
addFilter(), I guess. Check if $field is "location" and if so, add " OR
location:eresources" to the filter value. Without the SearchObject the
code around // Define Filter Query in services/Search/Results.php would
be the place to add something similar. But both solutions are ugly hacks...
Maybe that's something for 1.1: Are there more use cases for general
"filter manipulation" functionality? We are doing a lot of that to
restrict access to parts of the index based on user access rights (by
adding fq parameters matching the parts of the index an individual user
is allowed to search to every query sent to Solr). Should I open a JIRA
issue on that where we may collect use cases for it?
> As I undersatand it this kind of thing isn't possible with the current
If you can catch those eresources with a Solr query (like
"location:eresources"), it is not an issue with Solr. But VuFind needs
to generate appropriate Solr queries carrying that additional query
parameter. That is a bit hackish at the moment...
Verbundzentrale des Gemeinsamen Bibliotheksverbundes (VZG)
Platz der Göttinger Sieben 1, D 37073 Göttingen
kinstler@..., +49 (0) 551 39-13431, http://www.gbv.de