Open BillPascoe opened 2 years ago
Unlike MySQL, it's case sentitive when you query records by a column value. Changing the keywords to case sensitive will probably generate a lot of duplicate keywords which are essentially the same. E.g. 'This keyword', 'THIS Keyword', 'this keyword' and so on. However, there will be cases where keywords with difference letter cases have the different meaning, like 'US' and 'us'. I think we need to think about enhancing the keyword widget to allow autocomplete and suggestions before we make the keyword stored in the database case sensitive.
We apply the autocomplete suggestion of keywords already in the database, but will allow user to enter upper or lower case versions of keywords. Eg: if some start typing 'ind' it will auto suggest 'Indigenous' but will allow user to put in 'indigenous' or 'Indigenous'.
Looks as though we should experiment with Bill's suggestion once we have budget for issues again.
When I create or edit a layer I can enter Subject keywords. At the moment it converts them all to lower case which makes case insensitive comparison easy. However, sometimes it's important that they have a capital letter. Eg: 'Aboriginal People', 'Indigenous', 'WWII'. Make it possible to enter subject keywords with capital letters.