Quote:
Originally Posted by dhdurgee
Interesting. I would have expected nested folders to result in nested collections when collections were being built from folders. So what happens when nested folders are converted to collections?
|
The full path (minus /mnt/us/documents/) becomes the collection name.
e.g.
Code:
/Fantasy/JK Rowling/Harry Potter/Harry Potter and the Philosopher's Stone.azw3
-> Collection: Fantasy/JK Rowling/Harry Potter
/Romance/Historical/Judith McNaught/Almost Heaven.azw3
-> Collection: Romance/Historical/Judith McNaught
/Romance/Suspense/JD Robb/In Death/Naked in Death.azw3
-> Collection: Romance/Thriller/JD Robb/In Death
I don't like to create collections for authors with only a few books though and I find pure folders to be too limited. I tend to use a combination of LibrarianSync JSON (for books downloaded via web browser or copied from phone/tablet) and Calibre JSON to generate collections. It works great as long as the collections don't overlap.