Standardizing location on GEDCOM upload
I am not a CET-enabled user. But I like the feature a lot and will surely use it to clean up my exported data before pushing it to the shared tree. I expect to spend most of my time on standardizing locations. But I am pretty sure this could be automated to some extent during the import.
In Czechia, the same place belonged to different districts, and even the country name has changed throughout history. See this example of one village located on the borders of two districts:
https://www.familysearch.org/en/research/places/?focusedId=13696050&text=%C4%8Dlupek
In my records, I use current location names, without those district/country distinctions. However, in FS, I should use not only fully qualified names, but also the variant valid for the particular time range.
My idea is simple:
1. Normalizing my data to use the most recent fully qualified FS location
2. During the import, if a matching location is found and the particular event is fixed to a specific date (or year), pick the variant in the corresponding date range
3. Otherwise, keep the location non-standardized
Knowing the logic in advance would help me to prepare data to minimize future cleanup before CET becomes production-ready.
Thanks, Jan
Kommentare
-
@JanTosovsky Thank you for your interest in User Trees (formerly CET). As you know, it is still in early release. I have passed your suggestion to the engineering team.
0 -
@JanTosovsky as part of the User Tree creation process, place names are standardized automatically to the extent possible.
Thank you for bringing this to our attention. We’re committed to resolving as many issues as possible, and we’re closing this discussion for now. If you or others encounter this issue again, please start a new discussion and include relevant information such as your operating system, browser, URLs, and screenshots if available.
We appreciate your support and engagement. Please don’t hesitate to reach out with any future questions or concerns.
Thank you for using User Tree.
0
