Capital letters in location fields [closed]

Question

It maybe that I'm being over fussy but I have seen a number of profiles recently where the first letters of place names in the location fields, don't have capitals. It looks wrong and as an ex primary school teacher, I want to correct them. I also don't want to cause hurt feelings.

Is this something that it would be feasible or desirable for the data error base project to include?

(or are there far more important 'errors' to look for and I am being far too old fashioned and fussy ?)

I do wonder if it has something to do with the increase in the use of 'phones and tablets for entering profiles.

Comments

I am often too lazy to type location names with proper capitalization

Answer 1

Hi Helen, thank you for posting this on our g2g forum. It seems to be a very common error that is made, as I see it constantly myself. As a data doctor I know that this error is listed on their project page here:

https://www.wikitree.com/wiki/Project:Data_Doctors

Location errors are split into 3 groups as follows: 601-630 Birth location, 631-660 Death location, 661-690 Marriage location.

For example:

• 611, 641, 671 Location in lowercase.

So we do have data doctors constantly working on those as well as other errors noted by the project.

PS: If you do see these errors on profiles in your watch list or on a profile you're interested in, there is no problem  to go ahead and correct the lower case spelling of a location. 

Comments

A very common error I see on G2G posts: "your interested in" instead of "you're interested in".  Oh, Dorothy. ;o)

---

Corrected lol!! Its only 5:51 am here, haven't had my coffee yet.

---

Thank you Susie M. for Best Answer!!

---

Thank you, I hadn't realised it was already an error. It's somehow less personal when you can quote it as an error.

---

I think it is a bad habit resulting from text messaging.

Answer 2

Oh my, I absolutely feel your pain. Capitalization seems to be hit or miss with many people lately. I see many names using lower case as well. I would simply correct them and do. This isn't something major that you might want to discuss with the PM prior to fixing. You aren't changing the information.

Yes, I vote for including it in database errors if possible.