Standardized Places don't persist from Source Linker
Hi: I've noticed over the last 6 months or so that, even after standardizing place names with in the Source Linker, getting the little map pin in confirmation, when I go to the Person page where the record is shown, the place name for the just-added source has a red exclamation mark next to it. This is true even though that place name is actually the standard place name left by the standardization in the Source Linker. The workaround is to re-standardize within the Person page, which fixes it. However, this requires one to standardize place names twice, or to just give up trying to standardize them within Source Linker. Neither are very desirable. I've tried to describe this before but only get vague answers. Any ideas? I'm using Chrome browser, Win 10.
One more thing; it doesn't always happen. Seems like some kind of timing issue?
Best Answers
-
Hello @ScottStieg.
The issue you describe was first reported in April, but, as you said, seems to now be an on-again, off-again issue.
In your experience, has the problem been when attaching census records as sources? And, would you be able to provide us with screenshots of the problem? If you can provide an example we can investigate further.
0 -
Desktop iMac, Mac OS 11.4, Safari 14.1.1
I had this happen consistently today while attaching christening records. I'll go detach one I just put on, delete the info from Family Tree and go through the process again and so you can see what is happening:
Starting point:
I find her christening record:
Click "Attach to Family Tree" to enter the source linker:
I move over the christening information and the place looks standardized. I even have clicked on the place name and re-standardized it to be absolutely certain it is:
I click Attach, then leave the Source Linker and return to Kari's page to find that the standardized version of the place name was not attached:
This only seems to happen with places. The date was standardized just fine even though I left the display date as it was in the source. I have gone back and fixed both the date and the place so I don't forget to do so later.
Hope the work flow and screen shots help track down the trouble.
0 -
I've had this happen repeatedly with passenger lists and at least once with a census record. It especially doesn't like "New York City, New York, United States" when it comes from Source Linker. (Or so it seems.)
Checking My Contributions, it looks like my last "episode" was on July 14, with New York passenger lists. It did not happen with the Hungary Civil Registration records that showed up as indexed yesterday. (Granted, those generally don't have data to transfer via Source Linker.)
0
Answers
-
Hi; It's Scott Stieg again. It happens with place names, in all sorts of records including many many census records. You can see the screen shots from above; it's exactly the same symptom: the standardized place name shows the map pin in Source Linker, but in the Person page, the exact same standardized place name has a red exclamation mark next to it. It seems like it gets worse the longer my session is, like something is getting behinder and behinder. That's everything I have to offer.
0 -
Just want to suggest that you try to delete the cookies and temp. internet files from your browser.
As you said @ScottStieg it gets worse the longer your session is. Seems as though attaching sources creates a lot of cookies and this can lead to some problems.
Generally speaking if things are not working as they should in FamilySearch first thing to try is clear your browser.
Personally I clear my browser daily if using FamilySearch a lot.
Try it and see if it helps.
1 -
More than a decade ago, when I was serving in FamilySearch support for The "New Family Search," item after item in the Knowledge Base gave, as the work-around for a multitude of problems, "Clear your Cookies!" It seems that nothing ever changes.
I'm not a database engineer, so I don't really understand how cookies work, but why on earth must FamilySearch forever allow cookies to cripple it? Is the system hopelessly wedded to such high caloric intake? And where is Cookie Monster when you need him?
2 -
Hi It's Scott Stieg again; just wanted to point out that this problem still happens within the Source Linker, in place names, in all sorts of fields; marriage places, birth places, etc. The text that appears is exactly to the letter the standardized place name but is marked with the red exclamation point. This is a serious bug as it wastes a lot of time having to re-standardize place names that are already letter-perfect. I sure wish someone would look into this. All the screen shots you could ever want are above. Please don't ask me to clear my cookies again or I will lose them!
2 -
I have been getting this bug daily for the past week.
1 -
Here's another odd thing that might be related. See
- Notice the (incorrect) birthplace shown in the right pane: "Philadelphia Monthly Meeting, Philadelphia, Pennsylvania, United States" Now, look at the actual birth place in the person: 27DW-TYM. It has "Philadelphia, Philadelphia, Pennsylvania". Not wrong but not standardized yet.
The "Philadelphia Monthly Meeting, Philadelphia, Pennsylvania, United States" is a standardized place, but it is wrong. It's below the correct standardized place in the place pick list.
0 -
"Philadelphia Monthly Meeting, Philadelphia, Pennsylvania, United States" is an unrelated problem. I have been seeing it for years, literally, whenever the actual text in any event place name is "Philadelphia, Philadelphia, Pennsylvania, United States".
1 -
Huh, strange. Maybe a stealth plug for the Quakers, ha! I guess I was just doing a lot of Philadelphia. But, bug, nonetheless; shouldn't it just show whatever unstandardized text is in the Place field?
0 -
- Marion, Ohio, United States
0 -
Hi; I'm commenting on this bug that has persisted now for quite some time. It looks like it's getting better; don't know, of course, if any work has been done on it. However, places like this one consistently fail to remain standardized as they are attached in the Source Linker:
Marion, Ohio, United States
that is, of the form County, State, United States. These always fail and have to be re-standardized within the person. As usual, no actual change is needed in the place's text, just the action of standardization fixes it. The original text within the Source Linker is always marked as standardized, with the little map pin symbol.
0 -
I just replicated, as shown in screenshot.
0 -
Hi it's Scott Stieg again. Just wanted to point out this bug is as virulent as ever. I have to constantly re-standardize perfectly standard place names in census and marriage event fields. I sure wish someone would fix this as it wastes a lot of time. Yes, I cleared browser, etc. but has no effect.
0 -
Hi, it's me again. Just wanted to point out that this bug still persists, although it seem to have shrunk to affecting only marriage and burial places.
1 -
Yes. I am seeing this bug consistently on marriage records. Including some worked today.
Also, it is only on the web interface. Mobile app is fine.
0 -
On a PC, chrome browser, hiccup persists 4 days, US census Columbus, Platte, Nebraska 1860 to 1880. THANK YOU in advance to programmers team to fix.
0 -
Scott Stieg again; this years-long bug still exists, and in all place fields, not just marriage. Today I noticed that a place like "Schwetzingen, Baden, Germany" will not standardized, but if you select instead "Schwetzingen, Mannheim, Baden, Germany", it works fine, no problems. I wonder if the standard place only has three pieces, it fails. This is very consistent today. Take a look at Karl Friedrich Breitenbucher
• G61D-XM1
- 16 September 1915 – DeceasedI sure wish someone would take this seriously as it is a great time-waster, it's been going on for years and only FS has the resources to fix it.
0
