Well, first of all, thanks A LOT for your reply
Quote:
Originally Posted by theducks
As you are aware, A VL is just a (restricted) View of the overall, so you could have a VL for coffee table sized (>MB) books [ {size}>2000000 } (note this value is not just a single book, but the contents of that Title record)
|
Well, the problem here is that the separation between big and small books is not a matter of viewing them, but where are they to be stored.
The size was just an example, really. The complete issue I explain below
Quote:
You could add 'EMPTY BOOKS' (a book without Formats), tagged: "In XYZ Library" (which you switch to). The drawback is this is a High effort maintenance model (Every BIG book added/changed needs the mirrored empty book metadata)
So, what are you really trying to cure by doing this?
|
Well, in my library I have books bought from quite a number of stores. Some of them are updated frequently (well, more or less) when the books are corrected. For example, Amazon does that, sometimes nearly weekly for new books.
Other books are updated very seldom, if at all.
And other books I maintain myself (most of them from friends who self-publish), and they are shared with the authors.
This is only the tip of the iceberg, my library is quite complex
so it makes sense for me to store some of the books in a folder which is periodically synced to the cloud, others in a network storage which is always available, others in a folder in my laptop, etc.
Right now I have all of them together, and I can live with that, but it would make my life a bit easier if the library could be spread over more than one storage.
I know there's a single DB but I thought that since the paths of the books have to be stored on the DB (I think...) there would be some tweak.
Thanks a lot, really