Ticket #266 (closed defect: fixed)

Opened 11 years ago

Last modified 10 years ago

GS2 and GS3: Casefolding is off by default even though prefs say it's on

Reported by: ak19 Owned by: nobody
Priority: moderate Milestone: Greenstone 3 wishlist
Component: Greenstone2&3 Severity: blocker
Keywords: casefolding, preferences Cc:

Description

Tested on: GS3 compiled from source (checked out from svn on March 03, 2008) and on GS 2.80 binary installation.

When a collection is created in GLI with case-folding options available (Design tab > Search indexes > Casefold ticked), the Greenstone browser's preferences page says that the case-folding is ON (meaning searches performed should be case insensitive by default). However, casefolding starts being OFF by default in spite of what the preferences page says, so that searches made are case sensitive. Casefolding does not take effect until the Set-Prefs button is pressed (with casefolding status showing ON) which then turns the functionality ON.

See  https://list.scms.waikato.ac.nz/mailman/private/greenstone-users/2008-March/006504.html for this problem identified by Jack Kelly.

Change History

Changed 11 years ago by ak19

  • component changed from Building to Greenstone2&3

Changed 11 years ago by davidb

  • severity set to blocker
  • milestone changed from Next Release (2 or 3) to Release 2.82

Changed 10 years ago by kjdon

  • milestone changed from Release 2.82 to Release 3.04

I think this may be a problem with other options too.

GS3: Quick solution, make the code defaults the same as the interface defaults.

Long term solution: I can't remember what that was, but I know I had an idea about it :-(

Changed 10 years ago by kjdon

  • status changed from new to closed
  • resolution set to fixed

I have made the code defaults the same as interface defaults.

Note: See TracTickets for help on using tickets.