ViewsWatchers |
This change may not be too hard? Some people add Married Name to pages. This is presumably to help searching. Clearly this is extra work to do. It also adds a maintenance headache in that any correction to married surname on the Family page (i.e., change to spelling, correction of husband, addition of marriage) may need to be updated on the Person page, but since the change to data is done on the Family page (and to data nominally belonging to the husband), the poster may not be aware that a parallel change is needed on the Person page for the wife to keep things in sync. The inconsistency of use (some pages have this feature, some do not) is not optimal. I suggest generating Married Names to wives automatically when a page is saved, for each Family page representing a marriage, unless the married name is the same as their maiden name or a previous marriage (no harm in duplicates except clutter). Since, in some cases, this might not be valid, perhaps something like the nomerge template, e.g., {{nomarriednames}} (on the page? on the Talk page?) could be the signal to skip this step. Not only would no Married Names be generated for that person, but all existing Married Names would be left unchanged, so that pages with this template would reflect only what is put there manually. --Jrich 21:56, 9 October 2020 (UTC)
I agree that married name is a maintenance headache and would like to see WeRelate strongly discourage its use when the family page exists. WeRelate already searches for the spouse's surname based on the family page (and has for years) so there is no need for married name unless the family page is not created in WeRelate (e.g., all you know is that someone is "the widow Smith"). If I am updating a page and note that the married name is no longer accurate (spouse's name was incorrect), I just remove it rather than fix it (faster) - it is entirely unneeded. Same if the married name is entered as the first name (probably an early GEDCOM upload bug, given how common it is). (I should note that I don't just remove names if the contributor is still active - I would communicate first, but generally I just leave it alone or correct it if I am correcting the husband's surname. If it is clearly additional information, I leave it alone as well.) My background is in data, including database design, and one of the strongest rules is to avoid redundancy of data whenever possible - because it is very hard to keep it in sync. If someone changed their name due to immigration (new culture), I use "immigrant name" instead. As far as I am aware, that's what it is there for.--DataAnalyst 22:23, 9 October 2020 (UTC)
I would much prefer NOT to have a married named added automatically from the family page -- in quite a few countries/societies women retain their maiden name with marriage and it would create a real mess and/or a major bit of work if they all had to be deleted or prevented with the addition of a template. As for people who enter a married name that is already evident from the Family Page, I find that much less annoying than having every source on the page added as a source for the name at birth, but some people do seem to derive some comfort from doing so. --GayelKnott 04:34, 10 October 2020 (UTC) |