Quote:
Originally Posted by kovidgoyal
The LCCN column is legacy from a time when I thought I would implement it, but I never ended up doing it.
My sticking point with this is that:
1) Very few users would benefit from this. Essentially only people that understood the system, and apart from librarians, who does? Plain text tags, while far less precise are more approachable.
1.5) It therefore needs to be default off in the GUI and in metadata fetches.
|
A user does not need to understand the LCCN in order to benefit from it. Sorting your library by LCCN (or dewey), would create a natural browsable list where books that are related are
clustered together. One's library could be organised like a physical library, where "shelves" of books are related to each other. The tags would remain and could still be used for searches, but Im talking about Sorting order not filtering. Sorting on the Tag field currently has no value for multi-tag entries, as currently it only sorts on the first tag in the group which is stored in "arbitrary" alphabetical order.
I say "arbitrary", because tags are normally entered in some form of heirarchy and not in alphabetical order. (i.e people don't enter their tags alphabetically)
on 1.5 altho the column is in the database, its not even available to be switched on. ie its not in the list of available columns.