Permissions Issue on Suggested Sources for Whole Films
Yesterday I ran across a permissions issue that doesn't seem to be tied to a history of edits.
For example, the first suggested source for K6Q4-XR4, christened "Josepha Joaquina" on 22 March 1795. When I click on the suggestion, I get the message
We're unable to show this record.
This record can only be displayed on certain accounts. FamilySearch must honor the agreements we have with our partners, record owners, and internal policies.
I can browse to the relevant image in the old image viewer, it's image 403 of 527 on the film "Bautismos 1790-1796", DGS # 004241367, FHL film 645481. So this is a permissions issue on the source-record, not on the image.
I know I was able to access it about a week ago. But since yesterday I can't. I've tried in Edge on Widows 11, Chrome on Windows 7 and Chrome on Windows 10, three different devices.
And I haven't yet gone through the thousands of profiles that should be associated with that film, but all of the few I've checked so far have the same problem.
There's at least one other film for the same location that has a similar problem. It's FHL film 645491, DGS # 004010876 consisting of 610 images with just the IGI-derived index (not linked to particular images on the film), also available as DGS # 007830234 consisting of 609 images with index entries linked to particular images (an AI-generated index). In that case, the already-attached source from that film for LZ4N-GGN behaves as expected, but I saw the permissions error on a suggested source for some profile I was working on yesterday. Just choosing a profile at random, MDN4-FSL shows the error on the first suggested source.
Best Answer
-
I've only had time to look at your first example, but the others are likely the same problem. The permissions on this record hint are set so that anyone should be able to view it. The problem isn’t that you’re blocked; it’s that the hint is wired to a missing copy of the record. This film shows a wide discrepancy in persona count, meaning that most of the indexes are not connected correctly, cannot be opened, and are not searchable.
I do have a list of these that need to be fixed. It's interesting that you say it was accessible only a few weeks ago. I will make note of that in the report to engineers.
@MLE7 Please provide details as your case may not be the same problem.
1
Answers
-
@SerraNola Could you please take a look at this one? Thanks!
0 -
Having the same problem since March 26 on records from Sicily. No idea why it suddenly started happening.
0 -
Another profile with a suggestion that has this problem: MXFH-ZJ3 , source suggestion "Francisco Xabier Viques".
0
