Ere Maijala has done some work on hierarchical/nested facets, as described here:

 

https://vufind.org/jira/browse/VUFIND-599

 

and found in this pull request:

 

https://github.com/vufind-org/vufind/pull/164

 

The pull request is a work in progress and is likely to be revised significantly once Ere returns from vacation. Also not sure if it’s exactly what you want – I believe this is for presenting facets as a tree, whereas a simpler approach that I have thought about (but not found time to implement) would involve simply switching some facets on and off based on whether or not others have been selected.

 

In any case, food for thought. Let us know if you’re interested in collaborating on any of this.

 

- Demian

 

From: Shepard, Thomas - 1150 - MITLL [mailto:tshepard@ll.mit.edu]
Sent: Wednesday, July 16, 2014 10:11 AM
To: Clint Bellanger; solrmarc-tech@googlegroups.com
Cc: vufind-tech@lists.sourceforge.net; vufind-general@lists.sourceforge.net
Subject: Re: [VuFind-Tech] vufind import options and mapping files

 

Thanks, Clint!

That tip will come in handy for a lot future faceting I am planning, not just periods.

But for the end of string periods, I looked on the SolrMarc site and discovered how to remove the periods at the point of import:

 

taxbt = custom, removeTrailingPunct(691a),tax_map.properties(taxbt)

 

 

I am now exploring ways to make these new facets conditional; ie, only appearing when other facets are used up.

For example, we have a hierarchical vocabulary of several levels, and I am able to create a separate facet for each level, but it would be nice if some of those specific levels could be hidden until broader terms are selected.

 

Thanks again!

Thom

 

 

From: Clint Bellanger [mailto:clintbellanger@gmail.com]
Sent: Wednesday, July 16, 2014 9:58 AM
To: solrmarc-tech@googlegroups.com
Cc: Shepard, Thomas - 1150 - MITLL; vufind-tech@lists.sourceforge.net; vufind-general@lists.sourceforge.net
Subject: Re: vufind import options and mapping files

 

A tip that's helping me at Auburn - these java style .properties allow Unicode escaping for the map keys and elements.

 

The form is \uHHHH where HHHH is the Unicode hex value for that character. So to match on "Audiovisual." (period intact) the map properties file can be:

 

Audiovisual\u002e = Audiovisual

 

The characters #, !, =, :, and blank space (u0020) can also be escaped with a simple preceding backslash. From the Wikipedia example:

 

key\ with\ spaces = This is the value that could be looked up with the key "key with spaces".

 

via:

 

- Clint Bellanger

 

 


On Monday, March 24, 2014 1:48:22 PM UTC-5, Demian Katz wrote:

I’m guessing that the problem here is that periods have a special meaning in the property map, because you can use them to create named maps. You might want to try escaping them with backslashes to see if that helps.