Home› Welcome to the FamilySearch Community!› Ask a Question› Family Tree

Fix TIMELINE to show more accurate family relationships

Bill Kaczmarek
Bill Kaczmarek ✭✭
May 21 edited May 21 in Family Tree

As it stands now, the Timeline lists births of children when they happen. This is so with StepChildren too, listed as "children". And when a future marriage will later make a person a step-child, they are still listed on Timeline as Birth of a "son" or "daughter" , even though Step-son or Step-daughter would be accurate. Or more accurate yet, would be Future Step-Son or Future Step-Daughter.

Here's an example:

I was just corresponding with a relative in Poland who pointed to something that might be improved.  Have a look at https://www.familysearch.org/en/tree/person/timeline/G4DF-9V7 which is the timeline for Mikolaj Kador.   

It shows "birth of a daughter", which is confusing, for Marianna Wroblewski.  

Marianna is born at that time, that's true, but she is a future step-daughter, rather than a daughter.   "step-daughter" is less confusing.  "future" may be too much to ask for ;-)   

Tagged:
  • Labels
  • bug
2

Answers

  • Paul W
    Paul W ✭✭✭✭✭
    May 21 edited May 21

    @Bill Kaczmarek

    I just noticed that when adding a relationship type there is an option to add a date. I wonder if a date has been added in the example you reference? If so, I would agree that this is the event date that should show on the Time Line.

    After writing the above, I decided to test this out myself and was disappointed to find the fact that a child is marked in a step relationship and that the relationship did not begin until twenty years after the child's birth made no difference at all.

    In my example, in spite of marking a "child" born in 1930 as "Step" (instead of "Biological") and that that relationship didn't occur until 1950, the 1930 event for the birth of a "child" still remained on the Time Line, instead of an expected placing in 1950 for having a "stepchild".

    I would agree the Time Line is currently presenting a totally misleading picture and that the issue needs to be addressed in order to present an accurate recording of the facts.

    2
  • AnneLoForteWillson
    AnneLoForteWillson mod
    May 22

    @Bill Kaczmarek and @Paul W Would you put this in the Suggest An Idea section, please? That will get it to the engineers who can fix this type of thing.

    0
  • Bill Kaczmarek
    Bill Kaczmarek ✭✭
    May 22

    done. Thanks Anne

    0
Clear
No Groups Found

Categories

  • All Categories
  • 43K Ask a Question
  • 3.4K General Questions
  • 571 FamilySearch Center
  • 6.8K Get Involved/Indexing
  • 644 FamilySearch Account
  • 6.5K Family Tree
  • 5.2K Search
  • 1K Memories
  • 2 Suggest an Idea
  • 476 Other Languages
  • 62 Community News
  • Groups