Name inconsistencies (maiden vs. married)
When a last name is the same as a husband's, and a maiden name is discovered, this ideally would not show up as an inconsistency. The "canned" explanations in the old merge function is a convenient shortcut, although not very descriptive. Perhaps new "canned" explanation buttons could be provided? Meanwhile, I am switching back to the old version.
Comments
-
Just anther curious user: In the situation you ran across, was the married name entered as an alternate name? The Data Quality Checker looks at alternate names when looking for name inconsistencies but I don't know if the new merge function does or not or whether it should.
Also, specific examples of what is not liked really helps the developers. If you post the ID numbers of the two people you were merging so they can recreate the situation, see what might annoy people, and fine tune things can really help improve new routines.
However, since a married name should not be entered under the Vitals section in the first place, it sounds like the new merge routine actually did a good job pointing out an error.
1 -
It is pretty common that the married names of females appear in the Last Names field in the main Vitals Name area, even though that is not preferred. And it is relatively uncommon to see a married name in the Alternate Names section. Thus, after turning on the new "merge experience," I ran into this issue several times, and it does not seem reasonable to have to manually explain this every time. My suggestion would be to have the "software" always assume that all of the last names of attached husbands be considered Alternate Names, and that the new merge function not require a manually typed explanation in these situations. It can post a little note on the merge screen next to the name that it appears to be a maiden vs. married name—just not require an explanation.
This raises a question I have always had about the Family Tree. I have assumed that the married names are included in the algorithm that generates hints, etc., so I never do the busy work of adding married names to the list of Alternate Names for all of the women. And I think the vast majority of female PIDs do not include all of those married names. Am I correct on this? Does manually adding the married names to the list of Alternate Names help the hints/search in any way. I would think the married names should just be assumed without explicitly listed in the Alternate Names. In fact, leaving the married name out of the list of Alternate Names should actually be preferable to avoid hints/matches between women with a maiden name that matches another woman's married name.
I only enter a married name in the Alternate Names area if the name is completely different than expected (e.g., when a woman keeps her maiden last name and hyphenates it with her husband's name).
0 -
Yes, adding the married name as an alternate includes it in all hinting routines. Whether that is beneficial or not depends on your point of view.
Also, I would assume the system is designed to function best when the data is entered as the program expects it to be:
I would take that notice in the merge section that we should be taking the opportunity to improve the profile by getting married names out of the Vitals section.
It would be interesting to know if having a woman's married name in the alternate name section suppresses the inconsistency. I'm mainly working in a time period in Norway when women did not take married names at all so I won't be running into any examples. If you do and are willing to take the time to experiment, it would be interesting to hear the result.
0 -
Thank you for the time that you have spent trying out this beta project. It is important to remember that the algorithm is only looking for data inconsistencies in order to prevent bad merges. The algorithm does not evaluate the content for accuracy.
0 -
@SteveLinke
What did you like about the old "canned" explanations?
Do you have any suggestions for new explanations?0


