http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7031
Jared Camins-Esakov <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #13 from Jared Camins-Esakov <[email protected]> 2011-12-28 16:52:26 UTC --- Katrin, (In reply to comment #12) > Created attachment 6938 [details] > screenshot of advanced search > > I tested this and have some questions/notes: > > 1) I was searching for a special combination of itemtype A, location B, and > collection code C. The search turned up a record where no item had this > combination. There was one item with my itemtype A, while the other item had > itemtype D, location B, and collection code C. > Is it possible to make the search more specific here? Not with GRS-1 indexing. DOM indexing would make it possible. > 2) Why use phrase for itype, but not for ccode or loc? > No results match your search with limit(s): 'mc-itype,phr:BK or > mc-itype,phr:CF or mc-itype,phr:CR mc-ccode:"NFIC" mc-loc:"CART" or > mc-loc:"CHILD"'. I'm not sure, but I would think that adding a phrase index and using that would be preferable here (however, I wouldn't hold up the QA process for it if I were the one signing off). Of course, while we're using GRS-1 indexing, it probably doesn't really matter all that much anyway. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
