Quote:
|
That's one of the three options being discussed (user would get to choose the desired option). (The other two are to ignore duplicate formats, as we do now or to overwrite a duplicate format with the new one.)
|
That sounds brilliant. Ideally, you'd also have a way to search for duplicate book entries created during auto-merge.
Quote:
|
Originally Posted by barium
I think the behavior that would work best for me doesn't make sense for the program.
|
Quote:
|
Originally Posted by Starson17
?? Why?
|
Only because of the inconsistency I described. With this behavior, you avoid merging because you may have a different edition in one case (where duplicate formats get separate book entries) but you ignore the possibility that a different edition exists in the other (where different formats are merged). The auto-merge feature is consistent in this regard right now - it always ignores the possibility that a different edition exists. (Assuming that the program is designed to have different editions stored in separate book entries, which I think it is, because you can only have one of each format per book entry.)