Menu

Multiple Name Change

Help
monty124
2009-04-27
2013-05-30
  • monty124

    monty124 - 2009-04-27

    Hello.

    How can i show multiple (yes multiple) name changes (not marridge name changes, these are "deed poll" (not sure what you guys call them) changes) for a person in the GUI?
    should name changes show in the individuals page for each surname or only for the last adopted surname?
    should deed poll changes be shown or should only the last adopted surname be shown?

    i added entries in the GEDCOM but it did not show up, unless i am doing something wrong.

    these are real names from the GEDCOM this time ;)

    at #3 there was a single parant child and the name changes/display of the name changes will make more sense for the childs record... i would think at least.

    2 SURN Jones
    3 SURN Williams
    4 SURN Jones
    2 _MARNM Mary /Street/

    this is an isolated case and i am happy to do these changes directly into the GEDCOM but it would be nice if they showed in the GUI.

    Do i need to reimport for direct GEDCOM changes? or are my edits incorrect.

     
    • Stuart.G

      Stuart.G - 2009-04-27

      I would enter them as "Also Known As" or AKA, with  TYPE. In the TYPE field enter "By Deed Poll" or whatever.

      To add AKA and TYPE to the GUI, go to Gedcom Edit -> Edit Options and go to the line - Advanced Name facts and enter _AKA  and TYPE to its field. I have:

      NICK,_AKA,TYPE

      I hope that helps.
      --
      Stuart

       
    • Greg Roach

      Greg Roach - 2009-04-27

      The "gedcom spec" way is to have multiple NAME records.  Use the "add new name" from the indi menu.

      If you are exporting your data to a desktop application that only recognises single NAME records (e.g. FTM), then you can use the _AKA custom tag.

      The first method allows you to add sources, notes, etc to each name.  I use this method.

      Greg

       
      • monty124

        monty124 - 2009-04-27

        thanks that seems to do the trick!

        but do i need to add another instance of the original name? or just leave the born name in there?

        so born with jones
        changed to williams
        changed back to jones
        then married street

        2 SURN Jones
        3 SURN Williams
        4 SURN Jones
        2 _MARNM Mary /Street/

        or is there a sequence to entering the names in?
        born, name change, name change, married

        i think thats how you do it, that way it shows the history of changes...

         
    • Stephen Arnold

      Stephen Arnold - 2009-04-27

      Monty
      Greg is suggesting

      1 NAME Mary /Jones/
      2 TYPE birth
      2 NOTE Mary's mother was unmarried and Mary was given her mother's surname as his father was not known.
      1 NAME Mary Williams
      2 TYPE Poll Deed
      1 NAME Mary /Jones/
      2 TYPE adopted
      2 NOTE Mary reassumed his last name after her mother married, this time to James S Jones, and she was adopted.
      2 _MARNM Mary /Street/

      Stuart is suggesting

      1 NAME Mary /Jones/
      2 GIVN Mary
      2 SURN Jones
      2 _AKA Mary Williams
      2 _MARNM Mary /Street/
      2 NOTE Mary was given her mothers surname at birth as her father was not known. From a Poll Deed, she had the name Mary Williams. Later, her mother married James S Jones and Mary assumed that surname as she was adopted. Upon her marriage to Jack Street, she then took his surname as hers.

      Either is appropriate, depending on how you wish to record the information. PGV has some issues with displaying more than two 1 NAME records in the header and only the first listed 1 NAME record will currently appear in charts. There is, IIRC, an RFE to display multiple 1 NAME records in all places.  Either way, the names will 'hunt' via any search.
      -Stephen

       
      • Stuart.G

        Stuart.G - 2009-04-27

        It is for the reason that Stephen states that the headers look really messy even with two 1 NAMEs, especially if you want to have notes for each. Using _AKA and the TYPE and then writing one note to cover the lot presents better. I have one person known by five names. This was a real mess until I changed.
        --
        Stuart

         
      • monty124

        monty124 - 2009-04-27

        Thanks all!

        i think i will use greg's suggestion, the notes are what i'm after.

         
    • Thomas52

      Thomas52 - 2009-04-27

      I know it looks 'busy,' but I have:
      1 NAME Anneke /Jans/
      2 GIVN Anneke
      2 SURN Jans
      2 _MARNM Anneke /Jansz/
      2 _MARNM Anneke /Janzsen/
      2 _MARNM Anneke /Bogardus/
      2 _MARNM Anneke /Bogaert/
      2 _MARNM Anneke /Webber/
      2 _MARNM Anneke /van Masterlandt/
      1 NAME Annetje /Jansen/
      2 GIVN Annetje
      2 SURN Jansen
      2 _MARNM Annetje /Bogardus/
      ... the second NAME as an"add name," but it was the only way to give my visitors the ability to search all the spelling variations used.  I may switch to the "AKA."

       
  • John Walker

    John Walker - 2010-05-16

    With the change of name by deed poll, which name should be the 'primary' name according to gedcom standards?

     
  • Gerry Kroll

    Gerry Kroll - 2010-05-17

    Wouldn't the most recently used name be the primary name?  I'd make sure that this name is first in the list.

     
  • John Walker

    John Walker - 2010-05-17

    Thats what I am thinking. And their previous name would be an AKA. But just wondered what the convention for the gedcom is.

     
  • Greg Roach

    Greg Roach - 2010-05-17

    When you have multiple values for something, the gedcom spec says to put the "prefered" one first.

    It is up to you to define "prefered".

     
  • Gerry Kroll

    Gerry Kroll - 2010-05-18

    Actually, I'd insist on "preferred".

     
  • John Walker

    John Walker - 2010-05-18

    It probably makes more sense to use the new name (the one changed by deed poll) because this persons children will more than likely be known by that name… if its a man who changed their name or an unmarried woman.

     

Log in to post a comment.