Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Deleting eBooks based on shelf assignment (Two-Way-Sync) #3298

Open
Domoel opened this issue Jan 27, 2025 · 0 comments
Open

Comments

@Domoel
Copy link

Domoel commented Jan 27, 2025

Hi all,

I played a little bit with the Kobo sync integration feature and found out, that the syncing mechanism is somewhat limited when it comes to the deletion of eBook from the Kobo device itself.

I see two issues currently when it comes to the kobo sync integration:

You can only delete an ebook directly from your Kobo. It is not possible to trigger deletion from the calibre web frontend.
Once you delete a ebook from your kobo, the ebook will be sent to the archive area of your calibre web frontend (which is suboptimal).
Therefore it would be great if we could get a real two way sync mechanism. Ideally, this should be subject to the shelf logic (provided you have your books synchronized across specific shelves). I imagine it as follows:

If an eBook is removed from the Kobo Shelf within the calibre web frontend, the book should also be removed from the end device (regardless of the reading status). Conversely, if a book is removed from the end device, it should be removed from the calibre web shelf which is assigned to Kobo (assignment to the shelf should be undone instead of moving the book to the archive).

The eBook itself should not just be archived, as it still belongs in the book collection and should remain there (just not on the end device). I think that many people certainly see it that way.

Is this somehow possible?

BR
Dom

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant