the "Edit" button says "Sorry, you need special authorization to edit this record"
Comments
-
How can I get the errors corrected for a record where the "Edit" button says "Sorry, you need special authorization to edit this record"?
For example, in this record: https://www.familysearch.org/ark:/61903/1:1:62FN-YVC2?lang=en the parents names are incorrect.
- "Kounandrlie Mitchell" should read "Norman Leslie Mitchell"
- "Alice Mande Mitchell" should read "Alice Maude Mitchell"
0 -
Since the images for this record are now restricted there would be no way for you to edit.
I'm curious about the message as I've never seen it pop up when trying to edit. Was the button grayed out?
1 -
@SerraNola The message shows on hover (over Edit) for me on that record.
I think I've seen it before, but I haven't captured it. Generally, when Edit is grayed out and no image is present, I just move on because I know I won't be able to edit.
1 -
Ah yes, I didn't think about "hover" messages!
2 -
if there is an error, I can't change it "forever"?
0 -
@Ann L Mussatto Newell If there is an error and I can fix it, I will.
@Robert2,182 I corrected Alice's middle name from Mande to Maude. When I tried to correct Norman's name I found that it was already correct in the index. It was edited by you in February of 2024, but the system is overriding it so it displays in record details with the AI created version:
Sorry, but this is out of my control and I can't say if there's a fix available.
2 -
Since @Robert2,182 made the correction in February of 2024 and the "system" overrode it in August and September 2024, does that mean that any edits/corrections made by a researcher can, at some later time, be overridden by the FamilySearch AI system? Or, does that only apply to Indexed Names?
1 -
I have a similar case.
My 5th great-grandparents married in colonial Maryland on 20 December 1753. The date was indexed as 25 Dec 1753, apparently from the next marriage in the Vestry Records.
The date has been edited, but the incorrect date still displays.
https://www.familysearch.org/ark:/61903/1:1:QG6L-DKH1?lang=en
2 -
@SerraNola surely this is a bug? AI should not be overriding manual input, or am I missing something?
1 -
If this had appeared to be a system bug, I would absolutely have created a work order. In fact, I pulled up the example of “Norman Leslie Mitchell” in an engineering meeting in April while I was reporting a bug in which user "deletions" were being overwritten by later creations. That issue was fixed. Since then, I’ve been watching for any similar reports of edits being reversed, and I haven’t seen any. I should have explained more clearly that when I said, “I can’t say if there’s a fix available,” what I meant was that it hasn't been determined whether this specific instance was a one‑time glitch in how the "create/update elements rolled up" (engineer's words—not mine).
Most reports of edits “reverting to the original” turn out not to be reversions at all, but cases where the edit didn’t save. I often see Feedback entries saying a correction couldn’t be made, but by the time I check, the edit has saved successfully.
Áine, in your example, there was no record of an edit from you in the change log. My best guess is that the standardized date format wasn’t selected before saving. When I tested it, the edit saved correctly. You can also see in the change log how the value in the day field (25) was pulled into the date when displayed in record details.
For the record, AI should never override manual input. If anyone in the community encounters a case where it appears that has happened, please report it right away so we can investigate promptly.
3 -
Thanks, @SerraNola, both for the fix and the explanation.
2
