Quote:
Originally Posted by kiwidude
I would suggest "use with caution" the "special character tag" approach. A couple of reasons. First you might find that in a future version of search your tag characters conflict with some special search syntax, so then you have to change them and "unlearn" what you may have adapted yourself too.
But far more importantly also are you 100% sure that you are the only person who will ever browse your library in future? No intention of a family member or friend sitting down to browse it or shared with them over the web? Because you are going to find it incredibly painful to explain to them that "[!@$sf" is your foo genre or whatever....
Sorry unboggling, I just can't grok the prefixing of % signs, brackets and all other sorts of things to genres or whatever. I think you are out on a limb with that one - I understand that you like it for yourself but I would hate to have to try to explain it to someone else  |
No problem, kiwidude.
I deleted most of the abbreviation and tag discussion, it didn't show up in the revision posted last Friday except maybe a passing mention. Next revision I'll make sure that's explicitly cleared out of all nooks and crannies except maybe to mention how I do it with an explicit "not recommending this" notation.
Most people have family and friends they share with. I happen to live alone and don't share books with friends presently but if either ever change, it'd be easy to rename abbreviations back to human-speakable/comprehend-at-glance-able. Re symbol prefixes, yeah, that's happened to me already, learning something doesn't work anymore in my new method or a new calibre revision. Those are easy to change too. Hopefully by the time most symbols can't be used, I'll be more proficient at formal searches and restrictions on the fly, or move to using some other method.
Nothing I said in the KISS/Workflow posts after the first few was meant in general as advice or recommendation, except one thing: try to keep it simple. Everything else is supposed to be just examples of how one user does things. I don't know how to make that more explicit than it already is stated in the first section, Orient. When in the workflow I say, "Do this" or "Do that" I'm writing out the steps I use, or want to use, for myself. Those become examples, which any other user can try out, use for awhile, or ignore as they please. I thought of changing the title to something like: "Examples of One User's Workflow, Not Necessarily Recommended" but that just didn't work for me as a title.