Quote:
Originally Posted by dewd
Ideally, I'd like to see a "download read-date only if read-date field is empty", which would also solve the issue of losing first-read dates for those books which are re-reads. (I see a suggestion earlier in this thread for someone who is uploading to GR, but it doesn't help with sync'ing.)
|
Adding validation that the date coming from GR is not null so that it doesn't clear the last read date in calibre is reasonable, and I'll look at it. But, if you still have a book doing this, can you run calibre in debug mode, sync and post the log. I don't think there is enough debug logging happening to show me exactly what is wrong. I'm wondering if the date is coming down but it isn't being converted properly.
As to not syncing the date if it is already filled in calibre, I disagree. The "Date read column" in the configuration is for the
last date read. Syncing from GR brings the last read date it knows about. Whatever the value is that comes from GR should replace the value in the calibre library. That is what the function is designed to do, so anything else would be a bug or a change in function.
If what you are actually recording is "Date First read", then you should either not be syncing the date read, or use a separate column in calibre.