RussellHltn wrote:I'd make the rules this way: If it's a clerical change, then don't move a verified marker. If the marker isn't verified, then it should be moved based on the new results of the geocoder as the original non-standard address may have confused it the first time around. (Of course, if the change isn't just clerical, then the marker should be processed just like a new move-in.)
I can endorse suggestions to enable the clerk, when changing an address in MLS, to expressly check a box to leave the maps location unchanged. But I think the default behavior should be to reset the geocoding when addresses change.
The current system does not save effort on the part of ward clerks, but can actually increase it, because among the users of maps.lds.org who are deceived by wrong "Verified" information online are the clerks themselves, at both the ward and stake level. No one can be confident that a "Verified" address is really verified. If someone is newly called as a ward clerk, and finds that his predecessor has "Verified" many or all addresses but some are obviously wrong, the only method he most likely would have to be sure is to reverify every address because he cannot rely on the "Verified" status he sees online. Stake clerks, emergency coordinators, quorum and auxiliary presidencies, etc. -- any users of the data -- are also potential victims when the reported status online lies to them. Is it really a good idea, when the flood hits, to show the widow Jones at a "Verified" location on high ground when her true address is in the flood plain?
As for level of work, typically there is more than one person within a ward with MLS privilege to change an address, and our clerk's office is barely controlled chaos on Sundays. The clerk or assistant who updates an address handed to him on a scrap of paper may be the one updating MLS. If a conscientious clerk absolutely wants to avoid introducing errors into the map when updating a moved family that is "Verified," he must:
- Login to maps.lds.org and unmap the family.
- Change the address in MLS.
- Wait a day or so for the change to propagate to the maps site.
- Login to maps.lds.org and manually map the family's marker.
Frankly, I doubt that happens very often, if ever.
By contrast, if the new address were just automatically regeocoded when it changed, it would most probably be plotted at a location very close to its true lat/lon, and classified as "Unverified," just like any move-in. Then, filtering by "Unverified" status online, ward clerks can prioritize these addresses for verification because that status would be trustworthy.
If the concern really is to reduce the redundant work occasioned by address standardization by clerks, the right place to attack that problem is at its source. The best way to mitigate this inefficiency is to standardize and validate new move-in addresses before they are even sent down to local MLS systems. (This could have the additional substantive benefit of trapping invalid addresses from even being disseminated to wards in the first place. Right now our ward roster is burdened with more than a dozen invalid addresses sent to us, mostly missing apartment numbers, for less active families. They never should have gotten past Address Unknown because the true addresses are actually not known)
But meanwhile, developers should just get the current tool as it exists functioning according to the overriding principle that getting the data right online is paramount, and users should be informed reliably if it is ambiguous. This principle trumps any concerns about efficiency.