6 posts • Page 1 of 1
As far as I know, equal positions that arise by a different move order (or by passes) do not lead to the same database entry. That's an important feature that should by implemented to avoid doubled work.
The main advantage of this feature isn't even avoiding duplicated effort but in making sure there aren't duplicates of a position having different sets of follow up moves and being seen by different eyes. Also, someone who's an expert on a certain position shouldn't have to hunt around for every example where the position comes up.
A user should be informed about all the variations that lead to the merged node. How do you want to achieve it?adum wrote:this is a good idea -- i have this for goproblems, and it would work well in josekipedia too. it's a bit tricky right now but someday i'd like to do it.