Quote:
Originally Posted by speakingtohe
I prefer not to merge isbn ...
I would like to merge custom columns with the proviso that if first one selected is blank it gets overwritten, but maybe not
|
Well, that's 4 for 4 to leave it as is. I'm glad I posted. I personally like it as is, but it did seem a bit odd/inconsistent to leave out that one bit of metadata during a Merge. At this point I'm inclined to just update the warning to tell the user that ISBN is not merged.
I left a message in the bug report directing the bug reporter here, so perhaps he'll make some comments.
As to custom metadata, that was added to the Merge function a month or so ago. It's treated exactly like the type of non-custom metadata that the custom field is based on.
If a field in the destination record (first selected) is empty, it gets filled in. If it's not empty, it is never overwritten, but it will get additional metadata appended, where possible (without duplication). Tags and comment-like fields are two fields where additional data is appended, but checked to prevent duplication.