EnergyLens: Very nice idea. I hadn't seen that clipping service, but I can see a use for it.
A couple of comments.
I have to admit I cringed when I saw the code to get the annotations column. But, I'm so used to writing calibre plugins, hadn't thought about other ways to do this. It would be safer to get the name of the annotations column from the annotations configuration. That is plugins/annotations.json in the calibre configuration directory.
This would be great as a plugin. Collecting the annotations and adding the file to calibre can be done with no problems. Doing this for all books in the library is easy. And adding something to collect and upload the files to the service would be easy as well.
And when I say that, it would actually be natural to add this to the Annotations plugin. That could generate the file when retrieving the annotations. Or an export function could generate them to be saved elsewhere.
In any case, if there is something the annotations plugin could do differently that would help, I am willing to consider it. Especially it come in the form of a patch
One thing I don't understand is:
Quote:
Originally Posted by EnergyLens
In the future I plan to establish an Annotations database that is independent from the Calibre database because I find that with the volatility of news downloads there is the danger of Highlighted Content being lost.
|
How does the news downloads affect this? Unless news articles are being annotated on the devices, there shouldn't be an issue. And if they are, it should only be these annotations that are at risk.