MobileRead Forums - View Single Post

Johansen · 09-09-2011, 08:06 PM

I have this problem.

I have set up calibre with two different databases. One more or less "clean", and one where I have tinkered with the books.

The problem is, when I move books from one database to another (in Calibre, keeping one database active, and copying books manually from the other, and dropping the new books IN the old book (upper right corner)).

I believed that I would get a message from Calibre if the book was allready in the system (like you get when you add books as "new"... "This book already exists"). Or something like what happens when you merge books, that the format allready existing is kept, and any "new" books of the same format is deleted.

And I suddenly realized this is NOT what happens.

The NEW version of the book replaces the old one, without warning. (This is a problem as I tend to stumble through Calibre, more or less half blind (and sober, I promise), and sometimes manage to mark the wrong book.

My working method:
1. Find book to fix in the "clean" folder. Book1: Book1.epub
2. Mark the book in the UNCLEAN folder (Book1.epub2)
3. Fix book1.epub with appropriate software.
4. Update the UNCLEAN folder by dragging the book into calibre. The unclean calibre-folder should now have two files, Book1.epub and Book1.epub2. (I do this to keep track of what books I have edited and what I have not. At some point I will have to delete all *.epub2, but I do have enough disk-space for now, so...)

The problem is when I mark Book2 instead of Book1 in Calibre. I get no warning that the Book2.epub allready exists, and suddenly I have a Book2.epub that is actually the edited Book1.epub.

What I am asking is: would it be possible (and even smart) to add a feature that warns the user that "there is allready a file named Book2.epub" when dragging books/new formats into existing books?

Or will I just have to learn how to read properly, so that I stop making stupid mistakes like this? (I'll start reading, but I still think a warning would be smart...)

09-09-2011, 08:06 PM	#1
Johansen Junior Member Posts: 8 Karma: 10 Join Date: Jan 2011 Device: Sony SR650	Automatic overwriting ebooks... I have this problem. I have set up calibre with two different databases. One more or less "clean", and one where I have tinkered with the books. The problem is, when I move books from one database to another (in Calibre, keeping one database active, and copying books manually from the other, and dropping the new books IN the old book (upper right corner)). I believed that I would get a message from Calibre if the book was allready in the system (like you get when you add books as "new"... "This book already exists"). Or something like what happens when you merge books, that the format allready existing is kept, and any "new" books of the same format is deleted. And I suddenly realized this is NOT what happens. The NEW version of the book replaces the old one, without warning. (This is a problem as I tend to stumble through Calibre, more or less half blind (and sober, I promise), and sometimes manage to mark the wrong book. My working method: 1. Find book to fix in the "clean" folder. Book1: Book1.epub 2. Mark the book in the UNCLEAN folder (Book1.epub2) 3. Fix book1.epub with appropriate software. 4. Update the UNCLEAN folder by dragging the book into calibre. The unclean calibre-folder should now have two files, Book1.epub and Book1.epub2. (I do this to keep track of what books I have edited and what I have not. At some point I will have to delete all *.epub2, but I do have enough disk-space for now, so...) The problem is when I mark Book2 instead of Book1 in Calibre. I get no warning that the Book2.epub allready exists, and suddenly I have a Book2.epub that is actually the edited Book1.epub. What I am asking is: would it be possible (and even smart) to add a feature that warns the user that "there is allready a file named Book2.epub" when dragging books/new formats into existing books? Or will I just have to learn how to read properly, so that I stop making stupid mistakes like this? (I'll start reading, but I still think a warning would be smart...)