Standardized place not standardizing.
When creating a new person, I click on the standardized birthplace that's shown. After created, it says no standardized birthplace. Then after editing it's okay.
Have you resolved your problem or is there something that can be done to assist you?
If you need assistance, could you please list the person's name, Person ID, and the place you are having difficulty with.
If you do not need further assistance, mark this comment, as yes the question was answered. Thank you so much for using FamilySearch.0
This is normal. When you click on the standards menu that is detached from the name text field you are just looking at the choices. Instead, click on the place name text field. A drop-down menu of the same standard names will appear. Select one. If no standard is appropriate, edit the text field. An appropriate choice should then appear in the drop-down menu.
If there still is no appropriate standard, on the web interface scroll to the bottom of that pull-down menu and select "None of the above". I specify on the web because currently on the mobile app this menu is lacking "None of the above".
To request a new standard place name, click the "I"-in-circle.0
Were you adding the birth information from the source linker? If so, there is a known issue with the standardization process in the linker. It seems to be an on-again, off-again problem. If the standardized place does not persist after the source is attached, you will have to manually standardize it again in Vitals.0
@MNuttall , I have been seeing that exact problem with the source linker this week.
But it sounds to me like @cdungan3973784 is having a different issue.0
Thank you for taking the extra time to be sure the information is standardized. Have you tried to refresh your screen after adding the place name originally? Doing so may eliminate the need for editing.
Let us know if you concern is resolved.
Good luck with your work on Family Tree.0
Hi: I reported this issue several months ago: in brief, the standard place appears in the Source Linker, but when you look at the event within the Person, it shows as unstandardized, and you have to re-standardize it. I tried all sorts of tricks to see what would affect it, but this annoying bug still happens.
Today, I found that, when in Source Linker fields, you INSERT the place before the existing text, the standardized place 'takes'; i.e., it remains standardized within the Person's event when you go look at it afterwards. However, again in Source Linker fields, if you OVERWRITE the the place with the standardized place, it does not 'take', and this is when the problem above occurs. I've tested this several times and it seems to be the first clue as to how to reproduce this problem.
This is why it happens often in the 1940 US census entries, which have "Same Place" in the 1935 field. I often just overwrite "Same Place" with the same place as 1940 and this one does not take.
Fields that are neither inserted nor overwritten but just standardized from existing text seem to 'take' OK.
I sure wish someone would look into this. I pled my case several times in the plast and got the usual platitudes about deleting cookies, and other not helpful advice. This bug is a real time-waster as it causes one to have to re-standardize 100s of fields.0
Thank you for the update you included here.
We are forwarding your concern to a specific department for review. You may be contacted by them if they need more information.0
I too am still seeing this annoying bug in the source linker. I handle the event place names exactly the same way every time. Some days they all "take"; other days they don't.0
This is still an issue. When a person needs to be created during Census source linking, I know I updated the Birthplace to be a Standardized Event Place but afterwards when reviewing the person, there is a 'Data Problems' message saying "Missing Standardized Birthplace". User ID GDQR-H6T is an example.2
Thank you for the update about the Census source linker and Standardized Event Place problem. We are forwarding your report to a specialty department so they have another example. You may be contacted by that team is they need more information.0
If more examples are needed, there is 938G-TB2 birth date. Also GD7W-JK6 residences.0