|
- This page is part of the Data Doctors Project.
- Latest report: March 16th 2025.
- Data Doctors Challenge: Reference_Tags_LXII and
.
- Custom reports by: Suggestion lists, Unsourced lists, Unconnected lists.
- See
for custom reports and statistics and our Video Collection.
- Latest ProjectBox Report: Project Report
- Latest Categories Report: Categories Suggestions Report
|
| Team Tennessee!! |
|
|
| Welcome to Team Tennessee!! |
|
|
| Team Tennessee Volunteers!! |
|
| State welcome sign |
... ... ... is participating with Team Tennessee Volunteers during the 2019 Clean-a-Thon.
... ... ... is participating with Team Tennessee Volunteers during the 2019 Clean-a-Thon.
... ... ... is participating with Team Tennessee Volunteers during the 2019 Clean-a-Thon.
Contents
|
Quick Links
(You can also get to this via links in the spreadsheet cells.)
Those 2 labelled photos should give you all the basics.
- To see a step-by-step tutorial on how to find, correct, and update errors, see this tutorial:
- https://www.wikitree.com/wiki/Spring_Clean-a-Thon_Tutorial
- https://www.wikitree.com/wiki/Project:Data_Doctors - see Database errors project for more info
(NEW on every WikiTree profile this report can be run by selecting drop down menu called Suggestions under My Wiki Tree and your WikiTree ID in the right hand corner at the top.)
- Link to Spreadsheet: https://tinyurl.com/TeamTenn
- https://prnt.sc/hk72jy
- http://prntscr.com/j50ehs
Those 2 labelled photos should give you all the basics.
- Instructions how to use spreadsheet for TeamTenn: http://prntscr.com/j50ehs *There is a chat function in the sheet. If you want to participate in "live chat" please private message your email address to Tibbetts-150. (Hint: If you don't see the chat button on the sheet, he doesn't have your email.)
- https://www.wikitree.com/g2g/595737/do-you-have-clean-a-thon-questions
- https://www.wikitree.com/wiki/Help:Spring_Clean-a-Thon#Teams
- https://www.wikitree.com/wiki/Spring_Clean-a-Thon Main Clean-a-Thon page
- https://www.wikitree.com/g2g/788370/team-tennessee-volunteers-2019-spring-clean-thon-team-chat
- https://www.wikitree.com/g2g/595735/who-will-win-a-clean-a-thon-prize
- https://www.wikitree.com/wiki/Help:Spring_Clean-a-Thon#Tracking_progress
- Here is a help page about setting the status
- https://www.wikitree.com/wiki/Space:DBE_Status
This is our third (!) annual Clean-a-Thon. The mission is to clear out as many database suggestions as possible over the 72 hours.
The cleaning will start on Friday, April 26, at 8 AM (EDT) and run until Monday, April 29, at 8 AM (EDT).
Will you join us?
WikiTree will host Hangouts every four hours to update the progress of top contributors and all the teams. The schedule and links are here: Hangouts schedule.
You can check on your own progress and your team’s progress using the links here: Tracking your progress
Each error that is resolved, either corrected or marked as false, will score you a point.
We're also giving away special 2019 Clean-a-Thon t-shirts as prizes! All prizes are door prizes-all you need to do is participate to be eligible to win one. These will be announced during the Hangouts, then posted on our G2G Prize post.
Your team has a free-space page with links to errors your team might like to focus on. It may also have links to sources to help with correcting the errors and hints. If not, feel free to add some! Each team also has a G2G post where you can shout out progress you’re making, see updates about how your team is doing, post any fun circumstances you run into, or ask for help from your team leader. We’ll be checking these periodically to talk about during Hangouts. Check with your team Captains if you aren't sure where to find your team's free space page and G2G post.
We’ll start looking at stats and post how much all you awesome WikiTreers accomplished as soon as we can.
Status
Setting the status of an error is described on Error status Help page
Goal
Our goal for the Spring Clean-a-Thon is to clear out as many database suggestions as possible. To make it fun we're having teams and competing to see who can clear out the most. The WikiTree Spring Clean-a-Thon is focused on cleaning up the “cobwebs” around the site, with a primary focus on the errors discovered by the Database Errors Project. Your team free-space page has tables and links to the errors that might be of interest to you. You can work on any error, though.
What to Do
Fix Errors! See chart below for links to error lists. You can choose to work on a certain type of error, or you can work on any Tennessee profile errors. Your choice! All help is needed and welcome! Our goal for the Spring Clean-a-Thon is to clear out as many database suggestions as possible. To make it fun we're having teams and competing to see who can clear out the most.
How to Get Started
•First, read the project documentation below. •Second, check and correct errors on your managed profiles to learn the process. (My WikiTree / Error Report or Click here). •Next, check and correct errors on your extended family tree to learn the process. (On starting profile Second menu / Error report or Click here). •Optionally, check and correct errors on your watchlist. (Click here. It redirects you to apps server, where you have to login with WikiTree credentials). •Then you might correct errors by type. Check out the Latest errors list to find error types you can correct. Read the help information 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 the Latest errors page so that others will know that error is already being checked. •You can also use prepared error lists by country, US states, projects,... (Custom lists) •Or you can correct errors by location (your town, region, country ...) (Click here). •Or you can correct errors by person’s names (first or last names) (From last name page on WikiTree click Error report (last name page or define custom search Click here).
Data doctors need to become familiar with all error types since there can be more than one error on the profile and they can each give you a clue to finding a main problem. Then all the errors can be corrected at once. But you may choose to specialize in one error type.
How to Join Team Tennessee
- Go to the https://www.wikitree.com/g2g/787244/have-you-registered-for-the-2019-spring-clean-a-thon-yet and leave an answer (not comment) to let them know you want to join the Clean a Thon, on Team Tennessee Volunteers. They will get you a badge.
- Go to the G2G thread and let us know you've joined.
- Read the general Clean a Thon instructions here and ask questions, if you have them. I can help you, or you can ask a Leader for help.
- Decide which errors you want to work on (see below) and add your name to the task list
- Have fun, and be accurate!
Participation instructions
To see a step-by-step tutorial on how to find, correct, and update errors, see this tutorial: Spring_Clean-a-Thon_Tutorial
Team Members
- 1: Team Leader:Linda Barnett, Data Doctor |See your work
- 2: Stephen Pierce, Data Doctor |See your work
- 3: M. Hilliard|See your work
- 4: Judy Bramlage | See your work
- 5: Elissa Ertwine, Data Doctor |See your work
- 6: Arthur Van Riper |See your work
- 7: Beverly Davis Ahrens |See your work
- 8: Tim Prince |See your work
- 9: Azure Robinson, Data Doctor |See your work
- 10: Terry McClintock, Data Doctor |See your work
- 11: Pam Vick, |See your work
- 12: Lance Martin, Data Doctor|See your work
- 13: Ellen Bradley, Data Doctor|See your work
- 14: Philip Smith, |See your work
- 15: Monica Watkins, |See your work
- 16: Karen Wells, |See your work
- 17: Katy Morrison, |See your work
- 18: Jennifer Jordan, |See your work
- 19: Mary Jenkins, |See your work
- 20: Linda Ritcher, |See your work
- 21: Martha Garrett, |See your work
- 22: Pansy Roper, |See your work
- 23: Vicki Parrott, |See your work
- 24: Renee Cash, |See your work
Instructions
Participation instructions
To see a step-by-step tutorial on how to find, correct, and update errors, see this tutorial: Spring_Clean-a-Thon_Tutorial
Task List
Where to find suggestions
There are a few different ways to choose suggestions to work on:
By Project:
•Go to the category page for the project you're interested in, e.g., Category: Project Name Project -- and look for the sub-categories named "Project Name Needs ..." or "Project Name Maintenance Categories".
• Use the "Managed By
" option on WikiTree+ and enter the Project Account to run the error list on the watchlist for your project. You can find a list of Project Accounts here: Category: Project Accounts
By Surname:
• Go to any surname page and click the "error report" link (HINT: It's in the middle of the links above the list of profiles)
By Error Type:
Working errors by Error Type: Add your name below, to the area in which you wish to work (click the edit tab on this page, scroll down, fill in the blanks, click "save changes")
- 100-errors: Person-related - (Linda Barnett); (Katy Morrison);
- 200-errors: Father-related - (Linda Barnett);
- 300-errors: Mother-related - (Linda Barnett);
- 400-errors: Marriage-related - (Linda Barnett);
- 500-errors: Name/Gender-related - (Linda Barnett);(Karen Wells);
- 550-errors: Wikidata-related - (Mary Weston);(Linda Barnett)
- 587-errors: FindAGrave - Link to non existing Grave ID- (Linda Barnett);(Mary Weston);(Karen Wells)
- 600-errors: Location-related - (Linda Barnett);(Karen Wells)
- 700-errors: Name-related - (Linda Barnett);(Karen Wells); (Katy Morrison)
- 800-errors: Biography-related - (Azure Rae Robinson);(Linda Barnett)
Error report
'"I have the DBE ErroList TN linked to the spreadsheet tab named Team Ten as the URL is listed just click on that and you will see the list. Also down below the list is your name and you can choose what color you want and color the cell that your name is in. Then when you choose what error you want to clean up put the color that you choose in cell you choose to work on."'
To work an error, simply click on the number link in the "open" column beside the error type you wish to work on. A report will open, and it will give you a list of errors to be corrected. Follow the steps given to correct them.
Note: Aleš has developed a way to perform automatic tracking for the Clean-a-Thon changes so we don't need to report or add links of profiles here or at the Team page, to show what we have corrected or where we added posts or sources this time.
- https://www.wikitree.com/wiki/Project:Data_Doctors - see Database errors project for more info
NEW on every WikiTree profile this report can be run by selecting drop down menu called Suggestions under My Wiki Tree and your WikiTree ID in the right hand corner at the top.
Tennessee
Suggestion report for Tennessee. There were 125477 suggestions for 784629 profiles on 16 Mar 2025.
Suggestions
Unique Names
| Unique Names suggestions on 20250316 | Total | 0000-0000 | 0001-1499 | 1500-1699 | 1700-1799 | 1800-1899 | 1900-1999 | 2000-9999 | Private | Hidden | New |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Total | 4031 | 26 | 0 | 0 | 309 | 2728 | 926 | 0 | 42 | 1227 | 7 |
| Unique Names | Total | 0000-0000 | 0001-1499 | 1500-1699 | 1700-1799 | 1800-1899 | 1900-1999 | 2000-9999 | Private | Hidden | New |
| Warning 717: Unique name in Prefix | 11 | 2 | 9 | 3 | |||||||
| Warning 727: Unique name in First Name | 302 | 1 | 21 | 233 | 44 | 3 | 141 | ||||
| Warning 737: Unique name in Preferred Name | 151 | 16 | 112 | 23 | 40 | ||||||
| Warning 747: Unique name in Middle Name | 1808 | 1 | 55 | 1276 | 454 | 22 | 645 | 5 | |||
| Warning 757: Unique name in Nicknames | 451 | 3 | 38 | 306 | 98 | 6 | 159 | ||||
| Warning 767: Unique name in Suffix | 3 | 2 | 1 | ||||||||
| Warning 777: Unique name in Last Name at Birth | 576 | 10 | 88 | 386 | 87 | 5 | 87 | 1 | |||
| Warning 787: Unique name in Current Last Name | 361 | 5 | 21 | 181 | 152 | 2 | 52 | ||||
| Warning 797: Unique name in Other Last Names | 368 | 6 | 70 | 230 | 58 | 4 | 100 | 1 |
WikiData
FindAGrave
Profile Completeness
Table prepared at 18.03.2025 14:24:18 (Slovenian time). Condition to prepare list (Location is Tennessee,TN).
Description of Errors
100 Person
- 101 Birth in future: This one is obvious. We are not fortune tellers. The most common cause is a typo in the birth date. This error is checked on all profiles where a birth date is recorded.
- 102 Death in future: This one is obvious. We are not fortune tellers. The most common cause is a typo in the death date. It is checked on all profiles where a death date is recorded.
- 103 Death before birth: Death date is before birth date. The most common cause is a typo in the birth date or the death date. It is checked on all profiles with both dates.
- 104 Too old: The Person is too old at death. At the moment the maximum age is 110 years and will be lowered as current errors are corrected.The most common cause is a typo in the birth date and/or death date . It is checked on all profiles with both dates.
- 105 Duplicate sibling: A profile exists with the same full name, birth and death dates and both parents as this one. These two profiles are probably duplicates and need to be merged. An exception to this is stillborn unnamed twins. If you find they are not the same person, after looking at both profiles and sources, you can mark the error as a False Error. Similarity will be reduced as current errors are corrected.
- 106 Duplicates between global tree and unconnected: A profile exists that has the same full name, and birth and death dates as another profile and is not connected in any tree. Orphan profiles are ignored. These are probably duplicates and need to be merged. With this action an unconnected tree is connected to the global tree. If you find they are not the same person, after looking at both profiles and sources, you can mark the error as a False Error. You need to mark it for both profiles.
- 107 Full name in UPPERCASE: These profiles have the whole full name in uppercase. This error is no longer calculated.
- 108 Full name in lowercase: These profiles have the whole full name in lowercase. This error is no longer calculated.
- 109 Profile should be open (birth date): These profiles should be open, since the birth date is older than 150 years or the birth date is wrong.
- 110 Profile should be open (death date): These profiles should be open, since the death date is older than 100 years or the 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: These are profiles where one person appears as 2 or more relations on the same profile.
- 114 Still Living Status and Entered Death Date:These profiles have "Still living" selected, but have a death date entered.
- 115 Still Living Status and Entered Death Location: Same as 114, but a death location is entered.
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 is similar to 109 and 110, but are identified for profiles with no birth and death date and their children were born more than 135 years ago.
- 213 Missing fathers DNA confirmation: Father is marked ‘confirmed with DNA’, but the words ‘paternal’ and ‘confirmed’ do not appear in the biography. This suggestion is overseen by the DNA Project.
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 is similar to 109 and 110, but are identified for profiles with no birth and death date and their children were born more than 135 years ago.
- 313 Missing mothers DNA confirmation: Mother is marked ‘confirmed with DNA’, but the words ‘maternal’ and ‘confirmed’ do not appear in the biography. This suggestion is overseen by the DNA Project.
400 Marriage
- NOTE: Marriage dates and places can be edited by first clicking on the profile's edit tab. Then look for the "edit marriage" link below the spouse in the Edit Family section on the right.
- 401 Spouse is self: The person is married to themselves. The marriage should be deleted (and, ideally, replaced with the proper one). Look for the "add/remove a spouse" link in the Edit Family section of the person's edit page.
- 402 Unknown gender of spouse: The person's spouse does not have a gender. If it can be confidently determined, set the spouse's gender for their edit page.
- 403 Single sex marriage: Both spouses have the same gender. Same-sex marriage is not uncommon today but it was rare in history. Verify that one of the partners does not have the wrong gender and edit if appropriate.
- 404 Marriage before birth: The person's marriage date is before their birth date. If the correct marriage date or the person's birth date can be confidently determined from a source, fix it.
- 405 Marriage too long after birth:The person's marriage date is more than 115 years after their birth date.
- 406 Marriage after death: The person's marriage date is after their death date. If the correct marriage date or death date can be determined, fix it.
- 407 Lived too long after marriage: The person lived too long after marriage. So probably death or marriage date is wrong. Limit is set at 115 years. Correct death or marriage date.
- 408 Multiple marriages on same day: The person married more than one spouse on the same day. If one marriage date is incorrect, fix it, or if the spouses are duplicates, merge them.
- 409 Marriage to duplicate person: The person married more than one person with the same name. If the spouses are duplicates, merge them.
- 410 Marriage in future: The marriage date is after today's date. Correct the date if it can be determined from a source.
- 411 Marriage End Date in future: The marriage end date is after today's date. Correct the date if it can be determined from a source.
- 412 Marriage End Date before Marriage Date: The marriage end date is before the marriage date.
- 413 Marriage too long: The difference between the marriage date and the marriage end date is more than 115 years.
- 414 Marriage End Date before Birth Date: The marriage end date is before the person's birth date. If the correct birth or marriage date can be determined, fix it.
- 415 Marriage End Date too late: The difference between the person's birth date and their marriage date is too long. The dates would mean the person's marriage ended when they were over 115 years old.
- 416 Marriage End Date after Death Date: The person died before their marriage ended.
- 417 Death Date too long after Marriage End Date: The difference between the person's death date and marriage end date is more than 115 years. This would mean they lived more than 115 years after their marriage ended.
- 418 Spouse is a sibling: The person's spouse has one of the same parents. This is not impossible but unlikely. If the problem can be determined, correct it.
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.
- 551 Wikidata - Missing gender: This error indicates that there is missing data in WikiTree and is present in WikiData.
- 552 Wikidata - Different gender: This error indicates that there is a mismatch between the data we have in WikiTree and Wikidata
- 553 Wikidata - Empty Birth Date: This error indicates that there is missing data in WikiTree and is present in WikiData.
- 554 Wikidata - Imprecise birth date: This error indicates that the birth date in WikiTree is less precise compared with the birth date in WikiData.
- 555 Wikidata - Different birth date: This error indicates that the birth date in WikiTree is different compared to the birth date in WikiData.
- 556 Wikidata - Empty death date: This error indicates that there is missing data in WikiTree that is present in WikiData.
- 557 Wikidata - Imprecise death date: This error indicates that the death date in WikiTree is less precise compared with the death date in WikiData.
- 558 Wikidata - Different death date: This error indicates that the death date in WikiTree is different compared to the death date in WikiData.
- 559 Wikidata - Missing birth location: This error indicates that the birth location is missing in WikiTree and is present in WikiData.
- 561 Wikidata - Missing death location: This error indicates that death location is missing in WikiTree and is present in WikiData.
- 563 Wikidata - Possible duplicate by father: This error indicates a possible duplicate profile on WikiTree. They are derived from WikiData data.
- 564 Wikidata - Possible father: This error indicates a missing father relation to existing profile on WikiTree. They are derived from WikiData data.
- 565 Wikidata - Possible duplicate by mother: This error indicates a possible duplicate profile on WikiTree. They are derived from WikiData data.
- 566 Wikidata - Possible mother: This error indicates a missing mother relation to existing profile on WikiTree. They are derived from WikiData data.
- 568 Wikidata - Unconnected branches to global tree: This Wikidata (notable) profile has no connection to the WikiTree global tree. However it is possible the profile can be already connected to the WikiTree global tree through private profiles.
- 569 Wikidata - Unconnected orphans to global tree: Same as 568 except for orphaned profiles.
570 Find-A-Grave
Some WikiTree profiles are referencing memorials on Find-A-Grave.com.
- 571 FindAGrave - Link without Grave ID: This error indicates a wrong URL to Find-A-Grave.
- 572 FindAGrave - Link without matching Grave: This error indicates a wrong URL to Find-A-Grave.
- 573 FindAGrave - Empty birth date: This error indicates a mismatch between the WikiTree profile and the Find-A-Grave profile.
- 574 FindAGrave - Imprecise birth date: This error indicates a mismatch between the WikiTree profile and the Find-A-Grave profile.
- 575 FindAGrave - Different birth date: This error indicates a mismatch between theWikiTree profile and the Find-A-Grave profile.
- 576 FindAGrave - Empty death date: This error indicates a mismatch between the WikiTree profile and the Find-A-Grave profile.
- 577 FindAGrave - Imprecise death date: This error indicates a mismatch between the WikiTree profile and the Find-A-Grave profile.
- 578 FindAGrave - Different death date: This error indicates a mismatch between the WikiTree profile and the Find-A-Grave profile.
- 579 FindAGrave - Missing birth location: This error indicates a mismatch between the WikiTree profile and the Find-A-Grave profile.
- 581 FindAGrave - Missing death location: This error indicates a mismatch between the WikiTree profile and the Find-A-Grave profile.
- 585 FindAGrave - Multiple profiles link to same grave ID: This error indicates that two WikiTree profiles may need to be merged.
- 586 FindAGrave - Link to merged Grave ID: This error indicates that the link should be changed.
- 587 FindAGrave - Link to nonexisting Grave ID: This indicates an error.
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 location: Text is not a location. If the location is not known, location field should be empty.
- 602, 632, 662 "Y" location: Y is not a location. These locations were part of GEDCOM imports and never corrected. (The field place is filled with "Y" or "Y/" or "Y;" or "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 Minimum Length is 4 characters 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 the location field there is only a number. It is often a date entered in the wrong field.
- 606, 636, 666 Bogus location: This location is inserted by autocomplete operations of some softwares or websites.
- 607, 637, 667 Misspelled word: One of the words in the location is misspelled.
- 608, 638, 668 Misspelled country: The last word (the country) in the location is misspelled.
- 609, 639, 669 Wrong character: There is unusual letter character in the location field.
- 610, 640, 670 Location in UPPERCASE: All characters of the location are in uppercase. This is an incorrect presentation of the location.
- 611, 641, 671 Location in lowercase: All characters of the location are in lowercase. This is an incorrect presentation of the location.
- 612, 642, 672 Location too early in location The location field should have the name that existed when the event took place. This error is shown when the country is used before the country existed....
- 613, 643, 673 Parentheses in location: Parentheses should not be in location fields. Either remove the information to the biography if it does not belong in the location field, or remove the parentheses if the place name is correct with them.
700 Name Errors
- 711, 721, 731, 741, 751, 761, 771, 781, 791 Separators in Name: There should be no separators in the field (such as punctuation or spaces). Exceptions to this rule are stated for each field on its help page.
- 712, 722, 732, 742, 752, 762, 772, 782, 792 Number in Name:
- 713, 723, 733, 743, 753, 763, 773, 783, 793 Suffix in Name:
- 714, 724, 734, 744, 754, 764, 774, 784, 794 Wrong word in Name:
- 715, 725, 735, 745, 755, 765, 775, 785, 795 Wrong character in Name:
800 Biography
- 801 Big profile: This error shows big profiles. A big profile doesn't necessarily mean it is a problem it is just a profile with more than 200,000 letters.
- 802 Empty profile: This error shows empty profiles. Every profile in WikiTree should have sources.
- 803 Almost empty profile: Since all profiles on WikiTree should be sourced, a profile with nearly no text is an unsourced profile and needs sources.
- 811 Uncleaned profile after merge: After a merge, you need to edit the new profile's biography and merge the information from both profiles to have only one Biography and one Sources section.
- 821 Heading starts with blank: Wiki syntax defines that a new line starting with a = is a Caption/Heading. This heading is not left justified and has a blank space before the =.
- 822 Heading doesn't end with =: Wiki syntax defines that a new line starting with a = is a Caption/Heading. This heading does not end with an equal number of =.
- 823 Heading doesn't start with =: Wiki syntax defines that a new line starting with a = is a Caption/Heading. This heading does not begin with an equal number of =.
- 824 Heading different number of =: Wiki syntax defines that a new line starting with a = is a Caption/Heading. This heading does not have an equal number of = on each side.
- 825 Use separator line ----: Wiki syntax has four minuses on a line to make a separator line. You should not make a visual separator line with ========= since it interferes with captions.
- 831 Multiple duplicated lines: There are many cases of repeated paragraphs or lines in biographies. Delete the duplicate lines.
- 835 Local file reference: This error lists profiles that contain references to files on a local computer. These files are not visible to anyone on internet. See the help page for an example.
- 841 Template doesn't start with double {:Missing double { at the beginning of a template on the profile.
- 842 Template doesn't end with double }: Missing double { at the end of a template on the profile.
- 843 Missing template (spelling): There is a spelling error in template name, the template could have been deleted from WikiTree or it never existed.
- 844 Out of use template: Template is not meant to be used directly or was replaced with another one.
- DBE_845 Direct usage of base templates: The profile is using {{Project Box|etc}} or {{Sticker|etc}} instead of the correct project name for the project box, ie {{Roll of Honor|etc...}}.
- DBE_846 Died before template time frame: The template used does not allow profiles with a death date before a certain date.
- DBE_847 Born after template time frame: The template used does not allow profiles with a birth date after a certain date.
- DBE_848 Error in template parameters: Unacceptable values have been used in the template.
- DBE_851 GEDCOM uncleaned Interpret date: In the biography, there is a GEDCOM import warning that the date couldn't be used. Check to see if the date has been added to the correct date field. Then delete the warning.
- DBE_852 GEDCOM uncleaned Parse Lastname: In the biography, there is a GEDCOM import warning that the last name couldn't be parsed. Check to see if the name has been added to the correct name field. Then delete the warning.
- DBE_861 Inline citation doesn't start with <ref>: The end of a citation </ref> is found, but there is no beginning of the citation <ref>.
- DBE_862 Inline citation doesn't end with </ref>: Start of a citation <ref> is found, but there is no end of the citation </ref>.
- DBE_863 Missing <references /> tag: Profile has inline citations <ref>...</ref>, but doesn't have a <references /> tag on the profile below the sources heading.
900 Unconnected Profiles
- 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.
