Invalid record hints
LegacyUser
✭✭✭✭
David Wynn said: 
Definitely an issue. Not sure why this particular record was removed, but if it was, it needs to be removed. If the record is no longer available, why is there still a hint to attach the record? Needs to be some error checking at several points along the line so that any missing records will not be listed as hints. Here's a few related to my own experience:
* If the record or set of records is removed from the system (seriously, the 1940 census?!?), then remove any associated record hints.
* As the profile is built for each viewing, double-check any record hints being provided. If the record is not available, delete the associated hint before presenting the profile to the end-user.
* Remember to update the mobile app also. This person is showing in my Ancestors With Tasks (Android version). Shouldn't be seeing any tasks for non-existent records.
Definitely an issue. Not sure why this particular record was removed, but if it was, it needs to be removed. If the record is no longer available, why is there still a hint to attach the record? Needs to be some error checking at several points along the line so that any missing records will not be listed as hints. Here's a few related to my own experience:
* If the record or set of records is removed from the system (seriously, the 1940 census?!?), then remove any associated record hints.
* As the profile is built for each viewing, double-check any record hints being provided. If the record is not available, delete the associated hint before presenting the profile to the end-user.
* Remember to update the mobile app also. This person is showing in my Ancestors With Tasks (Android version). Shouldn't be seeing any tasks for non-existent records.
Tagged:
0
Comments
-
Brett said: David
'Yes' ... definitely a problem/issue.
But ...
That said ...
I WISH "FamilySearch" was NOT even "Removing" (or, "Retiring") such "Sources" - the SAME problem/issue of the "1851 and 1881, Census' of England and Wales" all over AGAIN.
Brett
.0 -
Brian Jensen said: David,
Thanks for the report. I've duplicated the problem and I've reported it to the engineering team. I'll report back on what they find.
Thanks0