News on Database errors project (26 June 2016)

Question

Analysis was done on data from July 3rd 2016.

So in 7 days 12902 errors were corrected by my estimation. Great job. Have fun correcting errors.

You can also join the project here: http://www.wikitree.com/wiki/Project:Database_Errors

Detailed statistics are available on http://www.sdms.si:92/default.htm in Statistics section.

Comments

Noticed "probably" and "probable" in names and locations. What's you thought about catching those?

---

Probable appears only 49 times, but probably appears on over 2K profiles. So we should add that as location errors.

You can check frequencies of any.text on http://www.sdms.si:92/default.htm group search and item all wikitree

For name it appears only 13 times so i would check it only in location.

Answer 1

Excellent!!!

Answer 2

Re db_error_603  Is there a list or map of what you should change USA to in the pre-USA era?  I suppose Pennsylvania , USA can be changed to Pensylvania Colony, but what about Ohio?  Is it Pa or Va or what?

Comments

They slipped through again. Deleted.

Those errors are temporarily excluded, until Wikitree redefines Location fields.

---

It's a good question, though. I'm sure full of suggestions, but wiki says:

https://en.wikipedia.org/wiki/Province_of_Pennsylvania

So it appears that you could use:

<city>, <county>, Province of Pennsylvania, British American Colonies

Or

<city>, <county>, Pennsylvania Colony, British American Colonies

Or another variant along these lines.

---

We allready had this discussion here http://www.wikitree.com/g2g/249287/location-errors

Followed by this one from wikitree http://www.wikitree.com/g2g/252999/should-wikitree-use-familysearchs-place-names-database

And another one

http://www.wikitree.com/g2g/68640/how-to-name-places-in-pre-1776-usa0

---

animated history of united states and territories

---

Nice animated GIF
Url bigger version I added the link to error DBE_603 

An animated map like this makes me more convinced that we need to have more fields for historical locations

1. The name the location had when the event happened
2. The name today so we can draw maps
3. The exact GPS location so you can visit the place
4. Alternative names used when the event took place ex. the german name of a city the Polish....
5. The name in different alphabet like Cyrillic and Latin  

---

You have seen these maps of the states at the county level? You can move through them by year to see how they changed.

http://www.mapofus.org

---

Thanks Michael I added the link to error DBE_603 until we have a better solution.....

Answer 3

Thanks for magic work

Really like the new search interface and search Person Tree ==> you can see all related people and understand why people appear in the Error report. Would be nice to get a link on the WikiTreeID to WikiTree

 

URL http://www.sdms.si:92/default.htm

Video https://youtu.be/NFlVGIsB0hg

 

Big Picture
==> 892 profiles 10 generations Sälgö-1

Big Picture

==> 347 profiles 10 generations Sälgö-1 + Limit to blood relatives

Answer 4

Aleš Trtnik has given us a new magic tool to better understand the change rate in WikiTree and also analyse if we have more errors/quality in different time periods... with non open profiles....

You find the statistics on http://www.sdms.si:92/default.htm under Statistics

Example Error 107 Full name uppercase an error that you need to be profile manager to fix (LNAB) .... ==> its an error that is nearly impossible to fix with inactive WikiTree profile managers....

Big picture

My analyze is that open and public profiles has a higher change rate

Comments

True. For most easy errors opened profiles were fixed or will be in a month at current rate. The problem will remain with not opened profiles and i expect that those errors will be corrected at a wery slow rate since they involve communication with profile managers,...

It could be helped a little by wikitree if they automatically open all old profiles making them editable.

When we run out of public profiles to correct, we can create new errors.

---

I agree with you on Open Profiles. I don't understand why profiles can't just be automatically opened.

For that matter, I also wish that the cutoff could be raised from 200 years old

Answer 5

Added variations of Unknown

To errors 601, 631 and 661 I added also similar words to Unknown. It gives additional 2K errors.

Errors	Total	0000-0000	0001-1499	1500-1699	1700-1799	1800-1899	1900-1999
601 Unknown birth location	9764	1779	3	413	1436	4683	1450
631 Unknown death location	16665	1494	5	796	2653	9572	2145
661 Unknown marriage location	1428	75	4	21	252	823	253

Answer 6

Fantastic!

Answer 7

Added new errors Profile should be open (Child birth date)

This are similar to 109 and 110, but are identified for profiles with no birth and death date and their children were born more then 200 years ago.

Errors	Total	0000-0000
212 Profile should be open (Child birth date)	4716	4716
312 Profile should be open (Child birth date)	4452	4452

 

Answer 8

Added new error 111 Died too young to be parent

This error lists all profiles, that were under 10 years old and have children without birth date. If child has birth date set, error is already listed in other errors.

Errors	Total	0001-1499	1500-1699	1700-1799	1800-1899	1900-1999	2000-Now
111 Too young to be parent	514	44	67	68	195	133	7

 

Comments

I think you need to say they *died* too young (<10yo) to be a parent.  That looks like what the data is showing

---

Fixed. In error lists it will be visible on next update.

Answer 9

Added new error 112 Person is Father and mother

Here are profiles, that are father to some children and mother to some. This error must be corrected, otherwise there is a problem with siblings in children profiles. Some siblings are missing.

Errors	Total	0000-0000	0001-1499	1500-1699	1700-1799	1800-1899	1900-1999
112 Person is Father and mother	1431	169	16	67	354	709	116

Comments

You lost me again see video https://youtu.be/zW-XpvBt4Qk I dont understand the problem

Error reported on Webby-63 found on Err_20160626/112_1900-1999_0.htm

---

This error was corrected.

http://www.wikitree.com/index.php?title=Special:NetworkFeed&who=Webby-64

Child had Webby-63 as father and mother.