Home› Welcome to the FamilySearch Community!› Suggest an Idea

Allow an Individual Record to be Moved Alone or with Attached Relatives

DannyHooge
DannyHooge ✭
March 3, 2022 edited March 7, 2022 in Suggest an Idea

Considerable duplication occurs when patrons create new records because a record for

an existing person is attached to other relatives and some information may be inaccurate.

Modify the software so that an individual record may be moved within FamilySearch with

relatives detached or attached. With this function, there will be no need to create an additiional new record. Thank you.

Danny Hooge

Tagged:
  • Not Planned
1
1
1 votes

Not Planned · Last Updated March 7, 2022

As this works as intended, we are not planning on changing anything.

Comments

  • Gordon Collett
    Gordon Collett ✭✭✭✭✭
    March 3, 2022

    As people come to understand Family Tree, they will, ideally, quickly come to understand that there is never a need to purposely create a new record for an existing person. Teach everyone you know this is the case and that the the purpose of what the CEO of FamilySearch repeatedly called in his RootsTech keynote presentation today the Family Tree of Humanity is to have one single record for each person.

    If person already exists in Family Tree then there is only a need to refine, expand, and correct information on that one record. There is no need to move anyone anywhere. We can already edit anything we need to on a person to correct the individual's personal data and family relationships.

    If someone sees a need to disconnect a person from all parents, spouses, and children in one key press, then there is probably a high likelihood that someone is trying to turn an existing person into a completely different person. This should probably never be done.

    In the rare situation it might be needed, the user ripping a person out of a complete family really needs to take the time to edit each family relationship one at a time with full documentation on each severed relationship as to why this is being done.

    0
  • dontiknowyou
    dontiknowyou ✭✭✭✭✭
    March 6, 2022

    In my view the user interface already is adequate for this task. When it is just wrong parents, they are easily left behind during merges.

    This is a problem of users not understanding how to use the user interface. This very general problem is not necessarily resolved by making the interface more complex.

    So, no upvote from me but thank you @DannyHooge for the suggestion.

    0
This discussion has been closed.
Clear
No Groups Found

Categories

  • 28.7K All Categories
  • 23K FamilySearch Help
  • 115 Get Involved
  • 2.6K General Questions
  • 426 FamilySearch Center
  • 436 FamilySearch Account
  • 4.2K Family Tree
  • 3.2K Search
  • 4.5K Indexing
  • 595 Memories
  • 6.2K Temple
  • 311 Other Languages
  • 34 Community News
  • 6.4K Suggest an Idea
  • Groups