Improve interface for merging Collectors

[lexiclevenger]

Even when the underlying Agent is completely identical, differences in record metadata (like modifiedbyagent) trigger the secondary "Merge Collectors" popup. This window forces users to manually delete one of the duplicates using the red trash can icon to get the green "Close" button to appear. Compounding this, it is entirely unintuitive which record to drop—about 50% of the time, choosing the first option fails, forcing the user to cancel the entire process, restart the merge, and pick the second option.

Since conflicting Collector records are an expected outcome when merging two distinct CollectionEvent records, this workflow introduces significant friction and confusion for our data cleansers.

We would love to see the merge tool improved to automatically resolve identical Agents during a parent-level merge, or at least provide clear guidance on which record the UI expects the user to drop.

Reported by Garth Holman at the University of Michigan