US_State_Flag_Images-46.png

Team Tennessee Volunteers - 2018 Spring Clean-a-Thon

Privacy Level: Open (White)

Surnames/tags: Team Tennessee Data Doctor Clean-a-Thon
This page has been accessed 3,070 times.

Categories: Clean-a-Thon Teams | DD Clean-a-Thon 2018 | Challenges.

This page is part of the Data Doctors Project.
Latest report: December 2nd 2018 and the Spreadsheet.
Custom reports by: Suggestion lists, Unsourced lists, Unconnected lists.
See WikiTree+ for custom reports and statistics.
Data Doctors Challenge: Location IX .


Team Tennessee!!
Welcome to Team Tennessee!!
Team Tennessee Volunteers!!
State welcome sign
... ... ... is participating with The Team Tennessee Volunteers during the 2018 Clean-a-Thon, correcting 6,207 suggestions.
... ... ... is participating with The Team Tennessee Volunteers 1 during the 2018 Clean-a-Thon, correcting 3,307 suggestions.
... ... ... is participating with The Team Tennessee Volunteers 2 during the 2018 Clean-a-Thon, correcting 2,900 suggestions.
... ... ... is participating with The Team Tennessee Volunteers during the 2018 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.

(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.)

Those 2 labelled photos should give you all the basics.

If you have any questions during the Clean-a-thon, you can post them here on our G2G questions post: G2G Questions post. It will also have links to important Clean-a-Thon pages that may also answer the questions you have.

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 2018 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.

Everything wraps up Monday, April 23th at 12:00 am EDT. 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. (April 15th 2018) •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 pageor 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

  1. Go to the Spring Clean-a-Thon Registration G2G thread 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.
  2. Go to the G2G thread and let us know you've joined.
  3. 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.
  4. Decide which errors you want to work on (see below) and add your name to the task list
  5. 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: https://www.wikitree.com/wiki/Spring_Clean-a-Thon_Tutorial

Team Members

Team Tennessee Volunteers 1

Team Members

Team Tennessee Volunteers 2

Instructions

Participation instructions

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

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")

  1. 100-errors: Person-related - (Holly Battle); (Teri Taylor); (Robert Taylor); (Tracy Leighton); (Name);
  2. 200-errors: Father-related - (Emily Holmberq); (Gigi Ward); (Teri Taylor); (Robert Taylor); (Tracy Leighton); (Name);
  3. 300-errors: Mother-related - (Cindi Clark); (Gigi Ward); (Teri Taylor); (Robert Taylor); (Tracy Leighton); (Name);
  4. 400-errors: Marriage-related - (Cindi Clark); (Gigi Ward); (Teri Taylor); (Robert Taylor); (Tracy Leighton); (Name);
  5. 500-errors: Name/Gender-related - (Linda Barnett); (Holly Battle); (Gigi Ward); (Gwen Edwards-Fleming); (Name);
  6. 550-errors: Wikidata-related - (Linda Barnett); (Emily Holmberq); (Gigi Ward); (Gwen Edwards-Fleming);; (Name);
  7. 587-errors: FindAGrave - Link to non existing Grave ID- (Gwen Edwards-Fleming); (Linda Barnett); (Name);
  8. 600-errors: Location-related - (Linda Barnett); (Emily Holmberq); (Eileen Bradley); (Name):
  9. 700-errors: Name-related - (Linda Barnett); (Holly Battle); (Name);
  10. 800-errors: Biography-related - (Linda Barnett); (Holly Battle); (Kris Shearer): (Eileen Bradley); ( Alice Ann Fesmire); (Name);

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.

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 33098 suggestions on 2018-12-02.

33098 Suggestions on 20181202 Total 0000-0000 0001-1499 1500-1699 1700-1799 1800-1899 1900-1999 2000-9999 Open New
Date
103 Death before birth 9 2 7 2
104 Too old 119 1 62 56 116
131 No Dates - No Dates on relatives - Open - Unknown Status 80 80 80
132 No Dates - No Dates on relatives - Open - Status Died 10 10 10
133 No Dates - Dates on relatives - Open - Unknown Status 559 559 559
134 No Dates - Dates on relatives - Open - Status Died 124 124 124
205 Father is too young or not born 719 1 221 471 26 702 5
206 Father is too old 56 6 33 17 54
210 Father was dead before birth 803 25 18 290 466 4 800
305 Mother too young or not born 1095 1 374 679 41 1070 2
306 Mother is too old 50 16 23 11 50
310 Mother was dead before birth 895 9 15 324 542 5 894 1
404 Marriage before birth 131 21 101 9 121 1
405 Married too old 15 15 15
406 Marriage after death 164 2 73 86 3 163 2
407 Lived too long after marriage 1 1 1 1
412 Marriage End before marriage 2 2 2
416 Marriage End after death 44 1 8 33 2 41 1
Relation
105 Duplicate sibling 9 5 2 2 9 1
106 Duplicates between global tree and unconnected 50 13 37 48 6
112 Person is Father and mother 4 4 2
113 Duplicate in relatives 6 1 3 1 1 4 2
209 Father is also a sibling 20 5 14 1 16 1
211 Duplicate sibling by father 13 4 9 13 5
213 Missing fathers DNA confirmation 471 3 22 362 84 404 14
308 Mother is also a spouse 2 1 1 1 1
309 Mother is also a sibling 1 1 1
311 Duplicate sibling by mother 7 1 6 7
313 Missing mothers DNA confirmation 371 1 14 290 66 328 11
408 Multiple marriages on same day 90 4 37 49 90 4
409 Marriage to duplicate person 195 10 100 85 193 9
418 Partner is also a sibling 11 6 5 11 1
Name
511 Unique names (spelling) 4191 25 6 250 3153 757 3937 14
713 Suffix in Prefix 1 1 1 1
714 Wrong word in Prefix 3 3
721 Separators in First Name 67 1 55 11 19
723 Prefix in First Name 149 3 4 126 16 120 1
724 Wrong word in First Name 18 14 4 7 1
731 Separators in Preferred Name 2 2
733 Prefix in Preferred Name 13 2 1 5 5 8 1
734 Wrong word in Preferred Name 1 1
741 Separators in Middle Name 1 1 1
743 Prefix in Middle Name 46 3 26 17 43
744 Wrong word in Middle Name 14 1 1 5 7 12
751 Separators in Nicknames 14 1 8 5 11 1
753 Prefix in Nicknames 88 1 1 14 50 22 85
754 Wrong word in Nicknames 43 2 33 8 40 1
761 Separators in Suffix 6 4 2 5
763 Prefix in Suffix 5 1 3 1 5 2
764 Wrong word in Suffix 2 2
771 Separators in Last Name at Birth 19 3 16 19
774 Wrong word in Last Name at Birth 73 1 22 50 72 1
781 Separators in Current Last Name 13 4 8 1 12
791 Separators in Last Name Other 1 1 1 1
Gender
203 Father is Female 5 4 1 2
303 Mother is Male 4 4 3
304 Mother has no Gender 1 1
403 Single sex marriage 5 1 3 1 2 2
501 Wrong gender (male) 36 1 5 27 3 32
502 Missing gender (male) 22 2 10 10
503 Probably wrong gender (male) 60 2 1 46 11 48 1
504 Missing gender (probably male) 7 5 2 2
505 Wrong gender (female) 34 2 25 7 30 1
506 Missing gender (female) 11 1 7 3
507 Probably wrong gender (female) 63 2 53 8 58 3
508 Missing gender (probably female) 7 1 3 3
509 Missing gender 86 3 54 29 70
510 Unique name without gender 33 3 25 5 22
Location
601 Wrong word in birth location 13 3 1 5 4 2 1
603 USA too early in birth location 2735 2 2733 2735 23
604 Birth location too short 4 1 2 1 2
605 Number in birth location 13 1 1 10 1 11 3
607 Misspelled word in birth location 3 1 1 1 1
608 Misspelled country in birth location 22 5 12 5 12 1
610 Birth location in uppercase 31 1 22 8
611 Birth location in lowercase 97 18 45 34
631 Wrong word in death location 1745 4 5 1285 451 1610 1
633 USA too early in death location 7 1 6 7
634 Death location too short 7 4 3 7 1
635 Number in death location 42 3 34 5 33 1
637 Misspelled word in death location 4 4 3 2
638 Misspelled country in death location 34 1 1 21 11 9 4
640 Death location in uppercase 26 2 19 5
641 Death location in lowercase 76 18 29 29
644 Death location too long 10 10 10
661 Wrong word in marriage location 2 2
663 USA too early in marriage location 9 9 9
664 Marriage location too short 1 1 1 1
665 Number in marriage location 1 1 1 1
668 Misspelled country in marriage location 5 5
670 Marriage location in uppercase 3 3
671 Marriage location in lowercase 5 2 3
Privacy
109 Profile should be open (birth date) 157 157 1
110 Profile should be open (death date) 51 1 38 12 2
119 Still living in Death Location status with death location 1 1
212 Profile should be open (Child birth date) 13 13
312 Profile should be open (Child birth date) 11 11
Biography
801 Big profile 18 1 13 4 17
802 Empty profile 178 26 14 107 31 100 3
803 Almost empty profile 172 6 32 121 13 155
811 Uncleaned profile after merge 3689 26 2 675 2759 227 3391 3
821 Headings starts with blank 7 2 3 2 3 2
822 Heading doesn't end with = 70 8 52 10 60
823 Heading doesn't start with = 50 6 38 6 49 1
824 Heading different number of = 44 11 23 10 32 3
825 Use separator line ---- 7 4 3 7 1
831 Multiple duplicated lines 1020 117 810 93 962 6
835 Local file reference 1512 6 8 1238 260 1446
851 GEDCOM uncleaned Interpret date 589 101 41 419 28 461
852 GEDCOM uncleaned Parse Lastname 36 3 33 34
861 Inline citation doesn't start with <ref> 4 1 3 2
862 Inline citation doesn't end with </ref> 124 10 102 12 111 4
863 Missing <references /> tag 57 3 36 18 22 6
Template
842 Template doesn't end with double } 1 1 1 1
843 Missing template (spelling) 9 2 5 2 9 4
845 Direct usage of base templates 2 2 2
846 Died before template time frame 2 2 2
847 Born after template time frame 2 1 1 2
848 Error in template parameters 4 3 1 4 2
WikiData
554 Wikidata - Imprecise birth date 3 3 3
555 Wikidata - Different birth date 20 12 6 2 20
557 Wikidata - Imprecise death date 3 3 3
558 Wikidata - Different death date 23 6 13 4 23
561 Wikidata - Missing death location 1 1 1
568 Wikidata - Unconnected branches to global tree 41 2 21 18 39
569 Wikidata - Unconnected orphans to global tree 100 9 67 24 100
FindAGrave
571 FindAGrave - Link without Grave ID 1884 1 69 1498 316 1764 6
572 FindAGrave - Linked grave not matching profile 1005 11 189 703 102 984 7
573 FindAGrave - Empty birth date 3 3 2
574 FindAGrave - Imprecise birth date 761 74 615 72 750 13
575 FindAGrave - Different birth date 2269 367 1720 182 2230 33
576 FindAGrave - Empty death date 151 1 6 134 10 146 3
577 FindAGrave - Imprecise death date 670 1 98 481 90 660 9
578 FindAGrave - Different death date 1154 1 259 802 92 1145 21
579 FindAGrave - Missing birth location 459 2 64 287 106 448 3
581 FindAGrave - Missing death location 443 17 349 77 434 11
585 FindAGrave - Multiple profiles link to same grave ID 108 44 62 2 106 11
586 FindAGrave - Link to merged Grave ID 2 1 1 1
587 FindAGrave - Link to nonexisting Grave ID 3 2 1 3 3

Table prepared at 05.12.2018 0:10:49 (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.

570 Find-A-Grave

Some WikiTree profiles are referencing memorials on Find-A-Grave.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 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

800 Biography

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.

910 Sweden Specific







Images: 1
Tennessee State Flag
Tennessee State Flag

Collaboration

On 28 Apr 2018 at 20:49 GMT Linda Barnett wrote:

Hi you'll Thank you for your participating in the 2018 Team Tennessee Volunteers Clean-a-Thon. I hope you will join me again this fall for the 2019 Team Tennessee source-a-thon and next year for the 2019 Team Tennessee Volunteers Clean-a-Thon. I had fun doing this no matter if I did get stress with my life at home.

On 28 Apr 2018 at 20:11 GMT Linda Barnett wrote:

Hi everyone here is what the team participants did in the two teams.

TeamTennessee Volunteers I:

Total: 3,307

Terry Tidwell 1

Cindy Barnett 488

Linda Barnett-captain- 14

Robert Taylor 3

Jluv Taylor 1

Eileen Bradley 239

Susan Defoe 1,041

Phillip Thompson 127

Emily Holmberg 257

Sharen Moon 30

Cindi Clark 81

Deborah Dunn 195

Jamie Nelson 70

James Evans 85

Holly Battle 266

Alice Ann Fesmire 328

Beverly Ahrens 82

TeamTennessee Volunteers 2:

Total: 2,900

Barbara Mead 201

Bonnie Unal 731

Terri Taylor-Captain 100

Sydney Burnside 2

Judy Hixson 10

Kaylee Robinson 182

Nathan Horner 1

Tammy Caldwell 10

Gigi Tanksley 24

Tracy Leighton 15

Don Crum 175

Valarie Willingham 270

Randal Gardner 168

Kris Shearer 24

Gwen Fleming 31

Linda Green 834

Elaine Goodner 122

Team Tennessee Volunteers combined Total 6,207

With our team being larger this year we did a lot this year next year we will do a lot more. We will get better every time.

On 28 Apr 2018 at 16:22 GMT Linda Barnett wrote:

I checked and it okay to use the spreadsheet and the ERROR LIST (DBE ErrorList TN) this list Will be available after the clean a thon. Would be nice to keep working on in our spare time. Will you can keep working on in your spare time. So go for it.

On 28 Apr 2018 at 03:10 GMT Linda Barnett wrote:

Hi everyone this is what I was dealing with during clean-a-thon that I did not expect to deal with when I started this clean-a-thon.My biopsy that I had on my right side of my thyroid came back beign but the specialist wants me to have a thyroid ultrasound every 16 to 18 months. But since February for 45 days my dad has had diahra and he has been diagnosed with pseudo membrane colitis which started by taking antibiotics for his pneumonia that he has had 4 times this year. My mother has an UTI infection plus she has picked up a slight case of pseudo membrane colitis now. What my dad has is very contigious. It is a miracle I haven't gotten it. So since my mother was sick when my appointment on 23rd my sister came down and took me especially so when I move into her house I have to the doctor like that I will be use to her going with me when I need her to go with me. So when we got back she went with my mother to a walk in clinic so she could get some antibotics for her UTI. So I had my dad and mother to look after except for cleaning my dad. My mom did that and it about killed her plus if my mom eats the wrong thing it make her hurt and sick to her stomach and she thinks it is her hernia or gall bladder. My sister and my brother-in-law came down and went with my mother to put my dad in the hospital today for his pseudo membrane colitis because my mom just can't do it and since he has vascular demetia that he isn't like my mom says he not her husband and a father now is a different person now. He doesn't know what is being said and he fights what my mom says. So it seems too hard for my mom to clean him up since she got sick and she is very weak. She has arthiritis diease.

So during the clean-a-thon I was busy doctoring my mom and dad, also getting the quest bedroom and bathroom ready for my sister to come down on Sunday and I did try to be a leader and participate in the clean-a-thon and I did manage to do 14 corrections.

On 28 Apr 2018 at 01:05 GMT Astrid (Schellenberger) Spaargaren wrote:

Got confused at your pages but a well meant:

Congrats Team Tennessee!!!

Regards from Team Flying Dutch(wo)men!!

On 27 Apr 2018 at 15:24 GMT Eileen Bradley wrote:

Thank you Linda ! I know you jumped in at the last minute to lead our team, which I'm sure wasn't easy, and you did a great job. You are on my trusted list.

On 27 Apr 2018 at 03:35 GMT Linda Barnett wrote:

I am very proud of all you. You did all even the new ones. We cleaned a lot I will up date all of your profiles everyone should of gotten my email that the can put on the trusted list and then I can get in to edit to put your stickers on like the one that said you participate on Team Tennessee Volunteers during the 2018 Spring Clean-a-Thon but this one I adding will have how many you did on it. So the ones that don't even have the first one needs to put me on their trusted list if they want both of them even the second one even for the ones that has the first sticker even. Plus I will put on this page the least of what everyone did on the two teams of Team Tennessee Volunteers and the Teams total and the combined total.

On 26 Apr 2018 at 01:40 GMT Linda Barnett wrote:

I think you can I will check on it. As I told Holly down below I think you can if you use the link that is on this team free space page that says under quick link heading ERROR LIST: (DBE Errorlist TN)

On 25 Apr 2018 at 00:22 GMT Linda Barnett wrote:

Holly I will check on that and let everyone know. I think you can if you use the link that is on this team free space page that says under quick link heading ERROR LIST: (DBE Errorlist TN)

On 25 Apr 2018 at 00:19 GMT Linda Barnett wrote:

Hi everyone I saw this and thought you'll would like to see this.

Wow, WikiTreers!

What an amazing weekend! Thank you so much to everyone who participated in our 2018 Spring Clean-a-Thon. It's so great to see the community come together and have so much fun cleaning up our tree.

This year we handled 152,253 suggestions nearly doubling last year's total of 80,757. So impressive!

Here are some other stats from our event:

Top 5 Teams: •Team Roses: 43,393 (!) •Southern Super Sweepers: 12,517 •Team GB Gen: 11,156 •Kiwi Crew: 9,031 •Tidying Tornadoes: 8,009

Top 5 Participants •Lucy Lavelle: 7,652 •NJ Penny: 7,652 (yes, a tie for 1st!) •Charlotte Shockey: 7,515 •Emma MacBeath: 5,975 •Deb Love: 4,000

Top 5 Suggestions Handled: •USA Too Early in Birth Location: 25,528 •Empty Profile: 14,695 •USA Too Early in Death Location: 14,324 •Separators in First Name: 9,161 •Missing <references /> Tag: 7,590

Top Participant Per Suggestion Group: •Dates: Bobbie Bonner with 1,076 •Relationships: Sandy Patak with 396 •Names: Emma McBeth with 5,836 •Gender: Sandy Patak with 231 •Locations: Lucy Lavelle with 7, 297 •Privacy: Eowyn Langholf with 235 •Biography: NJ Penny with 3,064 •Templates: Aleš Trtnik with 688 •WikiData: Stephen McCallum with 101 •FindAGrave: Chet Snow with 805

26 teams participated and 24 of them broke 1,000! We had 385 members registered but 475 participated in some way. Members who weren't registered on a specific team handled 3,411. 47 individual participants broke 1,000!


Thanks again to everyone who participated. Can't wait to see what happens next year!

more comments