STYLES AND STANDARDS
Policies for profile fields should always put genealogy first.
I do not mean We should change the location field names to modern location names
I have been doing Genealogy for over 50 years. I have been to the archives in London, Edinburgh, Den Haag, and Oslo. I do know that Genealogy consists of more than names and dates, I do not need to be convinced of the part history etc plays in genealogy.
I am trying to discuss the present wording of the policy and any other suggestions that outside of that wording that could be used in addition, to the policy.
I am also saying that I feel that those that have more interest than the average genealogist, dictate or least try very hard, the rules and policies used for profile fields, to suit their purpose. I do not mean that in a negative way, just that it shouldn't be that way. I suspect it is because they are more engaged that the average on the issues they burn for..
GENEALOGY IS NOT FIRST
WIKITREE the primary purpose is too grow a well sourced single family tree. Historical locations and correct titles etc should then be secondary when defining policy for profile fields.
For historical place names
The correct location name for a particular era is an interest in historical accuracy, which is a policy of Wikitree.
So in my opinion, policy promoted by those interested in historical places, has won over the average genealogist.
In my opinion WIkitree needs to use categories or something else , instead of letting any group, monopolize ANY field by policies to promote interests.
Proof that genealogy does not come first
*if I had 1000 genealogists in a room and asked where Lenapehoking is--how many would know?. The use then of this name in genealogy tells most of us nothing
*if you did know where it is, or take time to look it up. It still only locates your ancestor in an area that covers 3 states instead of one.
As I genealogist I want to know which state it was today. As I genealogist I have used time, I could have used looking for sources, instead of trying to figure out where it is. I still don't even know which state, so was of no help and time wasted.
*I want to search for all of one surname on WIKITREE for genealogy purposes, to possibly find other relatives, in a state my ancestors lived. If I search for them in New York, Delaware, New Jersey or Pennsylvania, those that have Lenapehoking as the place name, will not show up. Again not best solution for genealogy purposes.
*Genealogists that do not use the correct historic name can do so, BUT
**someone may change it
**it will show up on error lists which is irritating for most genealogists and WIKITREE members
**Time is used to change the present name to the historical one, by different help groups. That is time that could be used on improving sources and profiles.
I don't like to complain without at least offering a possible solution. I do believe these interests are important and improve WIKITREE.
Use Categories for historical locations
[[Category:dates, what ever was historical name, State]]
Possibly it could be automated and come up as a suggestion when place doesn't exist for that time period and category be added by choice.
For those that are interested or need the place name for research --It does not need to be in the place field
Location groups have some good tools. They are a good alternative to using the place name field and those interested just need to save the link