Is anyone aware of this issue?
does not display United states and after poking it a bit I can't seem to make it do so.
Thoughts?
Answers
-
I am aware of this issue! That doesn't help, but solidarity and all that. I actually came to see if there were any threads on why I'm getting Italy in Alabama and Poland in South Carolina - now I see Norway and Denmark in the general US queue. Whimsical, but probably not optimal.
2 -
I am running into this bizarre change. First Findagrave and now Census. Which point to the culprits in programming section of FamilySearch. Seems the programmers are not thinking of whole locations, rather think of only the city, town, etc. Yes there are towns, census designations, cities named Alabama, Poland, Norway, Germany, Denmark, even Wales. Get it?
I had to force the corrections.
0 -
@pauli133 @W D Samuelsen contact me please could you provide example URLs please?
0 -
I had no problem getting records/profiles from the USA to display.
From the URL provided by @Michael J. Allen, "United States of America" is prepopulated. Then a state needs to be selected. I've tried several, and all populate correctly.
0 -
Hmmm. When I choose Oregon I get United Kingdom.
1 -
New Jersey gave me New jersey.
However . . .
Alabama gave me Italy
South Carolina gave me Poland
Oregon gave me U.K.
1 -
Alabama showed Italy,
Arkansas showed Denmark,
Nebraska showed Norway,
Oklahoma showed Panama,
Oregon showed the UK,
South Carolina showed Poland,
South Dakota showed Cook IslandsAll the other states were correct for me.
3 -
Same problem involving Findagrave have already been reported and in process of getting fixed. There iver 50 cemeteries with same name like Mount Hope Cemetery, and the first one is usually California when I wanted the one that's in Oregon. Hints still come in with wrong state for addition.
Census is showing same problem now. Right town, wrong state. Portland, Oregon is bad. Prior to 1940, was completely one county - Multnomah, and now it show up as Washington or Clackamas even the address is in the MIDDLE of the city far from those 2 other counties. Original hints of "event place" are always correct BUT for adding the hints, they show wrong ones, requiring manual entry to force acceptance of correct places.
0 -
If I click through to Global Hints, I get https://www.familysearch.org/en/campaign/hints-global?location=UNITED_STATES (I have no idea if that's the default everywhere, or just in the US). Right now, the three choices I get below the map are
https://www.familysearch.org/en/search/linker?ark=%2Fark%3A%2F61903%2F1%3A1%3AQLDC-6XBX&id=GMHG-11L&hinting=true (Denmark census)
https://www.familysearch.org/en/search/linker?ark=%2Fark%3A%2F61903%2F1%3A1%3AQL6P-RMJV&id=GD1H-11L&hinting=true (Denmark census)
https://www.familysearch.org/en/search/linker?ark=%2Fark%3A%2F61903%2F1%3A1%3AQK4L-Y42R&id=PMCN-11L&hinting=true (US GenealogyBank, Tennessee)
If I select Alabama, I get https://www.familysearch.org/en/campaign/hints-global?location=33 as I have for weeks, but it shows me three records from Italy:https://www.familysearch.org/en/search/linker?ark=%2Fark%3A%2F61903%2F1%3A1%3AXRYW-9PN&id=GT7X-F14&hinting=true
https://www.familysearch.org/en/search/linker?ark=%2Fark%3A%2F61903%2F1%3A1%3A6BH7-WB51&id=GH9Z-Q14&hinting=true
https://www.familysearch.org/en/search/linker?ark=%2Fark%3A%2F61903%2F1%3A1%3AXQW3-7RGV&id=PMS4-T14&hinting=true
South Carolina, at https://www.familysearch.org/en/campaign/hints-global?location=25 , is giving "Poland, Church Books". I'll just screenshot that.
I don't know if this is newer collections getting mis-tagged and popping up where they shouldn't - sometimes I do still get correctly placed records - or if the page is now making the wrong database call. Hopefully the DBAs and such can sort that out.
2 -
So the hints go to this place site? I wanted United States, Oregon and I get all British and so far none for the State of Oregon where I have hundreds of 6-8 generation relatives (I'm 6th generation since 1845)
0 -
@W D Samuelsen contact me please
This is a reminder that the Community has a Code of Conduct. Among the unacceptable behaviors is " using aggressive formatting techniques, such as ALL Caps…"
Your post was edited to bring it into compliance with the Code of Conduct.
Thank you for understanding and following the Code of Conduct in your future posts.
This particular issue has been sent up through the proper channels so that it can be looked at. FamilySearch is well aware of the issues with place names at the moment. Many examples have been submitted to help our engineers locate and fix these issues. We ask for your patience.
0 -
You managed to weaken the emphasis literally, showing the problem traced to this one called Global Places where the info based on the first place, mixing up with different places that are wrong. I was among early who reported Find a Grave problem few months ago. Few months later, we are getting screwed up hints with census and vital records.
Everything was fine until the findagrave problem showed up earlier this year and now those other places.
You should see the complaints against FamilySearch Tree in Facebook groups and email groups. Some are downright nasty.
Today I was at the FSL and the specialist in Czech language was surprised to discover Latin is STILL not included for the names. I asked about this one at last Rootstech and the tech staff were there and they said it needs to be added. Still not added. Should I raise the issue more loudly than last time few months ago? Latin is used widespread in European, Canada, USA and Latin American countries (including Brazil), particularly the Catholic Church.
0 -
@Michael J. Allen @W D Samuelsen contact me please @pauli133 @GFre
Thank you, everyone, for sharing examples and additional details. The screenshots and the specific stated examples are especially helpful in demonstrating that this issue affects multiple locations and record collections. Based on the reports in this discussion, it appears that some place selections are being associated with incorrect locations. The issue has already been escalated, and the examples being provided by community members are helping the engineering team investigate and identify patterns. If you would please use the feedback button in the global hints campaign. The feedback information you provide will go directly to the engineers. With everyone providing feedback on this issue, it will draw additional attention to it. We appreciate your patience while this is being reviewed. If anyone encounters additional examples, particularly those that consistently reproduce the issue, please continue to share them here, as that information can be valuable to the investigation. This will also be reviewed by the engineers on the Get Involved Team.
0 -
Figured out the issue.
I noticed the pattern last Saturday.
If the location is only one in existence - no problem.
If two or more have same name such as towns named Alabama, Poland, etc, cemetery like Mount Hope. the default kept going to the first one that have the name.
Such issue did not exist before last February. At the time we thought it was a Find A Grave issue. Now it isn't their issue, it is the FamilySearch issue.
We know who the culprit(s) is.
About that Feedback, I used it often to report Catalog problems (too many with missing information that we know were there before the upgrade. They have not been fixed as of last Friday, particularly Germany, Poland, and several places.
0 -
@W D Samuelsen contact me please
The problem of FS using the first location on its list in dealing with Find a Grave, in particular for cemeteries, has been reported to FS via the Records Issues form (which, not Feedback, is, we are told, the appropriate one for this purpose - see https://community.familysearch.org/en/categories/search). I think it was reported in this way by several people; here is a copy of my Records Issues report, submitted back in early July:
It is very clear from the various discussions of this matter here on Community that Find a Grave themselves were not at fault. But I do not think we have seen Records Issues reports mentioned for such an issue with Censuses.
@dancingintherain can you advise whether the engineers are looking at this in relation to Censuses also, or just Find a Grave?
And @W D Samuelsen contact me please I do think it would be helpful if you were able to provide a non-Find a Grave Historical Record URL demonstrating the problem, if possible, please.
1 -
I will check into this and discuss with the engineers we meet with on our team. Thanks for all you do!
1 -
I reported this issue directly to the engineers on the Get Involved Team.
0 -
Our team meetings have reported that the issues with the census records and Find A Grave are known, and Engineers are still working to fix them.
1 -
Update on the Global Record Hints page where US states were pulling up random European countries. Turns out it was a bug affecting the whole site and is being worked on right now!
0 -
Just following up: it looks like both Alabama and South Carolina are returning proper results again. Hopefully that can be generalized to the other affected areas.
0 -
It's been working again for the Australia/New Zealand region, and the Pacific Islands. (At least, it was until a few minutes ago, when the whole FamilyTree website stopped working. I presume that this is because of the maintenance that was scheduled and notified by a banner. "Please try again later", as they say.)
0
