Disambiguation needed in Germany, Lutheran Baptisms, Marriages, and Burials, 1500-1971
In the collection Germany, Lutheran Baptisms, Marriages, and Burials, 1500-1971
the place name Backnang, Murr, Oa u. Sulzbach, , Backnang, Murr, Oa u Sulzbach, Württemberg, Deutschland is robo-standardized incorrectly to Sülzbach, Weinsberg, Württemberg, Deutschland. For disambiguation help see https://en.wikipedia.org/wiki/Sulzbach
@dontiknowyou Thank you. I'll get those to engineering.1
The following knowledge article in the FamilySearch help center addresses your question:
How do I correct or edit a place in FamilySearch Places?
Thank you for taking the time to improve our place information. We value your submission and will review it carefully.
- Begin at FamilySearch Places.
- In the search box, enter the place that interests you.
- Click the appropriate search result.
- On the right-hand side of the screen, below the map, click Improve This Place.
- To see the link for Improve This Place, make sure that you are signed in.
- A box appears with the title "Suggest an Improvement."
- Use the drop-down menu to identify what is incorrect or incomplete with the current entry.
- Enter a brief description of what needs to be changed or added.
- If possible, enter the URL of a website that can be used to validate the new information.
- Enter your email, in case more information is needed.
- Click Submit.
Elder Gary Kearl Family Tree Support0
@Gary Kearl2, how does a correction to the Places database have any effect on an existing autostandardization error?
@dontiknowyou, any chance of a specific index entry (URL)? Doing a search for your exact placename (https://www.familysearch.org/search/record/results?count=100&q.anyPlace=Backnang%2C%20Murr%2C%20Oa%20u.%20Sulzbach%2C%20%2C%20Backnang%2C%20Murr%2C%20Oa%20u%20Sulzbach%2C%20W%C3%BCrttemberg%2C%20Deutschland&q.anyPlace.exact=on&f.collectionId=3015626) revealed yet another instance of a nonstandard definition of "exact" -- the only two occurrences of the characters "Murr" on the search results page are in the search field -- but no examples of Backnang being turned into Sülzbach, and removing the repetition from the search term (https://www.familysearch.org/search/record/results?count=100&q.anyPlace=Backnang%2C%20Murr%2C%20Oa%20u%20Sulzbach%2C%20W%C3%BCrttemberg%2C%20Deutschland&q.anyPlace.exact=on&f.collectionId=3015626) gave 16 results without the usual autocorruption telltales (i.e., no parenthetical "Original" on any field).1
Now the images are not viewable, so perhaps a fix is in progress.1
Once your request to change a place name is accepted, the database of place names is update with the new spelling.0
@dontiknowyou As Julia suggested, please provide us with a URL showing the error in place within the Germany, Lutheran Baptisms, Marriages, and Burials record collection. We need to see the error and then we can report it up to engineering for correction. Thank you.1
@Gary Kearl2, yes, and ...? What relevance does a change in the Places database have to an index entry that has been associated with the wrong place by the autostandardization bot? They're not running the bot again (and again and again and...), are they?1
My purpose here is to help the engineers train the transcription robots. Again and again the bots make mistakes on place names needing disambiguation. I don't know what happens behind the scenes, but there seems not to be enough integration between the indexing engineering team and the gazetteer team / place names improvement volunteer project.
The FamilySearch Places gazetteer is far from complete, but there are other gazetteers and FamilySearch could peek at them. When resolving place names myself, I find it very helpful to check Wikipedia specifically for disambiguation pages.0