Driver plugin: get file path of ebook?

[jgoguen]

Is there a way for a device driver plugin to get the original file path of an ebook, or do I need to open metadata.db and query for the path from there? For example, if I have a book at C:\Users\jgoguen\ebooks\Author\awesomebook.epub and I upload it to my device, the only path I can find how to get with the API is the obfuscated path in a temporary folder. I'm working on a plugin that modifies ePub files in transit and I'd like to be able to save the modified files back to the calibre library and replace the original book.

[Dopedangel]

Originally Posted by jgoguen

Is there a way for a device driver plugin to get the original file path of an ebook, or do I need to open metadata.db and query for the path from there? For example, if I have a book at C:\Users\jgoguen\ebooks\Author\awesomebook.epub and I upload it to my device, the only path I can find how to get with the API is the obfuscated path in a temporary folder. I'm working on a plugin that modifies ePub files in transit and I'd like to be able to save the modified files back to the calibre library and replace the original book.

Have a look at modify epub plugin it modifies the epub and then overwrites the original that might help.

[kovidgoyal]

No there's no way to get the original file path in a device driver. Device drivers are not supposed to be modifying files in the library. I for one would be pretty annoyed if sending files to a device caused the originals to be changed. Why do you need this capability?

[chaley]

Also note that device drivers run on a different thread. Modifying the library in any way from a device driver could lead to very difficult to debug inconsistencies. In addition, the ebook could have been modified by a plugboard before being handed to the device driver. Those modifications must not be made permanent.

[theducks]

My 2 cents
Many people don't keep the original source file in the same place (if at all) after import into Calibre, thus making use of any 'logged' 'original path/filename' inconsistent on further usage at best

[jgoguen]

Originally Posted by chaley

In addition, the ebook could have been modified by a plugboard before being handed to the device driver.

I forgot all about metadata plugboards. Thank you for pointing this out, I won't bother with this since you're right, this could likely lead to things that users wouldn't want or expect to be saved back to the library.

Originally Posted by kovidgoyal

Why do you need this capability?

It's more of something that I personally would like to have the option for. The driver plugin I'm working on modifies the contents of ePub files (adds extra span tags to allow annotation saving and last read position saving to work better) before sending them to the device and I'd prefer to not have to re-parse the files on the occasional times where I re-upload a book for some reason.

If the intention is that a driver plugin should never actually do this I won't bother, I can accomplish the same thing by removing the calibre book and saving from the device into my library.