Quote:
Originally Posted by barium
The more I think about it, the more I think the behavior that would work best for me doesn't make sense for the program.
|
?? Why?
Quote:
|
What I'd like is for an auto-merge to occur where there's no duplicate format,
|
That happens now.
Quote:
|
but for a new/duplicate book entry to be created where there is a duplicate format.
|
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.)
Quote:
|
Then, in a separate process (e.g. when I went to read the title in question), I could review duplicate entries to determine whether they're different editions or the same thing. If they're the same, I could delete one of them. If they're different, I could manually update the metadata accordingly.
|
Yes, that's how that option would be used. All books would be added, instead of ignoring matching formats as we do now.
Quote:
|
This seems like inconsistent behavior in a way, though. If you use the automerge feature at all, you can end up with different editions in the same book entry if the different editions happened to be in different formats.
|
Yes, that's a risk of doing it automatically, but I see no way to avoid that.