Quote:
Originally Posted by kiwidude
I understand what you are saying, and if searching across my Calibre library in that way was important to me I would be trying to find a way to make it work too. The problem I have with trying to do this though is that the quality of the search results is only as good as the data you have in your library. There is no guarantee that a book about vampires is going to have vampire somewhere in the comments - in fact I would suggest most of the time it won't from the books I have seen.  That is - unless you add the data there yourself of course. And if you are adding data yourself, then there can be advantages to putting it into the tags field (such as ease of searching to allow access via the tags browser etc).
...
But I am just playing devil's advocate here. If you are happy with your search results then go for it. For myself it drove me mental to quickly search for an author like Lee Child by typing "child" and having many hundreds of results being returned because they had a word like "children" in their comments, or because Lee Child had made some soundbite as promo for some other unrelated book. I rarely type the search prefixes (too slow/clumsy to type) and don't like having flow interrupted with popup dialogs as you do for advanced search. So turning off default searching on fields other than the ones I actually want to search rocked my world  |
Hmm. On second thought, I guess I'll keep my secondary genre tags for awhile. I just noticed today that recently, after creating all my new custom columns to receive tags moved out of tags column, I'd been searching the fields: authors, series, title, tags (tags now mostly empty), and specific custom columns #dlgroup (source), #fqr (format quality), #genre, #kind, #prizes, and #status. I'd forgotten to add comments to the list, and so in addition to making searches less precise, I also suspect searching comments will slow the searches down a little. Which I vaguely recall is one reason I started restricting searches originally to just certain fields indicated in Preferences/Search.