Plugins for Calibre Integration. Finally annotations sync for epub, etc

Named logseg-calibre-metadata and logseq-calibre-annotation on Logseq Marketplace.

The first is for auto-creating page like the built-in Zotero integration.

demo1

The second is for reading ebook while having annotation syncing to logseq.

demo6

These two plugins can function independently. The calibreMetadata plugin only creates the page and inserts the renderers used by the calibreAnnotation plugin.

Calibre Content Server is very convenient. We can connect and read books with a browser from any device, and the annotations will still seamlessly sync to the page.

Amazing! Kudos!

Does editing an annotation in Logseq also update the one in Calibre or the sync is only to one direction?

Nah, it just syncs one way. It’d be handy for me when I’m chilling in bed, reading a book on my phone, and jotting down some notes. Those notes would be synced to Logseq. Since the notes in Logseq are the final version though, there’s not much point in pushing them back into the book. Technically, it could be done, but it might require tweaking the Calibre API a bit.

2 Likes

This is best thing I’ve heard in a while.

My previous solution was to use logseq:// links in the Book Details pane (I had first done it with obsd) to create the pages for books, authors, etc, but some data loss forced me to restore a very old backup of calibre and I haven’t felt like setting it up properly again.

This is easier to set up and more functional. It might be interesting to add a place to copy and paste links that can go in Book Details based on the template set in the settings for this plugin. Automatic page properties would be a cool addition in the future as well, especially if they can pull data from custom columns

calibre-metadata adds a link to book detail in Calibre next to the two renderers. There is a convenient URL scheme for this i.e calibre://show-book/LibraryName/9. I need to update the gif demo.
Ther
e is work for the page property, as different data formats prefer different processing. Right now it is honestly minimal and may even lead to error when some property (like atm “rating”) are specified. I am always ready for feedback to improve.