Quote:
Originally Posted by vitalichka
Thank you kiwidude, you really took the time on this one.
|
yw. I don't mind posting my workflow if nothing else to see if someone else would jump in and tell me that there are better approaches for certain steps.
These to/fro conversations on algorithms are excellent, I apologise for not adding my own thoughts as yet but I do read each post and will revisit it all again when I can. Currently my only time allocated to thinking about duplicate detection is when I sit and write a rambling post.
As for the "way to approach development" of it, 100% agree with Chaley in that we need to agree an approach before we begin, certainly if it comes down to me to do the plugin development. My relative unfamiliarity with Python/Calibre code means I develop at snail pace so calling it "RAD" is a lie in my case
. I would be gutted to spend the considerable development time required for this only to find a fundamental flaw requiring a total rewrite. Such as if I had started coding it as a popup dialog as was our favoured approach in this thread for a while. Basic agreement on how duplicate results will be presented, navigated and maintained looks to be the fundamental issue for the plugin. I am less concerned at this point about the "identification algorithms" as they can be added/tweaked over time.
Final comment repeating one I made a while ago that is relevant again given recent posts. My hope was that we would develop it as a plugin initially so that we could get the kinks out without interfering with Calibre releases. And that one day it might get included for distribution with Calibre if Kovid deemed it useful. Confirmation from Kovid that he would be interested in including it when ready is great. We just need to produce something worthwhile to be included of course...