SUGGESTION: Case sensitive option for Library filter

I'd like to see a "Match case" option on the library panel menu. It would help avoid situations like this, where I'm looking for all the books I'm in the middle of reading (which I tag READING), and don't want to also find books that happen to have "Reading" in their bundle name (which I also tag).

I suppose I could rename my READING tag to INPROGRESS or something like that, or I could set up a collection with a rule such as mytag:READING -mytag:("daily bible reading","reading & preaching","daily readings") that weeds out all those bundles (it would need to be updated occasionally). But still I think a case matching option might come in handy. Maybe I'm the only one who would, in which case of course don't bother. I can work around its absence. Collection rule coming up now!

Find more posts tagged with

Comments

Andrew Batishko

Try: [match case]mytag:READING

Rosie Perera

https://community.logos.com/discussion/comment/724683#Comment_724683

Try: [match case]mytag:READING

Cool. Thanks!

I dislike features that are hidden unless you know the special syntax. This is something that could very easily be brought into the GUI and should be, IMO. It's the sort of thing I will not need again for such a long time that I'll forget again how to do it, and will have to search for it in the forums. I like that there was an effort to make the search syntax more available to users through the search helps. But there's no such thing for Library filter syntax. That's an area for Eli to look at for improvement in a future release.

MJ. Smith

https://community.logos.com/discussion/comment/724687#Comment_724687

Try: [match case]mytag:READING

Cool. Thanks!

I dislike features that are hidden unless you know the special syntax.

This is a documented element of the Search (see wiki) which has been mentioned several times in the forums recently. I'm not saying that it shouldn't be brought into a simplified GUI - just that it is no more hidden than the remainder of the syntax.

Rosie Perera

https://community.logos.com/discussion/comment/724691#Comment_724691

just that it is no more hidden than the remainder of the syntax.

I meant hidden from the user exploring the GUI. Note that I didn't say undocumented.

And yes, the rest of the Library filter syntax is hidden too, and should be brought into the fore in the GUI, IMO. Hence the rest of my post directed at Eli.

Note that this would make life easier for MVPs too. Fewer questions to answer. [:)]

Eli Evans (Logos)

https://community.logos.com/discussion/comment/724696#Comment_724696

I disagree this should be in the GUI. Relying on a difference in case sounds like a power use case, and so documenting special syntax is a reasonable solution. The UI for the Library is supposed to be dead-simple to operate in normal everyday circumstances. Why complicate it with buttons and knobs for things like case (and stemming, and mark sensitivity) that aren't anything like normal use cases?

Unless there really are everyday use cases for case sensitivity?

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/725098#Comment_725098

I agree with Eli here. For every one post suggesting that the Library have a case-sensitivity option, there are a hundred (give or take [:)]) forum posts asking "Why does my search for 'jesus' return no results?!" (Answer: do you have "Match case" checked?)

You can argue that hiding the control on the panel menu is a bad GUI design, but bear in mind that the user did manage to find it and turn it on the first time. [:)]

Lew Worthington

https://community.logos.com/discussion/comment/725119#Comment_725119

FWIW, I'd agree with Eli and Bradley. [:)]

Rosie Perera

https://community.logos.com/discussion/comment/725122#Comment_725122

I accept that answer.