Improve importation of Census Records
LegacyUser
✭✭✭✭
Adrian Clift said: Am working mainly in Tennessee, but also saw the issue in Texas. I have not worked that much in other states.
Assuming that your (our) objective is to include as much detail as practical and that you want to include uniform links for mapping purposes, there appears to be a fix that would be easy to implement.
In Tennessee, Census takers typically entered "3rd Civil District" or "District 3," for example. But since your uniform index format looks for "Civil District 3" in this example, you could improve the import process by universally inserting "Civil" if the census record includes "District" followed by a number. This would vastly improve the quality of data generated by user links to existing census records.
In Texas, the exact situation exists, except that the existing census field typically starts with "Precinct" but the index token is looking for "Justice Precinct."
Just a thought.
Assuming that your (our) objective is to include as much detail as practical and that you want to include uniform links for mapping purposes, there appears to be a fix that would be easy to implement.
In Tennessee, Census takers typically entered "3rd Civil District" or "District 3," for example. But since your uniform index format looks for "Civil District 3" in this example, you could improve the import process by universally inserting "Civil" if the census record includes "District" followed by a number. This would vastly improve the quality of data generated by user links to existing census records.
In Texas, the exact situation exists, except that the existing census field typically starts with "Precinct" but the index token is looking for "Justice Precinct."
Just a thought.
0