[OPEN-ILS-GENERAL] apostrophe in title search causing problems(Bug #744513)

[Gordana Vitez]

Hi Ben,

Thanks for you suggestion. Just after the upgrade to 2.0.7, all of our computers were upgrade to Windows 7 so everything was wiped clean. Nevertheless, I did try clearing the cache for staff client and web browsers and still came up with the problem. 

I'll follow the bug ticket as well. 

Thanks!
Gordana

>>> Ben Shum <bshum at biblio.org> 7/19/2011 12:57 PM >>>
Hi Gordana,

We're using 2.0.6, but we've applied by hand several patches from 2.0.7
and the upcoming 2.0.8.  Trying a search on our system for a title with
an apostrophe such as "boys don't cry" worked just fine without any
change to the search terms.  I tested this in our staff client and OPAC
and both were fine.

What I did notice however, is that if one were to hit the advanced
search after completing the initial search, it would construct the next
screen with my search terms without an apostrophe so:  "boys don t cry"
would show up instead.  Running that search still retrieved some results
on our system, but not as many.  I'll do some more tests and add a note
to the bug ticket if I can replicate the behavior consistently.

In the meantime, I would verify that you have cleared the cache on your
web browsers and staff client (admin --> for developers --> clear cache)
to make sure that there aren't strange remnants in the code from before
your upgrade.  Then try again.

-- Ben

On 07/19/2011 12:16 PM, Gordana Vitez wrote:
> Hi everyone,
>
> We recently upgraded to 2.0.7 and noticed that a search using an apostrophe in the staff client or the advanced search screen returns no results. For example: searching "cops don't cry" in Niagara College's catalogue returns the following results:
>
> http://niagaracollege.niagaraevergreen.ca/opac/en-CA/skin/nc/xml/rresult.xml?if=&it=&bl=&lf=&a=&la=&cl=&d=1&l=2&s=rel&sd=asc&adt=ml&tp=&t=keyword%3A%20cops%20don%20t%20cry&av=&rt=multi&ol=2 
>
> You'll notice that there is a space where the apostrophe should be. 
>
> I did find the following Bug #744513 that shows a fix was committed for 2.0.6. Is it possible that the fix wasn't committed to 2.0.7 or wasn't included in upgrade instructions? Our upgrade was from 2.0.2 to 2.0.7.
>
> Thanks!
> Gordana
>
> Gordana Vitez
> Library Services & Systems Coordinator
> NC Libraries and Learning Commons
> Niagara College
> 300 Woodlawn Rd
> Welland Ontario
> L3C 7L3
> Phone: (905) 735 2211 ext 7404
> Fax: (905) 736 6021
> gvitez at niagaracollege.ca 
>
>
>

-- 
Benjamin Shum
Open Source Software Coordinator
Bibliomation, Inc.
32 Crest Road
Middlebury, CT 06762
203-577-4070, ext. 113