Does CC's calibre driver support two-way syncing?

[karl1c]

I have CC on iOS and the only fields that are editable are the _is_read_ and _last_read_date_.

1. Is there a reason CC does not support editing of other fields?

2. In principal, does the Calibre driver support syncing other fields?
I've had a look at the code for the driver at https://github.com/kovidgoyal/calibr..._app/driver.py and fiddled about with Wireshark.
It seems that CC sends all the metadata back and looks like the driver *should* sync it.
I've tried emulating CC (with changes to, say, the comments field) using netcat, but the changes don't appear in Calibre (the changes to _is_read_ *do* appear).

Thanks.

[theducks]

Originally Posted by karl1c

I have CC on iOS and the only fields that are editable are the _is_read_ and _last_read_date_.

1. Is there a reason CC does not support editing of other fields?

2. In principal, does the Calibre driver support syncing other fields?
I've had a look at the code for the driver at https://github.com/kovidgoyal/calibr..._app/driver.py and fiddled about with Wireshark.
It seems that CC sends all the metadata back and looks like the driver *should* sync it.
I've tried emulating CC (with changes to, say, the comments field) using netcat, but the changes don't appear in Calibre (the changes to _is_read_ *do* appear).

Thanks.

Thats it. Read ststus

[karl1c]

Thanks @theducks. Where in the code is the "bottle neck"? (As you'll know, the other fields are sent from CC and appear to be accepted by the driver, but don't get synced.)

I assume by "Read status", you mean the status and the date, as the date also gets through.

[theducks]

Originally Posted by karl1c

Thanks @theducks. Where in the code is the "bottle neck"? (As you'll know, the other fields are sent from CC and appear to be accepted by the driver, but don't get synced.)

I assume by "Read status", you mean the status and the date, as the date also gets through.

There were special hooks put into Calibre for the reading status fields.
If you really want to edit metadata, use your browser and the content server (edit is a new feature)

[chaley]

If you have looked at the code then you would have seen that the calibre driver syncs only two metadata fields: read and date read. If you want to sync more than that you will need to:

• modify the calibre driver to accept the field name correspondence
• define the semantics of the sync (up, down, conflict) in both the single value and list cases
• change the client to send the original and new values so data change can be detected
• do the actual data syncing during the startup handshake (change synchronize_with_db in the driver)
• modify the client to allow the user to define the field name correspondence.
• return the correct metadata to the client

As calibre is open source, you can do everything except the last two. For those you would need to write your own wireless device client (CC replacement).

[karl1c]

Originally Posted by chaley

If you have looked at the code then you would have seen that the calibre driver syncs only two metadata fields: read and date read. If you want to sync more than that you will need to:

Thanks @chaley I saw where _is_read_ and _last_read_date_ get picked up and managed to get them to appear in Calibre. However, I noticed that CC sends abbreviated metadata in response to GET_BOOK_COUNT and *full* metadata in response to NOOP, {"priKey": 1}. I assumed that the full metadata wouldn't be sent only to be thrown away and that I must have missed something.

Thanks for the clarification.

[karl1c]

BTW why didn’t you go the whole hog and allow editing of metadata in CC?

[chaley]

Originally Posted by karl1c

BTW why didn’t you go the whole hog and allow editing of metadata in CC?

Because that is hard to do correctly in terms of data types, semantic analysis, conflict analysis, performance, and programming.

And BTW: the metadata isn't "thrown away". It is critical to the metadata caching scheme used to reduce network traffic.