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

Header dates don't match detail dates

Options
  • Mute
W Andrews
W Andrews ✭✭✭
December 21, 2023 edited September 26, 2024 in Family Tree

From census records, the estimated birth year was originally set as 1913. Later, from a headstone, I found the exact date; 31 Jan 1912. However, the birth year in the header remains 1913. There does not seem to be a way to update the header nor is there an explanation as to why it cannot be updated. See attached

Dates don't match.PNG

Tagged:
  • Active
1

Answers

  • Julia Szent-Györgyi
    Julia Szent-Györgyi ✭✭✭✭✭
    December 21, 2023 edited December 21, 2023

    When you edited the date, the associated background ("standardized") date failed to change. You can see this if you hover your cursor over the date in the Vitals box.

    image.png

    To fix it, click the Edit (pencil) button to the right of Birth, then click in the Date of Birth box of the resulting popup.

    image.png

    On the resulting drop-down, choose the bottom option (with the calendar icon) to make that both the display value and the associated background value.

    If you want to keep the month abbreviated in the display value, then the procedure starts out the same: click the pencil, then click in the Date of Birth box. However, don't click either of the choices in the dropdown; instead, click somewhere else on the popup (such as in the reason box) to close that dropdown. Then, click the "v" to the right of the Standard Date.

    image.png

    Choose the top option (with the calendar icon) to make that into the associated background value, while keeping the abbreviation for the display value.

    image.png image.png

    Unfortunately, the logical procedure -- going straight for the "v" on the standard if what you want to change is the standard -- doesn't work: if you do that, then the choices are "same as before" and "no standard".

    image.png

    I do not know why it's set up illogically like this. I do know that there are other ways to achieve the abbreviated-display plus correct-background setup, but my "click outside the box" method is I think the least alarming way of doing things.

    4
  • Maile L
    Maile L ✭✭✭✭✭
    December 21, 2023

    Mod note - moved to Family Tree category

    0
  • Gordon Collett
    Gordon Collett ✭✭✭✭✭
    December 22, 2023

    I have wondered about the current design on and off. And this post has got me wondering again and I've got a couple of random thoughts.

    If there is an existing display place name linked to an existing standard, there are three editing options:

    1. Change the display name and change the standard.
    2. Change the display name and keep the current standard.
    3. Keep the current display name and change the linked standard.

    For all three options the standard list dropdown menu is locked until you activate it by doing something to the displayed name. That dropdown then stays active until you have chosen a standard then it gets locked again.

    Maybe the consistency of the sequence: Touch display name, activate standards menu, makes the whole routine so much simpler to keep working right that it was felt best to keep that consistency. Or maybe there was some concern that being able to change the linked standard without confirming what you want the displayed name to be would lead to more incorrectly linked place names rather than fewer.

    But whatever the reason is, I do find that it works just fine to correct the problem seen here by clicking on the display place name to open that menu, clicking on the rust text just as if you were entering it for the first time, then clicking on the standardized version to correct it, when it works.

    This is the way it is supposed to work: https://youtu.be/rbaVaHO_Llg

    However, there is a bug in the routine for dates in that this does not alway work properly (See: https://community.familysearch.org/en/discussion/comment/534929

    For example, I just tried again and correcting a date standard is no longer working:

    When it is broken: https://youtu.be/hSjeqLMDqT0

    I hope they are still trying to fix this. It does always work properly for place names.

    1
This discussion has been closed.
Clear
No Groups Found

Categories

  • All Categories
  • 43.3K Ask a Question
  • 3.4K General Questions
  • 576 FamilySearch Center
  • 6.8K Get Involved/Indexing
  • 653 FamilySearch Account
  • 6.6K Family Tree
  • 5.2K Search
  • 1K Memories
  • 2 Suggest an Idea
  • 480 Other Languages
  • 62 Community News
  • Groups