Thread: Aura Manage epub and keep read progress
View Single Post
Old 12-19-2017, 05:58 PM   #23
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by JSWolf View Post
I don't mind the directory structure. It's all behind the scenes. So I don't have to deal with it. I just use the GUI front end and when I want to pull eBooks from Calibre, it's not an issue.

So why is not having Calibre automatically modify the eBook on import, opening with the Editor or Viewer meaning that there is not really any point to using Calibre? I use Calibre a lot since I figured out how to stop it from modifying when I don't want it to.
I'm not sure if I see the point of importing the book, maintaining the metadata in calibre but not writing that metadata back to the book at sometime. Because if I don't then, when I look at the book on my devices, then I won't have the right title, author, description or cover.

And don't say to use the Modify ePub plugin, the Embed metadata function or a conversion (yes, I know you don't) to do this. Then you are back to the situation that geek1011 is complaining about. All of these methods update the metadata in the book in exactly the same way. They will all put the things in the OPF that geek1011 doesn't like.

@geek1011: I'm not a fan of how the extra metadata is written to the OPF, and every now and then I consider looking at how to block it. Adding an option to only write the DC metadata, or calibre core metadata is probably not hard. But, it just hasn't been important. I have almost zero need to look at the OPF and I know that while there is a lot of seeming cruft, it is all valid and usable if the application wants it.

As to the library file structure, it's a database. I treat it that way and it doesn't bug me. I do play in it, but I do understand what is happening and knowing when the files will be updated is easy: when I change something. If I change some metadata, the OPF file will change. And the book will change if I push the change to the book. And if I change some common metadata element (rename a tag, fix an authors name) then all the OPF files for books with that element will change. Calibre updates the database and then updates the files in the background, so this can take a bit of time for a change that affects a lot of books. But if you want to put the library into a version control system, then you really have to just accept all changes. Push them once a day or each time you make bulk changes or something like that.
davidfor is offline   Reply With Quote