Month shift when integrating indexed event date to profile
When a record hint finds an existing record and new event date fields are available, they are sometimes modified when the Add button is pressed.
I had to review a dozen recent records and correct a few of them, as I didn't notice the shift and submitted my changes.
I pay attention to it since then, but I believe it would be better to find the root cause and fix it.
Thanks
Best Answer
-
This is another case where you can go into the actual index and potentially fix the problem. As far as I can see it is isolated to just this record and the one before it. The third record on this page and all the records on the previous page and following page all have not translated the month at all or have translated it to English correctly:
I don't know if correcting the date will correct that source date, but I hope so.
At least in this record set there are only two copies of each birth instead of 21! So if correcting the index does not fix the source date, then you can delete this incorrect one and leave the correct one which follows it:
3
Answers
-
I can see problems especially for November, which is shifted to October. I've just noticed a mismatch in the attached record:
https://www.familysearch.org/en/tree/person/sources/PQZX-PY6
The Event Date field is in Czech. "Listopad" means November in English, but the Source Date is set to October.
It looks like it is the Source Date what is injected to the profile, hence the difference.
So this doesn't seem to be a general issue, but this collection problem.0