Old Plugin Thread for KOReader Sync

[harmtemolder]

Originally Posted by lightmaster

Can you add support for the Device type "USER_DEFINED"? I added it as a compatible device type in the plugin I downloaded and it seems to work just fine, capable of finding the metadata and syncing to Calibre.

Thanks for your input. I've added it in release 0.3.1-beta: https://www.mobileread.com/forums/sh...41&postcount=1

Originally Posted by lightmaster

On a different note, it seems that while Koreader sets the "Summary"=>"Status" metadata when you finish a book, it does not set any status metadata for when you have a book that is currently being read. I thought that something like this might work, but my very rudimentary knowledge of python prevents me from trying it myself: "if 'Summary'=>'Status' doesn't exist, and read progress is >0 and <1, then set 'Summary'=>'Status' to 'in-progress'". This logic would also mean that if Koreader does start setting an in-progress metadata, this plugin won't override it.

If this is a bug in KOReader I prefer to have it fixed at the source. Until then this issue is on the issue tracker, so if anyone feels like picking it up their help is greatly appreciated: https://todo.sr.ht/~harmtemolder/kor...libre-plugin/4

[harmtemolder]

Originally Posted by Huwaetzel

The driver can be installed as a plugin and when the device is connected it gives a popup "Pocketbook632. Also in your plugin the error message states "type POCKETBOOK632 not yet supported.

I've added it in 0.3.2. Let me know if it works

[iupiter]

Originally Posted by harmtemolder

I've added it in 0.3.2. Let me know if it works

It works now.


What is the default state of the reading status, if an book never has been opened?

[Huwaetzel]

Originally Posted by iupiter

It works now.

I can confrim this. Thank you very much for adding the device/driver

[harmtemolder]

Originally Posted by iupiter

What is the default state of the reading status, if an book never has been opened?

It will probably be empty: This plugin reads the contents of the meta lua file you can find next to the book on your ereader's memory, but KOReader only creates that file when you open a book.

[harmtemolder]

Originally Posted by lightmaster

On a different note, it seems that while Koreader sets the "Summary"=>"Status" metadata when you finish a book, it does not set any status metadata for when you have a book that is currently being read. I thought that something like this might work, but my very rudimentary knowledge of python prevents me from trying it myself: "if 'Summary'=>'Status' doesn't exist, and read progress is >0 and <1, then set 'Summary'=>'Status' to 'in-progress'". This logic would also mean that if Koreader does start setting an in-progress metadata, this plugin won't override it.

Come to think of it, I actually solved this same issue ages ago using a template function in calibre:

def evaluate(self, formatter, kwargs, mi, locals, progress_field):
  if progress_field:
    if float(progress_field.strip('%').strip()) < 100:
      return '☐'
    return '☑︎'
  return ''

[harmtemolder]

Originally Posted by harmtemolder

I've gone through my code from 2020 again, and it reads the date from `summary` > `modified` in the `metadata.epub.lua`. But I'm manually opening a couple from books that I've recently finished, and all of these have an empty string in that field. So it looks like KOReader no longer logs that in the metadata.

I've replaced that old code with logic that looks at a book's highlights and sets a first read column to the earliest date, and a last read column to the latest. I hope that helps.

[chaley]

Originally Posted by harmtemolder

Come to think of it, I actually solved this same issue ages ago using a template function in calibre:

def evaluate(self, formatter, kwargs, mi, locals, progress_field):
  if progress_field:
    if float(progress_field.strip('%').strip()) < 100:
      return '☐'
    return '☑︎'
  return ''

Originally Posted by harmtemolder

I've replaced that old code with logic that looks at a book's highlights and sets a first read column to the earliest date, and a last read column to the latest. I hope that helps.

If you are running the newest version of calibre then the new Python templates might be of interest. Using these it isn't necessary to create user-defined template functions. See https://www.mobileread.com/forums/sh...53#post4264953 and the post immediately after it.

[Hyphen-ated]

Hi, I have implemented code in this plugin for a last_read_date column by reading the modify time of the metadata sidecar file and converting that to a date.

So now after I sync from my device, I can get calibre to sort my library by the last date I had each book open in koreader. Hooray!

My code is here: https://github.com/Hyphen-ated/korea...c94813a718df06

[harmtemolder]

Originally Posted by Hyphen-ated

Hi, I have implemented code in this plugin for a last_read_date column by reading the modify time of the metadata sidecar file and converting that to a date.

So now after I sync from my device, I can get calibre to sort my library by the last date I had each book open in koreader. Hooray!

Great to hear you got this working for your device. It's probably a USB device connected as regular storage, isn't it?

[harmtemolder]

On a different note: Someone reported that they got a ZoneInfoNotFoundError with v0.4.0-beta on Windows 10. Unfortunately I cannot test that, and they can't either. So if you have Windows 10 and run into the same issue, I'd be very grateful if you could test the otherwise untested v0.4.1-beta from here. If that solves it, I'll release it here.

[lightmaster]

Originally Posted by harmtemolder

On a different note: Someone reported that they got a ZoneInfoNotFoundError with v0.4.0-beta on Windows 10. Unfortunately I cannot test that, and they can't either. So if you have Windows 10 and run into the same issue, I'd be very grateful if you could test the otherwise untested v0.4.1-beta from here. If that solves it, I'll release it here.

I'm getting a "ZoneInfoNotFoundError: No time zone found with key UTC". Running Windows 11. About to download v0.4.1-beta to try it.

[lightmaster]

Not getting the error anymore with v0.4.1-beta

[Hyphen-ated]

Originally Posted by harmtemolder

Great to hear you got this working for your device. It's probably a USB device connected as regular storage, isn't it?

Yep, it is

[harmtemolder]

Originally Posted by lightmaster

Not getting the error anymore with v0.4.1-beta

Assuming that everything else still works as expected I'll release it then. Thanks for testing!