Quote:
Originally Posted by dwanthny
Filling in empty fields would be a plus, but I wouldn't want it adding any extra tags or changing series etc...
|
I'm going to have to do some tests, but from what I recall of Kovid's code, when there is no matching book already in the destination library, (or when my autosort option is not checked, which defaults to Kovid's original code), the entire record from the source library is brought over. That certainly means that all the tags from the source library come with it, along with all data from the non-custom fields (comments, publisher, rating, etc.). Since I haven't yet tested it, I'm not totally sure what happens to custom fields, but I suspect they come along only if they are defined in the destination library.
Responding to your post, and to be consistent with what happens when the entire record is brought over (along with all of its tags) doesn't that mean that you'd want the tags brought over from the source library and added to the tags in the matching record of your destination library? Any field that was already filled in in the destination would never be overwritten (that's how the Merge function works), so you wouldn't have to worry about the series being changed. But if the destination library has a record for the same book, and that book has an empty series, and an empty Publisher, should they be filled in with the new data?
Quote:
|
Maybe an option, either the standard merge you do now or a complete additive merge which would include filling in the blanks and adding any extra tags.
|
Hmmm. I'm not sure this would be very easy for the user to understand. This proposed option would only have meaning when the autosort option is turned on and it won't do anything even then unless there is already a book in the destination library that matches (author exact match, title fuzzy match) . I think it would lead to confusion.