Edit reason statements on merge?
Answers
-
Tom Huber said: I have to chuckle. I'm in the same boat and often make typos myself. Do I want to edit the reason statement for the merge? I might, but usually, other users are adept enough to figure out what I was trying to express (I hope).0
-
Kathryn Grant said: I've wished for the same feature. Somehow I always catch typos *after* I post something
We can edit reason statements for attached sources, so why not allow the same thing for merge reason statements? In this case, though, I think only the person who did the merge should be allowed to edit their reason statement because it applies specifically to the action they performed. 0 -
Juli said: Change log reasons are an odd species: on the one hand, they're part of the change log, so they shouldn't be editable, because then what's the point of a change log; but on the other hand, typos happen and it would be good to be able to fix them. But if we do allow fixing them, then that should go in the change log, so now we've got a change log for the change log....
There was one case where my typo/error in the merge reason was big enough that I actually came up with another change to make (and unmake) just so I could add a new reason for change, explaining the preceding error. (It was a while ago, so I don't remember the details, but I think I edited the name. Nowadays that would be an especially easy one to use: just choose a different checkbox from the language drop-down.)0 -
Adrian Bruce said: An interesting point - however, my view would be that a Change Log for the actual values on a profile (dates, places, on Vitals and other information) should definitely be fixed on a Change Log - but reasons seem a step further removed. And if we add in Kathryn's sensible restriction to the original inputter, that removes the malicious or downright stupid.
So I'm willing to be persuaded either way....0 -
I have a little suggestion regarding the “Suggested Reason Statements” under Reasons for Merge.
It seems to me that quite often users will just click one of these reasons statements as their reason, without a clear reason for the merge. I’m wondering if it may be too convenient for some and it doesn't give other users much comfort that their reason is valid.
My vote would be to have all of us come up with our own written reason statements for any merge.
0 -
The suggested reasons are relatively new. In the preceding merge process, you just got an empty box. Most people left it that way.
One advantage of the canned reasons is that they all include both IDs. This makes it much easier to figure out what happened, especially when you're looking at a family member's change log, where the merge is expressed as a sequence of additions and deletions that otherwise make no sense.
1
