Places
A similar problem exists with standardized forms of dates of death. During war times it was not impossible that the places where persons died are unknown, for instance "Rußland" (Russia), "Ostfront" (in the eastern theatre of war) or "Unbekannt" (unknown). Also, the exact date of death might be not known, for instance "August 1944" or there is not even an evidence of death. Then it must be entered: "Vermißt" (killed in action and missing). All these options are highly realistic but not envisaged in FamilySearch. This has to be changed.
Comments
-
FiedlerKarl-Gerhard
.
Something to consider ...
.
I often, 'Write'/Enter, such like, the following on, BOTH, 'Dates'; and, 'Place' ...
.
Killed in Action, Body Never Recovered, ...
Killed in Action, Lost at Sea, ...
Went Down with the Ship, Exact Location Unknown, ...
Drowned, Lost Overboard, ...
Lost in the Air, Exact Location Unknown ...
[ sometimes ... over the, Pacific Ocean/Timor Sea/Baltic Sea/Off the Coast of South Africa/Off the Cape Horn (wherever) ]
.
The EXACT "Location" may be "Unknown"; but, the County/Continent/Sea/Ocean/whatever, is generally "Known" (or, "Believed"); and, as such, CAN be used a "Standard".
.
Were you aware ...
.
'Dates' CAN be easily "Standardised" with, BOTH, such "Text" as a "Prefix"; and, a Month/Year; or, just Year; or, About Year, as a 'Date'.
.
'Places' CAN just as easily be "Standardised" with, BOTH, such "Text" as a "Prefix"; and, a County/Continent/Sea/Ocean/whatever, as a 'Place'.
.
'FamilySearch' HAS envisaged such highly realistic "Options"; as, BOTH, 'Dates' and 'Places'.
.
Especially for 'Places' ...
.
Take a look at the "Research/Places" Database in 'FamilySearch' ...
https://www.familysearch.org/research/places/
.
"Standardised" 'Places'
.
Some; but, NOT limited to ...
.
Europe
.
Africa
.
At Sea
.
In fact ...
.
The "Research/Places" Database in 'FamilySearch' is a CONTINUAL 'Work in Progress' ...
https://www.familysearch.org/research/places/
Ever Changing, Ever being Added to; Ever being Amended; Ever being Corrected; Ever being 'Tweaked' ...
.
ANY User/Patrons can make REQUESTS for Additions/Amendments/Correction/'Tweaking' to/of "Standard" 'Places'.
.
NOT too much has to change.
.
One just has to learn HOW to USE what has been made available ...
.
That takes 'Time' and practice ... I was never shown, I just learnt through trial and error.
.
Just my thoughts.
.
Brett
.
0 -
FiedlerKarl-Gerhard
.
Something to consider ...
.
I often, 'Write'/Enter, such like, the following on, BOTH, 'Dates'; and, 'Place' ...
.
Killed in Action, Body Never Recovered, ...
Killed in Action, Lost at Sea, ...
Went Down with the Ship, Exact Location Unknown, ...
Drowned, Lost Overboard, ...
Lost in the Air, Exact Location Unknown ...
[ sometimes ... over the, Pacific Ocean/Timor Sea/Baltic Sea/Off the Coast of South Africa/Off the Cape Horn (wherever) ]
.
The EXACT "Location" may be "Unknown"; but, the County/Continent/Sea/Ocean/whatever, is generally "Known" (or, "Believed"); and, as such, CAN be used a "Standard".
.
Were you aware ...
.
'Dates' CAN be easily "Standardised" with, BOTH, such "Text" as a "Prefix"; and, a Month/Year; or, just Year; or, About Year, as a 'Date'.
.
'Places' CAN just as easily be "Standardised" with, BOTH, such "Text" as a "Prefix"; and, a County/Continent/Sea/Ocean/whatever, as a 'Place'.
.
'FamilySearch' HAS envisaged such highly realistic "Options"; as, BOTH, 'Dates' and 'Places'.
.
Especially for 'Places' ...
.
Take a look at the "Research/Places" Database in 'FamilySearch' ...
https://www.familysearch.org/research/places/
.
"Standardised" 'Places'
.
Some; but, NOT limited to ...
.
Europe
.
Africa
.
At Sea
.
In fact ...
.
The "Research/Places" Database in 'FamilySearch' is a CONTINUAL 'Work in Progress' ...
https://www.familysearch.org/research/places/
Ever Changing, Ever being Added to; Ever being Amended; Ever being Corrected; Ever being 'Tweaked' ...
.
ANY User/Patrons can make REQUESTS for Additions/Amendments/Correction/'Tweaking' to/of "Standard" 'Places'.
.
NOT too much has to change.
.
One just has to learn HOW to USE what has been made available ...
.
That takes 'Time' and practice ... I was never shown, I just learnt through trial and error.
.
Just my thoughts.
.
Brett
.
0 -
FiedlerKarl-Gerhard
.
And, some additional "Standardised" 'Places'
.
Eastern Europe
.
Pacific Ocean
.
Atlantic Ocean
.
Baltic Sea
.
Indian Ocean
.
Timor Sea
.
Bass Strait ... in fact x2
.
▬ At Sea
.
▬ Indian Ocean
.
Brett
.
0 -
FiedlerKarl-Gerhard
.
And, some additional "Standardised" 'Places'
.
Eastern Europe
.
Pacific Ocean
.
Atlantic Ocean
.
Baltic Sea
.
Indian Ocean
.
Timor Sea
.
Bass Strait ... in fact x2
.
▬ At Sea
.
▬ Indian Ocean
.
Brett
.
0 -
FamilySearch Family Tree actually has extreme flexibility for how dates and places are entered, as Brett explains.
Do not be deceived by people who do not understand what FamilySearch means by “standardize.”
In FamilySearch, “standardizing” dates and place names does not mean “enter all dates and place names in one and only one way, either exactly as an ‘authority’ proclaimed as the only acceptable way in a manual fifty years ago or as required to exactly match the drop down menu suggestions.” In reality, to standardize a date or place name in Family Tree means to enter the date or place name in whatever manner works best for the situation you find yourself which will give the best accuracy and best clarity for other researchers then link it to the closest possible description as is currently in the standards database.
To take your examples, dates are pretty easy.
If there is no known death date, just leave the death date blank. If there is a known range for the death, enter that range. If there is just the month and year, enter that. If just the year is known, just enter that. Here is how these will appear when you enter them in Family Tree:
Place names can be much more complicated. The simplest entry is when the place is unknown. Just leave the death place blank. That means unknown.
Here is how I would enter the other examples you give and how they would be correctly standardized:
These are all properly and correctly standardized and the program is able to handle all of them without the least difficulty.
0 -
FamilySearch Family Tree actually has extreme flexibility for how dates and places are entered, as Brett explains.
Do not be deceived by people who do not understand what FamilySearch means by “standardize.”
In FamilySearch, “standardizing” dates and place names does not mean “enter all dates and place names in one and only one way, either exactly as an ‘authority’ proclaimed as the only acceptable way in a manual fifty years ago or as required to exactly match the drop down menu suggestions.” In reality, to standardize a date or place name in Family Tree means to enter the date or place name in whatever manner works best for the situation you find yourself which will give the best accuracy and best clarity for other researchers then link it to the closest possible description as is currently in the standards database.
To take your examples, dates are pretty easy.
If there is no known death date, just leave the death date blank. If there is a known range for the death, enter that range. If there is just the month and year, enter that. If just the year is known, just enter that. Here is how these will appear when you enter them in Family Tree:
Place names can be much more complicated. The simplest entry is when the place is unknown. Just leave the death place blank. That means unknown.
Here is how I would enter the other examples you give and how they would be correctly standardized:
These are all properly and correctly standardized and the program is able to handle all of them without the least difficulty.
0
