http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7421 Galen Charlton <gmcharlt@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Discussion |Passed QA --- Comment #56 from Galen Charlton <gmcharlt@gmail.com> --- (In reply to mathieu saby from comment #55)
(In reply to Galen Charlton from comment #54)
(In reply to Katrin Fischer from comment #51)
I am not sure if it's annoying - I always tell people that everything that is indexed can be searched in keyword search and the reactions so far are quite positive.
I agree -- it's easier to explain that an "any" index includes everything (though whether or not fixed fields should be included is a matter of opinion), so I for one don't really see a problem with the change in behavior of the "any" index.
Note, though, that that's a separate question from whether the "any" index should be included in, say, auth_finder.pl, as somebody looking for authority records via that interface has little reason to be using anything other than the headings searches to begin with.
Sorry, but I do not agree with both of you. I'm speaking here in general, not for authorities (we don't give access to authorities on opac). The OPAC search with GRS1 is very "noisy", with a lot of unwanted and non understandable results. Ex : I have a book published in "Roma". It has "1 vol. (215 p.)", it is written in french ("fre" in 105a) with an item having an INTERNAL note (not shown on opac) in 995 field, like "book given by a teacher". This book will currently show on opac when some user search "vol", "fre", "book", "given", "teacher" or "Roma". For "Roma" I could maybe understand, but I don't like that. For the other points I don't like that AT ALL.
We have a rather big catalog (400 000 records), to Koha can easily find a lot of unrelated records for any search. With DOM I understand it will be worse.
Of course this issue could been less problematic, if Koha had a good pertinence sorting (it is mad), a good date sorting (it is broken, for unimarc at least), and a good facetting system (all we have are pseudofacets, non parametrable for the moment, based only on the X first results, not cumulable, and whose general presentation is not user friendly). We can work on these points, of course, but it would be easier to define a more reasonable "any" index.
These are reasonable concerns and coments, but IMO they are more for bug 8962 than this one. Since the immediate concern of this bug -- adding an initial DOM configuration for UNIMARC authorities -- is now addressed in master and we have an explanation of the differences in "Any" authority searches in DOM vs. GRS-1, I'm setting this one to pushed to master. -- You are receiving this mail because: You are watching all bug changes.