Census Address field ‘Same Place’
Situation: When in source linker and attaching a census, you commonly have an address field that says ‘same place’ or ditto marks.
Problem: You then have to go back and type in the correct location. Fine for one, annoying for a family of 14.
Request: Have source linker identify ‘same place or ditto marks’ and auto fill the place with the location from the on year field. It could also highlight this so the user knows this is happening before it is attached it to the record so they can change it if they wish.
Answers
-
Isn't this a metadata problem not a Source Linker one? If the record is to be searchable it shouldn't be indexed as 'same place' or 'ditto'.
0 -
"Same place" comes from verbatim indexing of the 1940 US Census.
0 -
I don't honestly think the UI can be expected to cope with boundary conditions that result from bad indexing, I'd suggest the Feedback tab would be the way to go here.
0 -
But, it's not bad indexing.
Indexers type what they see; same place is on the form and what the enumerators were told to use.
3 -
Ah, ok, that makes sense, though I am surprised that's how this specific case works given that it is possible to search for any of the personas on the record. I guess the gap may be plugged at search time (admit I haven't tried). If it is, then the OP's suggestion sounds like the logical next step.
0 -
It is not bad indexing. The file has been indexed correctly.
I'm just saying that instead of having the person attaching the record take the extra step of correcting the location to be within the boundaries of the Standardized Place (the system already flagges the location as non standard)
Add a little code so that when the system flagges it as non standard it recognize that the reason is because of this one reoccurring specific instance found within census records.1 -
one approach to this problem is to "unclick" the box during the source linker process so that this information is not included in the Custom Events section for the individual's profile. Same with TAGS that can be "unclicked" especially with Census data. Just a thought.
2 -
If by having the system flag it you mean institute an automated routine, no, please, no. There are already WAY too many wrong things created by automated routines.
1 -
Not an automated routine.
Think of this flow option.
When you attach the Location Event from the census source. And if the address is 'same place', then at that moment the system gives you the option to click on keep 'same place' or use the other location that has been indexed from the record.
A hybrid approach.
0
