@kotnik: thank you very much for your time :)

I would like to have a few days to test the plugin myself. I'm short of time right now.

What I would like is feature parity w/ the joplin exporter but I'm not sure if it's already implemented or even doable (Didn't look at your code or at nextcloud api docs yet). I mean, among others:

• ability to update a note if it was changed.
• ability to ignore a note for a book if the same note exists on the server

This way implies the exporter works as a sync server and any past highlight or annotation is deleted from the server when the client exports/syncs it after deletion.

Please let me know if that's ok with you. If you prefeer some kind of archive without updating/deleting I think we can make it configurable :)

@kotnik: thank you very much for your time :)

I would like to have a few days to test the plugin myself. I'm short of time right now.

Thank you for the review. This is, obviously, not urgent at all and I am here to make it through. It's quite fun to code Lua!

What I would like is feature parity w/ the joplin exporter but I'm not sure if it's already implemented or even doable (Didn't look at your code or at nextcloud api docs yet). I mean, among others:

* ability to update a note if it was changed.

* ability to ignore a note for a book if the same note exists on the server

This way implies the exporter works as a sync server and any past highlight or annotation is deleted from the server when the client exports/syncs it after deletion.

Please let me know if that's ok with you. If you prefeer some kind of archive without updating/deleting I think we can make it configurable :)

Yeah, I looked into Joplin, and this (the first) iteration works by uploading every note/annotation to Nextcloud. If the note from the same title already exists it will be updated (version changes can be configured on the Nextcloud side). Notes are tagged with KOReader tag, which in Nextcloud means they will be put in separate directory, so it is easy to work with them.

I can add an option to update or skip if existing note already exists in Nextcloud. I'd appreciate testing as well, it works fine with my local and remote Nextcloud instances, but I am not super sure how it would work with big number of notes.

I'm very sorry, @kotnik. I forgot completely about this PR 😭

Yeah, I looked into Joplin, and this (the first) iteration works by uploading every note/annotation to Nextcloud. If the note from the same title already exists it will be updated (version changes can be configured on the Nextcloud side). Notes are tagged with KOReader tag, which in Nextcloud means they will be put in separate directory, so it is easy to work with them.

That's completely fine!

I can add an option to update or skip if existing note already exists in Nextcloud

Not required, current behaviour works fine.

. I'd appreciate testing as well, it works fine with my local and remote Nextcloud instances, but I am not super sure how it would work with big number of notes.

I've tested briefly and works fine, but I had to generate a bunch of notes to test. The best way for getting tests for free is to merge this and let hardcore hightlighters to use it.

TODO:

Create wiki page mentioned in help

If you want to add documentation before merging this be my guest ;). Otherwise I'll add some notes after merging.

Again, apologies for the late response.