Quote:
Originally Posted by Geremia
I wish your commit was merged into master. An auto-merging feature is desperately needed.
|
That will never be in my interest to do so. I think it is the single most dangerous thing you could do to corrupt your library (I have other words for it but they may offend).
If you have yourself in a situation where you are creating so many duplicates that you feel you need to automate resolving them then go back and take a good hard look at how you got into that mess in the first place and change your workflows.
Automated merging has a 99% chance of making the problem even worse for you, not better. There are way too many reasons how this goes wrong - remember duplicate groups in many situations are not "guaranteed" duplicates, they are suggestions. There are no guarantees unless you have been meticulous about each book added to your library whether the book actually is what the metadata indicates it is - and if you were a meticulous person then you would not even be in the situation of thousands of duplicates. Let alone when you start doing any sort of non-exact searches with all the false positives it will find.
The plugin can make no determinations as to which of the items in the group it should merge into. One may have "better" metadata. One might have a better format conversion of the book.
So automated merging is the equivalent of "close your eyes and hope for the best". That is not a behavior I want to encourage by adding it as a feature to the plugin, because inevitably people will come here after it goes wrong for them and complain about why the plugin could not figure it all out for them to prevent it.