Project: Database Errors

Categories: Profile Improvement Project | Functional Projects | DBE Error


This project is intended to correct data in the WikiTree database. It is a subproject of Project: Profile Improvement.

This page is part of Database Errors Project.
Latest prepared error lists March 19th 2017: Space:Database_Errors_Project_2017-03-19
Custom errors, statistics,... on: WikiTree+

Contents

Mission

The goal of this project is to correct data errors in the WikiTree database.

Most such errors are the result of typos or imports of GEDCOMs. Also, beginners can make mistakes that are not easily found. Here you can locate errors and correct them.

How to Join

Leader: Aleš Trtnik

Project Coordinator: Magnus Sälgö.

Here you can see tag followers and badge holders.

If you have any questions please:

  • First read project documentation below.
  • If the question is about a specific error, read the page for that error. Links to documentation of errors are at the bottom of this page.
  • Search for related subjects in G2G forum - Tag db_errors.
  • Ask in the G2G forum and add the db_errors tag.

If you would like to be involved in the Database Errors Project please:

  • Add DB_ERRORS to your list of followed tags. That way you'll see all of our discussions in your G2G Feed.
  • data_doctor.gif To get the Data Doctor badge, answer in this thread in G2G and the badge will be awarded to you. By receiving this badge, you are allowed to send more than 20 private messages per day. But you must be aware of the warnings here: Daily limits on_messages - Exceptions to the limits. It's important that nobody posts/sends too many similar-looking messages.

Goals

We have only one goal: Correcting errors in data.

  • First check and correct errors on your own tree.
  • Second check and correct errors on your watchlist.
  • Then you might correct errors by type. Check out the Latest errors list to find error types you can correct. Read the help info on that error to familiarize yourself with specifics and then start correcting. If you are working on the complete list of an error in a specific era add a comment on Latest errors page so that others know a specific error is already being checked.
  • Or you can correct errors by location (your town, region, country ...).

See the Links section below for all you need to get started.

Code of conduct when fixing database errors

Please, as a courtesy, look at the profile and previous comments before leaving any comments or templates on a profile due to database errors. There is no point in leaving multiple db_error messages.

Please write a change comment in the Explain your changes: box for each change you make. Especially make sure to write one if there is a profile manager, so they know why the profile was changed.

  • With very easy obvious errors such as incorrect gender and gender missing there is no need to contact the profile manager for an Open profile. The change log shows exactly what happened.
  • Be clear and friendly when advising of errors; errors happen to everyone! Be careful to try to not make people feel like they're in the naughty corner.
  • Post a message in the public comments of a profile to say that you have contacted the profile manager so that no one else also contacts them. Public comments should be ok to be deleted once they are finished with (we should have a debate about this soon).
  • If you do make changes such as changing an unknown birth location to a place make sure a source is added to validate the change.
  • Make sure all correspondence has the url of the errors project so they can look at it. This also helps people see they're not being personally targeted.
  • If you see the same name coming up regularly or if the person is pretty well known on G2G drop them a more general "have you seen this..." type message and leave them to it for a little while.
  • Ensure if the above is the case the profile manager is aware that after getting a list of their errors off they can hide them for 30 days while they are working on them, so there would be no need to send messages or put a comment on for every profile.
  • If people come back to you for advice or further information help them in a timely manner or direct them to a person who can help.
  • If you’re working on a particular error from the error sheet, add a note on the Latest errors page so no one else will also look at the same list for a week.
  • If you put through a merge then you and the profile manager are responsible for taking the duplicate notes out, I usually give the profile manager a few weeks to do that, if they haven't, do it yourself.
  • Concerning the "profile should be open" error:
    • If you're the manager/on the trusted list, open the profile
    • If you aren't, leave a message on the profile.
    • If you have several profiles that need attention, send them as a list to Paul using the Open Profile Request rather than many individual requests. Use this only when the profiles have the same profile manager.

Links

  • You can get all errors for your watchlist. Just follow the https://apps.wikitree.com/apps/trtnik2/ex/ to wikitree apps server. There you have to login with wikitree credentials like for FS Connect, and you will get errors in your watchlist. This is in early development but you can try it. For huge watchlists it can take up to 1 minute to process, so be patient.
  • You can manually check spelling of any word of location on http://wikitree.sdms.si/default.htm in group Analyse item Location spelling. There you can also see misspelled profiles and correct them on Wikitree.

For older error lists see:

Templates

There is also a template {{db_errors}} to put on profile and have link to errors for that profile and connected ones. Check documentation for this template.

  • {{db_errors}} ==> Generates a link that generates a report of current Wikiprofile 5 generations. This form can be used only in biography, not in comments.
  • {{db_errors|10}} ==> Same as 1 but 10 generations. This form can be used only in biography, not in comments.
  • {{db_errors|10|Sälgö-2}} ==> Same as 2 but starts with Wikiprofile Sälgö-2. This form can be used in comments, freespace pages and everywhere else on WikiTree.
  • {{db_errors|Generations=10|WikiTreeID=Sälgö-3}} ==> This form can be used in comments, freespace pages and everywhere else on WikiTree.
  • {{db_errors|10|Sälgö-1|Y}} ==> Third parameter adds more help text. This form can be used in comments, freespace pages and everywhere else on WikiTree.

Frequently asked questions (FAQ)

How to correct errors on Pre-1500 profiles

Asked here

When you find an error on a Pre-1500 profile and the current profile manager does not have a Pre-1500 Badge, putting a note on the profile will not help. The profile manager cannot fix the issue and no one with a Pre-1500 badge will see your request. Here is what to do:

On G2G post a very clear message about what needs to be fixed, why, and the source of the information to back up the change. Make sure to add the TAG Pre-1500. You can also add db_Errors, so we know the origin of corrections. Those with Pre-1500 badges will work these items.

Also, Data Doctors without a Pre-1500 badge can leave the Pre-1500 errors to the Data Doctors who have the badge.

Description of errors

False errors

If you encounter an error that isn't an error, you can click a link on the right to tell the system that it is not an error. Error will disappear at latest on next recalculation (on monday).

Temporary hidden errors

If you encounter an error that you cannot fix, and you posted a message to profile manager or you proposed a merge, you can click a link on the right to tell the system to ignore this error for a month. If profile manager will correct the error, it will no longer exist, otherwise error will reappear after 31 days so other actions can be taken. Error will be hidden at latest on next recalculation (on Monday).

100 Person

  • 101 Birth in future: This one is obvious. We are not fortune tellers. Probably typo in birth date. It is checked on all profiles with date.
  • 102 Death in future: This one is obvious. We are not fortune tellers. Probably typo in death date. It is checked on all profiles with date.
  • 103 Death before birth: Death date is before birth date. Probably typo in birth date or death date. It is checked on all profiles with both dates. For now it is one year gap to handle dates without month and day.
  • 104 Too old: Person is too old. At the moment max age is 115 years and will be lowered as current errors are corrected. Probably typo in birth date or death date. It is checked on all profiles with both dates.
  • 105 Duplicate sibling: Here are profiles that have a sibling with same full name, birth and death date and both parents. They are probably duplicates and need to be merged. If they are not, you can mark error as False Error and you need to do it at both siblings. Similarity will be reduced as current errors are corrected.
  • 106 Duplicates between global tree and unconnected: Here are profiles that have same full name, birth and death date and are not connected in any tree. Orphan profiles are ignored. These are probably duplicates and need to be merged and with these action an unconnected tree is connected to global tree. There can be already connected profiles because my global tree is smaller due to connections in private profiles.
  • 107 Full name in UPPERCASE: Here are profiles that have whole full name in uppercase.
  • 108 Full name in lowercase: Here are profiles that have whole full name in lowercase.
  • 109 Profile should be open (birth date): Here are profiles that should be open, since birth date is older than 200 years or birth date is wrong.
  • 110 Profile should be open (death date): Here are profiles that should be open, since death date is older than 200 years or death date is wrong.
  • 111 Died too young to be parent: Here are profiles that were under 10 years old and have children without birth date.
  • 112 Person is father and mother: Here are profiles that are father to some children and mother to some.
  • 113 Duplicate in relatives:

200 Father

  • 201 Father is self: This person is its own parent. Parent should be deleted or replaced with correct one.
  • 202 Parents are same: This person's mother and father is the same person. One parent should be deleted or replaced with correct one.
  • 203 Father is Female: This means that left person is defined as father of the right person. There are two possible errors. Left person has wrong gender or right person has swapped parents father should be mother.
  • 204 Father has no Gender: This person's father doesn't have a gender. Set parent's gender.
  • 205 Father is too young or not born: This person's father was too young or not born to be the parent so probably one birth date is wrong. Limit is set at 10 years. Correct birth date.
  • 206 Father is too old: This person's father was too old to be the parent so probably one birth date is wrong. Limit is set at 99 years. Correct birth date.
  • 207 Father is also a child: This person's father is also his/her child. He cannot be both. One relation should be deleted or replaced with correct one.
  • 208 Father is also a spouse: This person's father is also her husband. This is rarely true. One relation should be deleted or replaced with correct one.
  • 209 Father is also a sibling: This person's father is also his/her sibling. If there is no 201 error problem is in mother's children. Mother's children should be corrected.
  • 210 Father was dead before birth: This person's father died before birth so probably birth date or father's death date is wrong. Correct wrong date.
  • 211 Duplicate sibling by Father: There is a profile with the same full name, birth and death date and same father. Mother is different. These two profiles are probably duplicates and need to be merged.
  • 212 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.

300 Mother

  • 301 Mother is self: This person is its own parent. Parent should be deleted or replaced with correct one.
  • 303 Mother is Male: This means that left person is defined as mother of the right person. There are two possible errors. Left person has wrong gender or right person has swapped parents]] father should be mother. Same goes for errors 303.
  • 304 Mother has no Gender: This person's mother doesn't have a gender. Set parent's gender.
  • 305 Mother is too young or not born: This person's mother was too young or not born to be the parent so probably one birth date is wrong. Limit is set at 10 years. Correct birth date.
  • 306 Mother is too old: This person's mother was too old to be the parent so probably one birth date is wrong. Limit is set at 99 years. Correct birth date.
  • 307 Mother is also a child: This person's mother is also his/her child. She cannot be both. One relation should be deleted or replaced with correct one.
  • 308 Mother is also a spouse: This person's mother is also his wife. This is rarely true. One relation should be deleted or replaced with correct one.
  • 309 Mother is also a sibling: This person's mother is also his/her sibling. If there is no 301 error problem is in father's children. Father's children should be corrected.
  • 310 Mother was dead before birth: This person's mother died before birth so probably birth date or mother's death date is wrong.
  • 311 Duplicate sibling by Mother: There is a profile with the same full name, birth and death date and same mother. Father is different. These two profiles are probably duplicates and need to be merged.
  • 312 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.

400 Marriage

500 Name / Gender

  • 501 Wrong male gender: Person with this name should be male, but is defined as female. So probably gender is wrong or name is incorrect. Correct gender or name.
  • 502 Missing male gender: Person has no gender defined and according to name should be male. Enter gender.
  • 503 Probably wrong male gender: Person with this name should statistically be male, but is defined as female. So probably gender is wrong or name is incorrect. Correct gender or name.
  • 504 Missing probably male gender: Person has no gender defined and according to name is probably male. Enter gender.
  • 505 Wrong female gender: Person with this name should be female, but is defined as male. So probably gender is wrong or name is incorrect. Correct gender or name.
  • 506 Missing female gender: Person has no gender defined and according to name should be female. Enter gender.
  • 507 Probably wrong female gender: Person with this name should statistically be female, but is defined as male. So probably gender is wrong or name is incorrect. Correct gender or name.
  • 508 Missing probably female gender: Person has no gender defined and according to name is probably female. Enter gender.
  • 509 Missing gender: Person has no gender defined cannot be derived from name. Enter gender.
  • 510 Unique name without gender: Person has no gender defined and has unique name and cannot be derived from name. Enter gender and possibly correct name.
  • 511 Unique name (spelling): These are names, that appear only once in database. They are possibly misspelled.

550 Wikidata

Some WikiTree profiles are matched with a profile in WikiData see Space:Wikidata.

570 FindAGrave

Some WikiTree profiles are referencing memorials on findagrave.com.

600 Location

Location errors are split into 3 groups as follows: 601-630 Birth location, 631-660 Death location, 661-690 Marriage location. Some errors can be defined by users Space:Database_Errors_Definition.
  • 601, 631, 661 Wrong word in birth location: Text is not a location. If location is not known, location field should be empty.
  • 602, 632, 662 "Y" location: Y is not a location. I this locations were part of GEDCOM imports (Maybe some error in GEDCOM format) and never corrected. Checking also for yes.
  • 603, 633, 663 USA used too early: USA is used before the country existed. Old name should be used.
  • 604, 634, 664 Too short location: Short locations are not allowed, since they can be ambiguous. Also people from other parts of the world don't understand them. For now MinLength is 4 with exceptions like USA, UK. American states should be at least in form PA, USA which is longer than 4 letters.
  • 605, 635, 665 Number in location: In locations there is only a number. It is often date entered in wrong field.
  • 606, 636, 666 Bogus location: This location is inserted as location by autocomplete operations of some softwares or websites.
  • 607, 637, 667 Misspelled word:
  • 608, 638, 668 Misspelled country:
  • 609, 639, 669 Wrong character:
  • 610, 640, 670 Location in UPPERCASE:
  • 611, 641, 671 Location in lowercase:

700 Name errors

800 Biography

900

  • 901 unconnected empty public profiles: I added this error to find empty unlinked profiles. That means the profile has no relations (parents, children, marriage) and no birth and death data (date nor location) and is public. This was added based on Jillaine Smith request.
  • 902 unconnected empty open profiles: I added this error to find empty unlinked profiles. That means the profile has no relations (parents, children, marriage) and no birth and death data (date nor location) and is open. This was added based on Jillaine Smith request.

910 Sweden specific

ToDo

  • Merging tool, that would compare also relatives . Done.
  • create completeness scoring of the profile.
  • Add new errors
    • Problems with unicode characters in some GEDCOM imports. Done.
    • 104: At the moment max age is 110 years and will be lowered as current errors are corrected.
    • 105 Reduce similarity as current errors are corrected.
    • 1xx Find duplicates were S=Š Or ss = ß or A=Å
    • 205, 305 Do not allow false errors. Calculations are now exact. Excep Before and After qualifiers.
    • 400 Mclean-3147 suggested to find all partners with same LNAB. Generally they shouldn't be the same.
    • 600 Locations
      • See on what is correct location field.
    • 900 Any profile field empty .


This page was last modified 12:59, 21 March 2017. This page has been accessed 21,719 times.