Whenever I attach a source I faithfully ensure that I standardise the date and place before saving. However, the saved version gives an error message that no standard has been chosen and I have to go back and standardise the information again. This is something new and was not a problem in the past.
Yes, this is a well known bug in the source linker tool. It seems to be getting worse.
It is bad enough that I have stopped standardizing place names in the linker.2
Yes, it is driving me crazy. Why give the patron a chance to select a standard place if the Source Linker just ignores the patron's choice? If I remember correctly, selecting the standard place in the Source Linker used to work. I think that a bug was introduced a few months ago.
It should work something like this:
In the Source Linker, detect whether the patron has selected a standard place. If so, transfer the patron's choice to the individual's record. If not, then place the original form of the place in the individual's record.
Instead, what is now happening is that the original form of the place that is in the source is ALWAYS being transferred to the individual's record, and the patron's choice is ALWAYS being discarded!0
I have seen records where the standard was indicated in the source linker without any action by me, and then got the red exclamation flag on the profile.0
I can't find an example right now, but I believe the error happens even if the "original form of the place" is an exact, letter-by-letter match to the standardized place.
Yet another reason to be glad I work mostly with unindexed records....0
Paul W ✭✭✭✭✭
I have just added five children via the source linker, carefully ensuring each one had the correct, standardized birthplace before they were "moved across". As reported by others, I then had to go back and carry out the whole exercise again on their person pages.
Would a FamilySearch employee please at least confirm this issue is being looked at?3
I have experienced exactly the same problem at least a month after the comment was first reported0
Yes, this problem continues. I am experiencing it today.0