Standardized Event Place When a Closer Standard is Made and Found
LegacyUser
✭✭✭✭
Jordi Kloosterboer said: There is a cemetery with a place name "Begraafplaats Heidehof, Ugchelen, Apeldoorn, Gelderland, Netherlands" (That's with the country name in English) that I got the FamilySearch Places team to add to the standard places. However, before this standard was added, Ugchelen, Apeldoorn, Gelderland, Netherlands was the closest standard, so that is the standard I chose back in June this year.
Now that the cemetery standard has been added correctly, the previous closest standard (Ugchelen, Apeldoorn, Gelderland, Netherlands) is still the standardized place name even though it is not even on the list to choose from and there is an exact match with another standard.
Maybe you could add a clause to the programming that if there is an *Exact* match of the event place and the standard place, that you change the standard to that exact match (if the previous standard was not an exact match) and run it once a month? I don't know how much of a strain that would be for the system, though. And this only helps correct standard places with exact matches that didn't have exact matches before. (So this wouldn't help a situation where there is a closer match but not exact.) So maybe this is a feature for far in the future?
Or maybe you could make standardized Event Place hints where if the system finds a closer match (or exact match), that it puts a hint for that person. Although maybe not the same type of hint as record hints as this is more of a data hint....
What are other people's thoughts about this? Maybe y'all don't even care about the standard that is chosen; I'm OCD about that stuff.
Now that the cemetery standard has been added correctly, the previous closest standard (Ugchelen, Apeldoorn, Gelderland, Netherlands) is still the standardized place name even though it is not even on the list to choose from and there is an exact match with another standard.
Maybe you could add a clause to the programming that if there is an *Exact* match of the event place and the standard place, that you change the standard to that exact match (if the previous standard was not an exact match) and run it once a month? I don't know how much of a strain that would be for the system, though. And this only helps correct standard places with exact matches that didn't have exact matches before. (So this wouldn't help a situation where there is a closer match but not exact.) So maybe this is a feature for far in the future?
Or maybe you could make standardized Event Place hints where if the system finds a closer match (or exact match), that it puts a hint for that person. Although maybe not the same type of hint as record hints as this is more of a data hint....
What are other people's thoughts about this? Maybe y'all don't even care about the standard that is chosen; I'm OCD about that stuff.
Tagged:
0
This discussion has been closed.