Quote:
Originally Posted by please55
Fantastic guide, thanks for sharing.
|
You're welcome.
Quote:
Originally Posted by please55
I'm curious what system you used to organize your ideas.
|
Basic structure and functions of calibre; my ebook-related workflow.
Quote:
Originally Posted by please55
Most of my questions are geared towards understanding your choices or clarify my thinking.
a) You set the series for individual books to (1)[1] for sorting reasons but it doesn't appear to be any different from leaving the field empty for that subset. So why?
|
"(1) [1]" announces that the series was previously checked/entered, rather than possibly previously forgotten to have been checked/entered.
Quote:
Originally Posted by please55
b) Why not use tags at all? Genres fulfils the same purpose - so why not use tags & keywords for example? Why create two custom columns/fields entirely?
|
I like each column to address a specific attribute. For me discreet sets of attribute-specific metadata elements are more aesthetic, less confusing, easier to remember, and easier to isolate in search terms; than different sets mixed in one column. Otherwise it's just personal preference. [EDIT] calibre automatically enters the tags "News" and "Catalogs" in the Tags column; these metadata elements are publication types, so if I used Tags column for anything else it would be for types. Putting types in Tags seems more confusing than putting types in custom column Types.[/EDIT]
Quote:
Originally Posted by please55
c) Why use " , " instead of " & " as separator for keywords and genre column? It causes the tag browser to break out "fn, sf" and "sf, fn" as two separate categories and the "sf" category won't bring up books tagged with "fn, sf" or vice versa. **Edit** I just figured out why I had that behaviour - I had checked "contains names" when creating that column. Don't understand why but that explains (c).
|
Right. Separator "&" is for Name columns such as Author(s).