View Single Post
Old 10-21-2014, 02:35 PM   #16
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,463
Karma: 8025600
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by crazybrit View Post
So I got it working. I must admit, I find the distinction between connecting to the content server and connecting as a wireless client to be confusing. It seems the later gets the metadata and the former gets the actual titles. Unfortunate that it needs to be a two step process. I assume it's necessary to do both each time you want to sync newly added titles to the android device? Is there an ordering?
There is confusion.

The content server connection is a "pull" connection. CC is in charge, asking calibre to send books. When you ask for a book, it and its metadata are transferred. Because of the way the connection/protocol works, nothing else is transferred.

The wireless device connection is a "push" connection. Calibre is in charge. You send books from calibre. Again, metadata and the book are sent. However, the WD connection does much more because it is considered by calibre to be a calibre "device". Calibre updates the metadata for all the books on the device, and it sends to the device a description of all the custom columns currently in use in that library. It can also sync any book files on the device that have changed since they were last sent. It is the sending of the column descriptions that was required before you could do things in CC that requires knowledge of custom columns.
Quote:
So under "grouping drawer" settings I added "#genre" to "make groups for custom columns" which triggered a database update.

Now I see the following:

Code:
< genre
   computers.algorithms
   computers.architecture
   fiction.classic
I guess I was expecting a tree like:
Code:
< genre
   computers
      algorithms
      architecture
   fiction
      classic
I understand that the '.' separated notation is calibre's.

So then I selected "Hierarchical Groups" in "grouping drawer" and checked #genre, which triggered another database update but nothing changed in how it's being presented.

It's not a big deal, as clearly it's letting me see the sub genres in dotted notation. I was just curious.
CC shows hierarchies as one level. To enable hierarchies you must both select the column in hierarchical groups and turn on group by first letters for that column/group.
chaley is offline   Reply With Quote