Ahh, that does make it more readable.  But I’m not sure what purpose it serves to add this filter – that will hide any records that have no available_at value, but it has no bearing on whether available_at values show up as facet options – that’s what facets.ini is for.


- Demian


From: Joe Atzberger [mailto:joe@booksite.com]
Sent: Wednesday, June 26, 2013 11:35 AM
To: vufind-tech@lists.sourceforge.net
Subject: Re: [VuFind-Tech] Available At Wildcard Facet Count


This looks confusing in my default gmail font, but I should point out that the middle quotes are actually 2 single quotes, i.e. the empty string as the start of a range query.  That is:

addFilter("available_at:['' TO *]");


On Wed, Jun 26, 2013 at 10:16 AM, Demian Katz <demian.katz@villanova.edu> wrote:

I’m not sure I understand exactly what you are trying to do.  Can you simply add this new field to web/conf/facets.ini to turn on the functionality you desire?


- Demian


From: Duffy, Mark [mailto:duffymark@einetwork.net]
Sent: Wednesday, June 26, 2013 10:14 AM
To: vufind-tech@lists.sourceforge.net
Subject: [VuFind-Tech] Available At Wildcard Facet Count


I’m using vufind 1.x and trying to add the available at wildcard to the facets, but the counts are not reflecting this. Whenever I have set the following


$this->addFilter("available_at:['' TO *]");


It only updates the numFound count, not the facetcounts for each location.





This SF.net email is sponsored by Windows:

Build for Windows Store.

Vufind-tech mailing list