http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2098 Summary: Searching for numbers (ISBN) seems to find the wrong results Product: Koha Version: unspecified Platform: PC OS/Version: All Status: NEW Severity: critical Priority: P3 Component: Searching AssignedTo: jmf@liblime.com ReportedBy: nicole.engard@liblime.com QAContact: koha-bugs@lists.koha.org CC: galen.charlton@liblime.com When searching for 014100018X (an ISBN that wasn't indexed in my system) I came up with results for many unrelated titles. After some testing, Galen found that this happens with several similar searches. See the chat below to follow our testing of the problem: <nengard> search question - I entered an ISBN that wasn't in my system and instead of getting no results I got a bunch of results that were unrelated ... i know it's a keyword search - but where were those numbers that i got the results i got? <gmcharlt> nengard: what search string, specifically/ <gmcharlt> ? <nengard> 014100018X <nengard> ... is it the X? <gmcharlt> 018X by itself gets the same result set <nengard> um - should it? <nengard> I would think not <gmcharlt> no, it shouldn't; just narrowing down the problem <nengard> i just have to say that i hate finding things like this :( I know we want to get 3.0 out!! <gmcharlt> also, there's another problem - look at the first hit in the results list - no title <nengard> uh huh - should it not show up? it was one of my import tests - probably ... <gmcharlt> more that I'm curious how the 245 $a and $c came to be blank <gmcharlt> http://opac-nce.dev.kohalibrary.com/cgi-bin/koha/opac-MARCdetail.pl?biblionu... <gmcharlt> nengard: I'm able to reproduce the search bug with just the 20-record sample - things like 016x, 017x, etc. are giving the same results <nengard> is it not supposed to save if they're blank? <gmcharlt> nengard: file a bug on that, please - give it at least major severity <nengard> a bug on the search? or the 245 <nengard> or both? <gmcharlt> the search, for now <nengard> k ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.