View Single Post
Old 04-13-2018, 05:12 AM   #5
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,784
Karma: 30237628
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by davidfor View Post
A way that some people handle this is with an "intake" library. All new books are added to the intake library, metadata is updated and then the books are compared to what is in the main library. Then they can be deleted or replace the version in the main library.

The Find Duplicates plugin can help with this as it can compare two libraries.

Another thing you can do is to have calibre add a "new" tag to the book when it is added to your library. Then you will know which is the new book when you do the duplicates check. Of course, you need to remember to remove this tag when you finish this and any other processing you do for new books.
- that describes what I and several others in my group do.

In my case, after running Find Duplicate->Find Library duplicates on books flagged as "Ready to go" (a Yes/No column), the books that are not duplicates (hopefully, most if not all of them) are copied to the Main library, the duplicates are copied to a Duplicates library where, in the fullness of time, they get dealt with manually.

BR
BetterRed is offline   Reply With Quote