Automate unblocking temple work for valid surnames in Family Tree that are in the invalid words list
Surnames such as "Body" and "Baby" are quite common in Family Tree as legitimate names. The persons that are blocked from showing availability for Temple work span generations in both directions in the tree if they have a surname that is an invalid word with the error message, "This person's name contains one or more invalid words." No example is provided here as a quick search for a surname (Body or Baby) in the list using the Find feature returns too many examples of names with yellow icons and the error message to even page through. A search here in Community, alone, also returns enough examples of the issue to illustrate the scope of the potential for a more efficient process. And the number that are submitted on calls, chats, and emails is not even represented here.
The proposal in this "New Idea" is to automate the clearing of that error for persons who legitimately have surnames that are in the invalid words list. Maybe it's not new but it remains new in terms of being acted on.
This would only be recommended for relatively common surnames. Counting the occurrence of invalid words in surnames is an easy statistical analysis to do--even manually using the find feature in Family Tree--as is deciding from that analysis at what cardinality of occurrence of a surname in the invalid words list to draw the line for the best ROI based on the probability of finding multiple generations of that surname to check against. The main criterion would be to search for ancestral lines containing instances of a frequently occurring "invalid" surname that spans several generations in a line. There are other indicators of validity that can be cross-checked to confirm. Then anyone with that surname in the entire connected ancestral line could be released for Temple work.
A search for the exact surname "Body" returns 646 pages at 25 names per page--or more than 16,000 names. In the current inefficient process, each of those names will eventually have to be requested one to ten at a time on a call, email, chat, or question here in Community, documented for sending to another team by a missionary, and posted for review by the appropriate team who manually review it and manually release it to the requester. This is a time-consuming and tedious process--both for the guest as well as the multiple FS Support missionaries who touch it.
Obviously, prioritizing this value proposition between programmer resources and "free" volunteer missionary resources is really a decision for those who understand the opportunity cost of the current expenditure of "free" labor on this labor intensive process in terms of their truly higher value work that requires brainpower that programs can't supply and that needs to be done to hasten the work.