# causes problems in facets

Bug #856811 reported by James Fournie
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Evergreen
Invalid
Medium
Unassigned

Bug Description

EG 2.0.5
PG 8.4

# / pound sign / hash sign / number sign causes problems in a facet field. This can be observed by:

a) select * FROM facet.field_entry where value ~ '#'
b) do a search for one of those and attempt to use the facet with the #

James Fournie (jfournie)
tags: added: facets
Revision history for this message
Michael Peters (mrpeters) wrote :

Confirmed.

Can be tested in Evergreen Indiana (http://evergreen.lib.in.us) with the series facet " The Nightmare club ; #1".

tags: added: opac
Changed in evergreen:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Michael Peters (mrpeters) wrote :

For what it's worth, I think James may have meant "metabib.series_field_entry" (or one of the other *_field_entry) tables, instead of facet.field_entry which doesn't appear to exist.

Revision history for this message
Jason Stephenson (jstephenson) wrote :

Needs confirmation in 2.1+.

Changed in evergreen:
status: Confirmed → Incomplete
Revision history for this message
George Duimovich (george-duimovich) wrote :

Confirmed in 2.2.0 system running OpenSRF 2.1.0 & PG 9.14.

Changed in evergreen:
status: Incomplete → Confirmed
Revision history for this message
Dan Scott (denials) wrote :

Looks like the query is getting converted into:

"series|seriestitle[Foolish # 1]"

instead of:

"series|seriestitle:[Foolish # 1]" (note additional colon)

Revision history for this message
Dan Scott (denials) wrote :

Huh. http://evergreen-ils.org/dokuwiki/doku.php?id=documentation:technical:search_grammar claims that's the right syntax (no colon). And it does work for other facets without a hash.

Oh, ding ding ding: per those docs, the hash mark is the "modifier marker"; the docs also claim that can be adjusted (presumably directly in OpenILS/Application/Storage/QueryParser.pm.? Not clear where else that assumption is hard-coded though).

I guess when it was defined, the thought was that it wouldn't appear in series identifiers...

Revision history for this message
Jason Stephenson (jstephenson) wrote :

Is this a problem with facets in general?

It is a problem for tpac?

If it only affects JSPAC, I'm inclined to set this to "won't fix."

Revision history for this message
Dan Scott (denials) wrote :

Yes, this is a problem with facets in general; the search grammar is applied to any interface, and can be confirmed by following Michael's link to the Evergreen Indiana catalog (now running TPAC) and searching for series "The Nightmare Club", then trying to narrow down to one of the facets.

Revision history for this message
Dan Scott (denials) wrote :

Pushed a branch (user/dbs/pound_facets) to add some "#" facets to concerto.sql to make this easier to reproduce. Search for "Piano concerto in C major, op. 39" or "Beethoven: concertos and overtures" and you'll get facets with # signs.

Revision history for this message
Jeff Godin (jgodin) wrote :

The working branch user/tsbere/qp_fix referenced in bug 856811 contains a change which moves from using # to separate facets to using ][ to separate facets.

Elaine Hardy (ehardy)
tags: added: cataloging
Revision history for this message
Jennifer Pringle (jpringle-u) wrote :

This bug is no longer present on 2.4 in the TPAC.

Revision history for this message
Remington Steed (rjs7) wrote :

I am not able to reproduce the problem in 2.5.

Kathy Lussier (klussier)
Changed in evergreen:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.