Why are no data warning flags appearing on this page?
I just picked up that a user has recently entered marriage and chrsitening dates against L88T-77Y that could not possibly relate to this individual (marriage before christening, children born before parents, etc.). I am wondering why no data warning flags are showing, as is the usual case when such data conflicts appear. Is there a bug that is preventing the "red flags" from appearing?
Update - I just figured out why there is no flag for the children apparently being born before the parents: no birth dates have been inputted, only Christening fields completed. So, maybe this is always the case - even when a marriage is involved - as, in theory, a child could be baptised (or born) in the 1690s and the parents not married until the 1730s. There does seem to be some inconsistency here, however, as christening dates are used as a substitute for a missing birth date in pedigree views, etc.
I've probably answered my own question, but thought I'd leave the post here to at least highlight the different way FamilySearch treats christening / births (as well as "before" / "after" inputs) on different Family Tree pages.
Answers
-
As an open tree, everyone has access and can make adjustments to the tree as they believe correct, the warning usually pops up especially in your issue at https://www.familysearch.org/en/blog/correct-mistakes-family-tree , but people can easily override these warning without consequence, with the exception of your family member being married before they were born. You can see who made these changes and when they were made by checking the last changed information on the page such as below. I removed the actual name, but if desired you can click on the name and it will create a screen to allow you to contact them to see if maybe they have some facts or just made a mistake,
However being an open source you can just correct the error placing an reason as to why it is incorrect and repair any relationship issues. You can find instructions for this at the knowledge article Correcting Mistakes. Hope any of this helps in your research at FamilySearch.
0 -
Thank you for your response, but I had already intended to contact the user concerned (via Chat) and to make the necessary adjustments / deletions myself. As you will see, I updated my comments (just as you were responding) to note that I quickly realised, in this instance, the program is not designed to substitute christening data for a missing birth input. I can understand the logic, but got confused due to the lack of consistency when it comes to, say, the landscape page - where a christening date is used if no birth date has been completed on the profile page.
2
