Quote:
Originally Posted by kovidgoyal
1) Sorting (this is not really an advantage for a field like source as far as I can see)
|
Sorting (well, displaying) is useful when looking at multiple things at once. Considering source: I often want to look at where I obtained books from a set of authors (or some other set). Selecting the authors then looking at each set of tags is very tedious. Another, less frequent use is looking at the source of books I have recently read, so that I can 'correct' (that is, buy) any books where I don't have a legitimate physical or electronic copy. (This is
not an invitation to start a discussion on piracy.) I have other uses involving other 'organizational' tags such as to read (separate for my wife and me), priority, read date, and a few others.
The tag-as-column enhancement I proposed plus the [] tag change would satisfy all my requirements without adding any new specific columns. However, if someone wants to use SQL to manipulate the information, or to use calibredb to extract and manipulate it, then real columns could be preferable.