Member Edits to Records That Do Not Allow Edits
I've encountered records in the database, "Rhode Island Town Births Index, 1639 - 1932" that do not allow edits. The reason given is that they were indexed outside of the Family Search system by another party.
The indexed birth years provided are in the 2000's, which is obviously far beyond the database end point of 1932 & naturally in the majority if not all instances, is well beyond the range of the mothers' childbearing years & her lifetime.
I suggest that for this database & others that are similarly restricted from being able to be directly edited within the body of the transcript that Family Search devise an auxiliary/alternate edit field next to the boxed in transcript that will allow researchers to enter an edit correcting the incorrect information in the transcript while leaving the incorrectly indexed information intact.
Comments
-
The edit every field indexing solution is rolling out. Who knows if/when it will reach this collection? If/when it does the record will be editable - but as of my last checking it does not necessarily keep the original index and then record the edit(s) - it only displays the last edit (making editing of the index even more important).
If the original index is substantially wrong it allows deletion of the original index (something I might not necessarily be too keen on if the original is better than the subsequent edit/index). Ancestry.com index edit feature does allow alternates (keeping the original) - whereas what I have seen from the FamilySearch edit every field solution does not (from my recollection). You either edit the original - changing certain fields permanently (of course you can go back in and edit again but then those changed fields are the current/only displayed) with no record of the original (at least this is my recollection of this newer feature) - or you delete the original index and replace it entirely.
The new edit every field solution does allow for creation of a near - if not complete - transcription of the record - whereas the current indexing solution never has had this capability. For transcription purposes there did appear to be an issue with overlapping highlights (the app lost one highlighted area entirely and it was unrecoverable - not able to re-highlight that area).
0
