Quote:
Originally Posted by capink
I don't know whether this is relevant to the discussion at hand or not, but I will give it a go anyway:
I always thought that categories like authors, tags ... etc should have the same api as books (set_field, field_metadata ... etc). That way we can easily reuse other tools like library view, cover view, search and replace ...etc.
Not sure if that is possible or practical.
|
Thanks for the thoughts.
I spent some weeks thinking about this and came to the conclusion that it wasn't practical. My idea was to have "libraries" of items per category that could reference each other through links. I gave up after looking at the massive number of changes, such as having several "libraries" open at the same time and maintaining column structure. Smaller things like how search would work gave me headaches.
BetterRed's idea of using real separate meta-metadata libraries with the ability to show details from those other libraries in the "main" library gets most of the way there without massive changes.
Adding the ability to refer to local "documents" from category links provides a second simpler to understand mechanism to keep unstructured meta-metadata within the same library. Perhaps it might need some kind of search mechanism, for which Kovid suggested something like is used for FTS.
Kovid has reviewed the "links everywhere" database changes and db API to maintain them. He will look at the "remote book details" stuff and other UI changes when time permits.