Incorrect location information, missing indexes, missing batch numbers, core competence of FamilySea

LegacyUser

Volker Wilmsen said: via Google Translate

Dear FamilySearch users and programmers,

I really don't know any more where and which forum I can turn to. So far I have not received any helpful answers to my questions. I put these questions and hints in different places. Here are the relevant links:

1) https://www.familysearch.org/help/myc...
2) https://getsatisfaction.com/familysea...
3) https://community.familysearch.org/s/...

I am really at a loss as no one seems interested in solving this massive problem.

For the sake of simplicity, I would like to start over at this point with a first problem.

If you click on a magnifying glass symbol in the catalog for Albachten (https://www.familysearch.org/search/c...), you will get entries of births and weddings for Albachten.
In the case of births, the place of occurrence is "Albachten, Münster, Westphalia, Prussia, Germany". That is absolutely correct.
If the entries are restricted to weddings, "Albaxen, Höxter, Westphalia, Prussia, Germany" is given as the location. Albaxen does exist and sounds similar, but is located east of Paderborn and is unfortunately completely wrong.

What is the reason for this incorrect location information?

I would be happy to receive answers to this question.

And if answers to the missing indices could be found (see the links above), I would be even more happy.

Many thanks for your help.
I am very happy to answer any questions, test or discuss. Only your feedback is absolutely necessary for this.

LegacyUser

Juli said: It looks like the metadata on the marriage index is screwed up. I don't know who to contact at FamilySearch about such errors. The best suggestion I can come up with is to file a Support case, making sure to use the magic word "metadata", because otherwise you're sure to get nothing but boilerplate about index corrections.

LegacyUser

Jeff Wiseman said: Also, at the very bottom of many of the catalog pages there is an Errors? button. Selecting that will let you report the mistakes to the teams that support those records:

LegacyUser

Juli said: Except the error is not in the catalog. The catalog only has the correct placename; it's the index (and specifically just the _marriage_ index) that has the incorrect place.

LegacyUser

Tom Huber said: Ouch. I don't know if this is still the best place to report these kinds of problems, but it has been in the past. It is a problem in an existing index and as such, must be tackled by FamilySearch personnel to get resolved.

I have attempted to update the product (indexing) but that has not "taken", although the tag is what I entered.

LegacyUser

Tom Huber said: Okay -- the product is now showing, as well.

LegacyUser

Brian Rhees said: Thank you Volker for letting us know about this!

I agree with what has been said so far that it looks like the metadata on those records was not entered correctly. I've created a task for our data team to dig more into it and clean up those records.