Quote:
Originally Posted by Tanjamuse
I would really love to have more than one library on my new tablet.
|
I assume you are talking about separate calibre physical libraries, not separate calibre virtual libraries.
With some setup in calibre, CC already can handle separate virtual libraries. The setup:
- in calibre, create a tags-like column built from other columns with the template "program: virtual_libraries()".
- in CC, add that new column to the list of custom columns shown in the grouping drawer (CC's settings)
Now a long-press on a virtual library in the grouping drawer will restrict what CC shows to books in that virtual library.
CC can also already handle combining different physical libraries into its database, correctly handling metadata update depending on which library calibre is using when you connect as a wireless device. If you added a tag or a new custom column that provides the name of the library the book comes from then you could use CC's long-press-to-restrict feature described above to limit what you see in CC to a given source library.
EDIT:
you can create a column that automatically fills in the library name using a column built from other columns with the template "program: current_library_name()". This scheme would also work with the content server because the library name would be in the book's metadata.
As for handling multiple physical libraries as separate libraries in CC: there are complexities. The first is how would CC show them. Clearly no cross pollination between libraries should be possible, implying separate book storage, separate database (grouping and sorting), and probably separate setup options. This really implies separate CC installations, something that would not be straightforward given how Android works.
The second is ensuring that when you connect to calibre as a wireless device, you are connecting to the library associated with that CC installation. In effect, CC would be required to refuse to connect if the library on the calibre side isn't the "right" library; the same the one used when the CC library was created. How this would work with the content server is an interesting question, given that one can simultaneously have several different content server instances serving different content from multiple libraries. Also, a side effect is that combining libraries into a single CC database would be forbidden, something that people use today.
The third would be the expected immediate requests for dynamic switching between the physical libraries and for moving books between the libraries. Coordinating this with calibre would be extremely challenging.
Given these complexities and given the workarounds described above, I am not inclined to attempt to implement separate physical libraries.