On the 1900 US census the three male members of the household of Sarah E Keeler are all listed as th
Answers
-
@Clay I Petersen Jr This is a known problem with the 1900 census. See this thread, among others: https://community.familysearch.org/en/discussion/111793/a-gremlin-in-the-1900-us-census-kearny-new-jersey#latest
@N Tychonievich another one for you please and thanks.
0 -
It would be nice to see some official FamilySearch response as to what process is causing corruption of post-publication indexes. It just leaves it open for public speculation as to whether this is FamilySearch/record custodian AI or other database processes run amok, or some third party maliciousness (the source of the problem needs correcting). Perhaps it's just sunspots/solar flares ...
I see no official statement:
0 -
@genthusiast @N Tychonievich said there had been many reports. See the thread I referenced above.
AFAIK it is a very recent issue - within the last couple of weeks - as I had no problem attaching these same records in November.
1 -
I agree - this index corruption issue is fairly recent although I recall one where the HOH was duplicating from about a month ago. What exactly is the 'known' problem? My concern is with identifying the cause of this corruption (as I hope FamilySearch can track it down and prevent further damage). But since it has been going on for a while and continues ...
Let's just hope this doesn't continue spreading further...
It seems like if it were Familysearch changes - there would be public notice of maintenance on the index (but yes even public 'maintenance' notices are not generally specific - thus my suggested idea for public notification similar to Search> Images). So with all the platform issues going on these days it just leaves it open for Community speculation. It just seems like if there are specific issues 'known' to be problems that are being reported - that Familysearch would have a 'known' response indicating what is 'known' - otherwise it's not 'known' to Community.
0 -
I'm sure the developers are working on the issue. And, I know that they more specific reports they receive, the easier it will be for them to pinpoint the cause. That's why I've been commenting on any threads I see and cross-referencing to other threads. With the Christmas season, repair may take longer than it might normally due to staff vacations.
1 -
Ok, specifically - what is causing the HOH to overwrite the post-publication index of other family members that indexers worked so hard on and is now being overwritten? Obviously a post-publication index problem ... Who has that access? Is this a hacking from a third-party - or some other process - meant to be an improvement - but which isn't? Transparency...
0 -
Thanks to all of you for your input. My only consolation is that it is not a problem that I caused. MERRY CHRISTMAS
1 -
One other thing I know - you aren't expecting me to answer that.
0 -
As we heard in recent threads, a large percentage of the mods in this group are unpaid volunteers - not employees of the LDS Church or FamilySearch. Some are not even members of the LDS Church.
A definitive answer on any topic would likely have to come from several levels higher up. And it IS Christmas week.
1 -
Note; several comments in this thread have disappeared making it look as if I am talking to myself. Not so as I was responding to specific questions/comments.
1 -
@Clay I Petersen Jr Have a great holiday. The wonderful thing about genealogy research - there is NO deadline and we are never finished.
0 -
I am having this same problem. Several months ago, I attached the 1900 Census separately as a source to a husband and wife (William and Caroline Thomas). When I just checked the source for the wife (Caroline Thomas), it said the record had been removed. When I looked closer at the indexing, Line 87 (for William) and what was formerly Line 88 (for Caroline) have been combined into the same Line 87, so both are reading as William. When I edited the second line to Caroline, it ended up changing both lines to Caroline. I have now changed it back to William, so they are both reading William again.
https://www.familysearch.org/ark:/61903/1:1:M9VX-FNL?cid=fs_copy
0 -
This is the first time I have wanted to report an issue that I have found. My first thought is: most people just assume others have reported it. I have learned in other situations that that no one has reported it. My second thought is making sure the right person is contacted. In reading the comments on this post is that there is no indication that that has been done. With all the volunteers that have put in so much of their time, I would hope this is not the case. I hope this can be resolved soon. Thanks for the initial post.
0 -
@SharonBurton61 Please view the thread I referenced where a Mod HAS indicated that reports are being made to the appropriate person. Not tagging her this time since it is Christmas Day.
0 -
@SharonBurton61, @SteveLinke, @Clay I Petersen Jr, @genthusiast
Thank you for the reports of the problems with the 1900 US Census. The issues have been reported to the engineers. We do not need additional reports as they now have ample examples to use when they get back from Christmas break and start trying to track down and resolve the problem.
A work-around you can try while you wait is to pull up the census image and add it to your source box. From there you can attach the census image as a source to each family member. To add the image to your source box, look in the top-right of the image viewer and click Source Box. Here are instructions for how to attach from Source Box.
From my source box, how do I attach a source to a person in Family Tree? • FamilySearch
From your source box, you can find a person in Family Tree and attach a source to him or her.
Sorry for the mess!
2