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

Correct the birth year

System
System admin
February 13, 2023 edited July 11, 2024 in Family Tree
This discussion was created from comments split from: Make Correction.
0

Comments

  • MaryMurray3
    MaryMurray3 ✭
    February 11, 2023 edited February 11, 2023

    How do I correct an incorrect birth year?

    4417A5C5-A0E2-412F-A85F-847C6BB03A36.png


    0
  • N Tychonievich
    N Tychonievich ✭✭✭✭✭
    February 11, 2023

    @MaryMurray3 Is this the record you are attaching? (My best guess based on your screen shot of the source linker): https://www.familysearch.org/ark:/61903/1:1:FZT1-JYC. Since the edit button is grayed out for you on this record set, you will not be able to correct the inaccurate birthdate. When you attach something that has an indexing error such as this, we suggest that you make note of the error in your "reason to attach".

    https://www.familysearch.org/en/help/helpcenter/article/why-cant-i-fix-indexing-or-transcription-errors


    1
  • Maile L
    Maile L ✭✭✭✭✭
    February 13, 2023

    Hi @MaryMurray3 It looks like you were able to edit Mildred's (LWG4-BJH) vital info so that it contains the correct birth year. Please let us know if there is anything else you needed help with. Maile 🙂

    0
  • D Michael Byler
    D Michael Byler ✭
    March 12, 2023

    When I was first entering the birth year for John Philip Smeltzer (1938-2022) #GJ6J-6NF, I typed 1928 in error. Now I have correctly entered his complete birth date under “details” as 31 Mar 1938. But the software has not corrected the erroneous date 1928 under the introductory information with his name & photo & Family Search ID. And there is apparently no means for me to make such a correction. What shall I do? Thanks.

    0
  • Julia Szent-Györgyi
    Julia Szent-Györgyi ✭✭✭✭✭
    March 12, 2023 edited March 12, 2023

    @D Michael Byler, when you corrected the date, you didn't update the associated standard.

    image.png
    0
  • Gordon Collett
    Gordon Collett ✭✭✭✭✭
    March 12, 2023 edited March 12, 2023

    By the way, the dates acting like this is not a programming error or flaw. It is a powerful feature of Family tree that is often not noticed or is misunderstood. This property of being able to edit the displayed date without updating the standard allows for accurate entry of genealogical quandaries.

    Say you have a record that clearly states someone was born on February 29 in a non-leap year. You do not have to decide between entering February 28 or March 1, neither of which you can be sure is the right date. You can enter one of those dates then edit the date to put in what the record says (along with a good reason statement and source):

    Screenshot 2023-03-12 at 8.16.09 AM.png

    You sometimes need to use this technique to enter double dates and often need to use it for named dates. You don't need it near as often for dates as you do places, but it can come in very handy.

    1
  • D Michael Byler
    D Michael Byler ✭
    March 13, 2023

    Thanks for the responses. I now corrected the standardized date & everything is fine.

    0
This discussion has been closed.
Clear
No Groups Found

Categories

  • All Categories
  • 42.7K Ask a Question
  • 3.3K General Questions
  • 570 FamilySearch Center
  • 6.7K Get Involved/Indexing
  • 640 FamilySearch Account
  • 6.5K Family Tree
  • 5.1K Search
  • 996 Memories
  • 2 Suggest an Idea
  • 473 Other Languages
  • 62 Community News
  • Groups