On census records, when "Same House" is listed, have it automatically populate the current residence
Hello,
I've noticed often when attaching census records that when the family has lived in the same home it populates, "Same House" but one has to manually change it to the actual standardized location in order for it to show up on maps or just be correct in the first place. Is there a way to program on the backend that when this occurs, it doesn't have it automatically populate same house when adding an event but the actual standardized location? For example, when the Residence date of 1940 says something such as, "Virginia, United States" can it be programmed for 1935 Residence automatically say, "Virginia, United States"? I'm requesting this for both the web version and mobile app version. Note that on the mobile app version, there is not an option to edit this while attaching the record, so one has to attach with "Same House" then go back to the profile and change it after the source was attached.
Please see the attached screenshots that provide examples of how the website currently auto populates this data and what would be a nice change to actually have it fill in this information automatically so one doesn't have to change it themselves. And to be frank, the majority of users just add the Residence as "Same House" and never change it. This matters to be as, it makes information easier to be correct and correct information leads to making it easier to find records. Also, it makes it possible to have standardized locations appear on maps of one's family history.
Comments
-
That is a great idea!
1 -
Thanks, Debbiekvj! I hope someone sees this and is able to do it. Based on what I've done for work, I'm pretty sure this can be done. How easy or difficult it will be depends on how the application is structured and how it pulls information in from the database along with how it is organized. Well that's just me thinking from my experience. Fingers crossed!
0 -
Great idea. I also hope it gets implemented.
0 -
It'd be nice if someone could programmatically fix all of these that are already attached to person records throughout the tree. It's pretty useless on its own to see 1935 "same house" with a warning that it's a non-standard place.
0