Open untoreh opened 2 years ago
Hi, @untoreh Thanks for your idea. I think content server is considered a library, just like opds, and calibredb.el is working as frontend.
Would you like to add a pull request? You can make a function just like calibredb-opds-request-page
, and update calibredb-library-list
.
In this case, if we choose the content server via calibredb-library-list
, we will request the content server and get the results which will be shown in calibredb dashboard.
The calibre content server has the OPDS interface, but to use it as a replacement for the metadata
database OPDS is not enough to get the full details, so the content server API must be queried.
To use the content server as a library at least the function to read (download) the books is required.
Then after support for adding books (upload) and setting metadata, calibredb
is not a hard dependency anymore and calibredb.el can work just with just remote servers.
Yes. What I mean is adding a function to query the content server, I guess it is not difficult, just like the opds implementation. But adding books/updating meta/deleting books remotely are new features that may need some works.
These are examples to fetch the books from the calibre content server, and setting metadata on them. The advantages are: