Incorrect Registered Index in the Cook Island's Public Records.
Hey All,
Just needing to find out how do I go about getting an index corrected.
This index is meant to be a birth index but it is showing up as a marriage index.
"Cook Islands, Public Records, 1846-1989", database with images, FamilySearch (https://familysearch.org/ark:/61903/1:1:QLK4-SK3B : 6 December 2019), Are Tepaki, .
Do I need to report this somewhere else and if so can someone direct me please.
Thank you.
Best Answers
-
Is the event also showing as having taken place in the correct location? At present, it shows as " Cook Island, South Georgia and the South Sandwich Islands" - is that correct? If not, at least you can edit that part yourself.
With regards to the type of event (birth, not marriage) I believe this can only be changed by FamilySearch. I do not think you can go further than in reporting the matter here, and hope a moderator can add this to a very long list of such errors.
Whether "re-indexed" by a human or computer, there are many events that have been changed, so they now show erroneous information. I believe FamilySearch employees have acknowledged there needs to be a complete reassessment of the current process, which has led to a huge amount of such errors.
1 -
Right now, there are limits to what can be edited. There is a new program being rolled out that allows every field to be indexed/edited. They have not stated when it will be applied to various collections, so check back intermittently.
2
Answers
-
It is exactly as you said. It is not the place. It is the type of event it is.
Thank you for your reply. Guess I will wait and work on it at another time.
0 -
oh wow sorry for the late reply it looks like someone has refixed it. How do we redo the indexing. There is still data missing on the FamilySearch frontend.
0 -
@Miria Reu As mentioned by @Maile L editing is limited in the Cook Islands, Public Records collection. So, there is not currently a way to modify the event type. When you use the record as source, you can note the error in event type. Or, since the record image is available, you can click to open it and use it as your source, thus bypassing the flawed index. If you would like to do that and have never done it before, here are some Help Center articles that have instructions: https://www.familysearch.org/en/help/helpcenter/article/how-to-find-the-add-to-source-box-link, https://www.familysearch.org/en/help/helpcenter/article/how-do-i-attach-source-from-source-box, https://www.familysearch.org/en/help/helpcenter/article/from-my-source-box-how-do-i-attach-a-source-to-a-person-in-family-tree, and https://www.familysearch.org/en/help/helpcenter/article/how-do-i-create-a-source-in-family-tree
0 -
After examining these records in more detail, I feel the birth records have been classified correctly. It is just this one record that should probably not have been indexed at all. The original records are all for Births of his children and the "Marriage" record has been indexed to show the parent's relationship.
As in this example, the children have had their births indexed as such - the indexer was perhaps being "over-helpful" in adding the parents in a "Marriage event" - albeit, one without any place / date detail, as these are not shown on the pages in this collection:
In summary, were it to be possible, the only corrective action FamilySearch would need to take is to remove this "Marriage" record altogether. The correctly indexed births of the four children would still remain.
2 -
Sorry I am still learning how to use this. Do you see my picture? The event type is listed under marriage on Family Search at the bottom right yet the Image is a birth register.
0 -
From what I can tell, an over-helpful indexer indexed all of the births, then added marriages for all of the entries where the informant was identified as the father.
The index detail page for the indexed births makes no mention of marriage. (For example: https://www.familysearch.org/ark:/61903/1:1:QLK4-SK3J.) The erroneous "Marriage Date" and "Marriage Place" labels are only on the Image Index tab, probably because it can only show one label for each column, and whatever method it uses to choose -- maybe the last item on the list? -- it chose the one that's not correct.
1
