Re: [VuFind-General] Call number recognition - incorrect matching in 'narrow search'

[Demian K. <dem...@vi...>]

Are all of your 099 call numbers these local formats, or is it a mix of local formats and genuine LC numbers?

If 099 is just for local formats, the easy solution is to redefine your indexing rules to either completely exclude 099 or else to at least avoid indexing it in the fields used for call number faceting.

If 099 is a mix of local formats and LC, you may need to customize the call number indexing scripts so that they detect your local prefixes and skip just those numbers.

If you let me know more about your exact situation, I can give more detail on how to solve the problem.

- Demian

From: lu....@kc... [mailto:lu....@kc...]
Sent: Thursday, June 07, 2012 1:56 AM
To: vuf...@li...
Subject: [VuFind-General] Call number recognition - incorrect matching in 'narrow search'

Hello,

I searched an author and 30 plus records displayed. Call nos. of these records are local nos. that are in tag 099
one format of call no. - starts with >   FRB.
the second format of call no. - starts with > NBER.

On the right column > under Narrow Search > Call number , I find these:
                F - General American History (29) - that means 29 titles from the class F  !!
                N - Fine Arts (1) - means 1 title from the class N   !!

Big time match problem in this situation!  There are no relationships at all of these call numbers to these classes cited in 'narrow search'.

We have many local numbers like these that start with an abbreviation of the publisher or organization..

HELP!  Where could I fix or resolve this issue?

THANK YOU!

Lu
_______________________________
Lu Dayrit,
| e-mail:   lu....@kc...