Standard Event Date Setting will Not Save Correctly
I cannot set a standardized event date of "None of the above" in the Standardized event Date field. In many situations I have a date but no year. I need to enter the date that I do have. It is ok, and in fact desired, to have a data error marker there as a reminder that that date is incomplete.
I go to edit a Birth Date and get the following:
I then select "None of the above" and then get the following which is exactly what you would expect:
I then select "Save" which returns me to the details page. But something is wrong. The date is being displayed as though it was standardized (i.e., no data error):
To see what has happened, I go in and Edit the Birth Date again and see this:
It now is obvious that when I hit "Save", the value I had entered was NOT saved, and in fact was thrown out as though I had Canceled the operation. Furthermore, the default being put in shows a default standard value year of 0010 being entered. This throws up several meaningless data errors on the record (e.g., born before father, etc.).
This is a complete nuisance. I have several records where I have the day and month but not the year yet. The day and month by themselves are quite useful, but having all kinds of meaningless data errors because the system put in a meaningless standard date is less than useless.
Also note that these incorrectly assigned default standard date values look suspiciously similar to the screwed up dates that have been showing up in the Ohio County Marriages record collection:
This situation has also come up before in the legacy topics:
https://community.familysearch.org/s/idea/0874V000000siibQAA/detail
https://community.familysearch.org/s/idea/0874V000000siZiQAI/detail