Project: Data Doctors

Categories: Profile Improvement Project | Functional Projects | Needs Profiles Created | DBE Error


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

This page is part of the Data Doctors Project.
 
Latest report: October 13th 2019 and the Spreadsheet.
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


Are you interested in the Data Doctors Project?data_doctor.gif

Contents

Mission

The mission of this project is to help WikiTree members create more accurate profiles which equates to better overall genealogy. Good genealogy is based on sources, so all changes should be sourced.

If we have sources with different facts then we need to add our analysis so that other WikiTree users can understand our reasoning. This is usually done in a Research Notes section.

Some suggestions are classified as errors, e.g. a mother can’t be born after a child. Other errors are conflicts between a WikiTree profile and another source. We need to resolve the conflict and correlate the facts/sources.

Never hesitate to ask in G2G. WikiTree is a worldwide genealogy community and we all have our special knowledge.

Goals

The goal of this project is to make members aware of and to correct ERRORS, review WARNINGS and investigate HINTS in the WikiTree database.

Most errors are the result of typos or imports of GEDCOMs. Also, beginners can make mistakes that are not easily seen.

Warnings are produced by uncommon data. It may be a typo or it may be unique information.

Hints are results of inconsistencies in linking to external databases. It can be the result of a typo, an error in what we have linked to the profile, or an error in the external database and needs investigating.

How to Join

Leader:

Project Coordinators:

Here you can see tag followers and badge holders.

If you would like to be involved in the Data Doctors Project please:

  • 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.
  • Add DATA_DOCTORS to your list of followed tags. That way you'll see discussions in your G2G Feed.
  • You will be also invited to the Data Doctors Google Group where most of the discussions among Data Doctors take place.

Code of Conduct for Data Doctor Work

  • If you are working on a particular suggestion from the weekly Suggestion Report, add a note on the latest report page so no one else will also look at the same list for that week.
  • Click the status button from the suggestion list to see if a suggestion has already been corrected.
  • If no previous status has been marked, look at the profile for any previous comments that other Data Doctors may have already left so you do not leave a duplicate message. An exception to this is if you have new information (such as a new source) that would help the profile manager to better edit an error.
  • Do not remove information from a profile. In most cases, information is simply moved to the correct field or to the biography.
  • Refrain from editing merged profile biography sections beyond rearranging merged biographical text and/or deleting duplicate biography data.
  • Use their style, not yours. Leave a written biography as is if you are not the Profile Manager. See above.
  • If you do make changes, such as changing an unknown birth location to a known place, make sure to add the source to the biography that validates the change.
  • Make location changes only if you are very familiar with the area AND if you have and are adding a source that reflects the change.
  • When suggestions are corrected, always leave a comment on the Suggestion Status page for anyone who may come after you. Remember to click save.
  • Please write a short "change comment" in the Explain Your Changes box (right above the profile’s Save button) for each change you make including "Data Doctor". An example might be: “Data Doctor - Suggestion 712- Number in Prefix: Edited number in first name-”
    Try not to use the word “remove” or anything similar. This upsets profile managers. Although not always possible, try to include all the changes you made in the comment, leaving a separate comment for each suggestion in the recommended format.
  • When advising another member on correcting errors, be clear and friendly. Make suggestions not demands. Errors happen to everyone! Word your messages in such a way to make the profile managers feel empowered rather than as if they are being sent to the naughty corner.
  • On open profiles, you do not need to contact the profile managers for every suggestion correction. The change log (under each profile’s “Changes” tab) will show every change that has been made. The exception to this is if you plan to make a major change based on primary sources. Then it is a courtesy to contact the profile manager through a private message before making any changes.

Data Doctors Project Video Tutorials

Data Doctors Project Video Collection

In early 2019, topic and individual video tutorials went into production. This is a long-term task and we hope to have all videos completed by mid-2020.

Data Doctor Project Productions is thrilled to have our own Karen Hoy as our creative Cinematographer, Director, and Producer, and taking on the roles of Executive Producer and Technical Consultant is our esteemed Team Leader, Aleš Trtnik.

The Grand Opening was on 14 April 2019 and announced in G2G (See the Now Showing! section below).

Friday Features - Announcements made every Friday in G2G and Data Doctors Google Group of theatre openings and new releases for the week.

These are links for pages and videos to bookmark:


Watch for announcements every Friday in G2G and the Data Doctors Google Group for coming attractions and new releases! Posts are reprinted below.

Now Showing!

20 September 2019 - Data Doctors Project Productions Announces the Find A Grave Theatre is complete!
13 September 2019 - Data Doctors Project Productions: Mr E Returns!!
23 August 2019 - Data Doctors Productions Friday Features Release
16 August 2019 - Data Doctors Project Productions Find A Grave Genre Grows Again!
09 August 2019 - Data Doctors Project Productions Announcer This Week: Mr E!
02 August 2019 - Data Doctors Project Productions New Friday Feature
26 July 2019 - Data Doctors Project Productions Releases More Grave and Gender Solutions
19 July 2019 - The Data Doctors Project Productions announces the opening of the 9th theatre with a new feature!
12 July 2019 - Data Doctors Project Productions Reveals All!! Mr. E Siting Not A Mistake!!!! - 6 New Videos This Week!
05 July 2019 - Data Doctors Project Productions Friday Features: A New Topic Film & Theatre Grand Opening!
28 June 2019 - Data Doctors Productions Brings Back Friday Features!
21 June 2019 - Data Doctors Project Productions Completes Another Theatre!
14 June 2019 - Data Doctors Project Productions Biography Genre Grows Again!
07 June 2019 - Data Doctors Project Productions Multiplex Theatres are 75% Complete!
31 May 2019 - Data Doctors Project Productions Continues to Grow with New Theatres, Features & TV Station!!
29 May 2019 - WikiTree TV Sneak Peek
24 May 2019 - Data Doctors Project Productions Epic Release
17 May 2019 - Data Doctors Project Productions Opens Another New Theatre
10 May 2019 - Data Doctors Project Productions Expanding Biography Theatre
03 May 2019 - Data Doctors Project Friday Features
25 April 2019 - Early Edition: Just in Time for Clean-A-Thon!
19 April 2019 - Data Doctors Project Productions Announces New Releases
14 April 2019 Grand Opening - Data Doctors Project Proudly Presents...

How to Get Started

  1. Read all the project documentation. If you have any questions, please contact one of the Project Coordinators listed above.
  2. Check and correct Suggestions on your managed profiles to learn the process. (My WikiTree tab and scroll to Suggestions tab or Click here).
  3. Check and correct Suggestions on your extended family tree to continue learning the process. (On starting profile Second menu (at top of page) and scroll to Suggestions tab or Click here).
  4. Check and correct suggestions for profiles on your watchlist (My WikiTree / Watchlist or Click here). It redirects you to WikiTree+ where you log in with WikiTree credentials to use).
  5. Correct Suggestions by Type. Check out the latest suggestions list to find suggestion types you can correct. Check for videos and read the Suggestion Help Page information to familiarize yourself with specifics and then start correcting. *Note: If you are working on the complete list of a suggestion in a specific era add a comment on the latest suggestions page so that others will know that suggestion has already been checked. (October 13th 2019)
Next Steps:
These suggested steps help in cleaning up profiles that benefit the entire one-world tree.
  • Use prepared Suggestion Reports by country, US states, projects,... (Custom lists)
  • Correct Suggestions by Location (your town, region, country ...) (Click here).
  • Correct Suggestions by Names (first or last names) (From last name page on WikiTree click Suggestion Report (last name page or define custom search Click here).
Data Doctors need to become familiar with all Suggestion Types since there can be more than one suggestion on the profile and each gives you a clue to finding the main issue and then all the suggestions can be corrected at once.
  • Choose to specialize in one Suggestion Type.
  • Participate in Weekly Challenges. Note: you must be familiar with the Suggestion Type and location or time period (or other criteria related to the topic suggestion) of the Weekly Challenge and have been a Data Doctor for at least 3 months before participating in any challenge . The exception is for Clean_A-Thons in any year beginning 26 April 2019.
  • Any questions on the steps can be addressed to one of the Project Coordinators listed above. ALL questions regarding FindAGrave suggestions should be addressed to Lance Martin.

Special Situations

  • England Project Orphan Trail Profiles: Whether a Data Doctor is working on a particular Suggestion or in any Challenge, the following profiles should never be worked on if [1] is an England-based profile of any location or time period AND [2] a graphic similar to this appears on the profile page:


  • Project Protected Profiles: These profiles will have a box at the top right that says PROJECT PROTECTED and contain this image. They might have a green privacy level regardless of the time period. Data Doctors may edit the profile for minor errors such as USA too early suggestion or typos. For more substantive edits, please leave a comment on the page of what you want to change or add along with source information. This alerts the manager(s) of the profile, Project Coordinators and Leaders of changes needed.

    If there are questions about doing work on a PPP, leave the question as a public comment for the project to review and advise next steps.
    Note: if the profile is PPP and OPEN, make necessary changes and be sure to leave a comment of your changes in both the edit box and Public Comments.
  • Pre-1700 Profiles
Pre-1700 means 1500-1699. You must be Pre-1700 certified to edit these profiles. One of the requirements to gain the Data Doctors' badge is to take the self-administered Pre-1700 certification in order to work on suggestions in this time period. If you are not interested in working on profiles in this time period, that is OK. Just leave these suggestions to Data Doctors who desire to work on profiles in this time period.
  • Pre-1500 Profiles
Pre-1500 means all profiles before this century. You must be Pre-1500 certified to edit these profiles. However, this certification takes more work to acquire.
If you have a special interest in a particular profile (It is in your family tree for instance) and you feel a suggestion needs attention, you may post in G2G asking for a Pre-1500 certified member to correct the suggestion on your behalf. 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 DATA_DOCTORS, so we know the origin of corrections. Those with Pre-1500 badges will work these items. Otherwise, leave these suggestions to Data Doctors who are Pre-1500 certified.
  • Private and public profiles (Level Green to Red)
Data Doctors cannot directly correct suggestions on private profiles. However, there are a few steps that can be taken to improve the health of a profile.
  • If the profile should be open due to the person’s age (anyone born 150 years ago or died 100 years ago):
  1. Go to the second tab at the top right of the profile page where it shows the profile’s WikiTree ID.
  2. In the drop-down menu, go down to the choice that says, “Open Profile Request.” You will be asked to confirm the age is old enough to require it being opened.
  3. Leave a short note of evidence (such as birth date is 1830 or the child was born in 1797) that will help the administrator make a faster decision to open the profile.
  4. You will receive an email when the profile has been opened. Go back to the profile and correct that suggestion.
  5. Leave a comment on the Suggestion Status Page of what you did. This will alert others after you that issue is resolved, and a second request is not needed.
  6. Be sure to click on Update Status to save your work.

How to Get Help

  • If the question is about a specific suggestion, check the Description of Suggestions section below that link to the Suggestion Help Page for that suggestion.
  • Check the Data Doctors Project Video Collection described above for a suggestion-related How-To video tutorial. The "theatre" is also linked under the Suggestion Type Group Headings below as available.
  • Search for related subjects in [http://www.wikitree.com/g2g/tag/data_doctors G2G forum - DATA_DOCTORS.
  • Ask in the G2G forum and add the DATA_DOCTORS tag.
  • Contact one of the Project Coordinators for individual help.

Weekly Challenge

Each week a theme is selected for the Weekly Challenge. Click here to join our current challenge! Data Doctors: Be sure you have met the How to Get Started criteria first.

Templates

The usage of this template (template {{db_errors}}.) was never approved and should not be used. There are better ways to do the same. The template will be deleted in the future.

Description of Suggestions

Videos on Suggestions Group (Genre) Topics and Individual video tutorials (How-Tos) are in production with first releases now showing.

Status

This section is being revised so stay tuned for improvements.

Setting the status of a suggestion is described on Suggestion Status Help page and individual Suggestion Help Pages.

The following are short descriptions of the suggestions and links to each suggestion's help page for a full description, methods, and hints on how to correct the suggestion.

NOTE: All Suggestion Help Pages are under revision and once updated will redirect to the revised page "behind the scenes". Watch for the new look coming soon and to be announced.

Date Suggestions

Videos are available! Please see: Date Genre Theatre

  • 101 Birth in future : Birth date is in the future. The most common cause is a typo in the birth date.
  • 102 Death in future: Death date is in the future. The most common cause is a typo in the death date.
  • 103 Death before birth: Death date is prior to the birth date. Common causes are a typo in one of the dates, or the birth and death dates have been reversed. This error is only checked on profiles with both birth and death dates entered.
  • 104 Too old: The person's age at death is over 110 years. May be caused by a typo in the birth or death dates or by incorrect birth or death information. This error is only checked on profiles with both birth and death dates entered.
  • 111 Died too young to be parent: This person was under ten years old at death, but has children attached to the profile.
  • 113 Duplicate relative: This person has the same relative appearing as two or more relatives on the their profile.
  • 131 No Dates - No Dates on relatives - Open - Unknown Status: Both Birth and death dates are missing on this profile. There are no data on this profile or any attached relation profiles to estimate birth or death dates.
  • 132 No Dates - No Dates on relatives - Open - Status Died: The profile information indicates this person is deceased, but both birth and death dates are missing. There are no data on this profile or any attached relation profiles to estimate birth or death dates.
  • 133 No Dates - Dates on relatives - Open - Unknown Status: Both Birth and death dates are missing on this profile. There may be sufficient data on attached relation profiles to estimate a birth or death date.
  • 134 No Dates - Dates on relatives - Open - Status Died: This person is marked as dead, but all birth and death information are missing on this profile. There may be sufficient data on attached relation profiles to estimate a birth or death date.
  • 205 Father is too young or not born: The father was either not born or under ten years old at this person's birth. Either a birth date or the relationship is incorrect.
  • 206 Father is too old: The father was either over 99 years old or deceased at the birth of this person. Either a birth or death date is incorrect, or the reationship is incorrect.
  • 210 Father was dead before birth: This person's father died before their birth. In most cases the person's birth date, the father's death date, or the relationship is wrong.
  • 301 Mother is self: This person is their own mother. The relationship should be deleted or replaced with the correct mother.
  • 305 Mother is too young or not born: The mother was either not born or under ten years old at this person's birth. Either a birth date or the relationship is incorrect.
  • 306 Mother is too old: This person's mother was either over 99 years old or deceased at the birth of this person. Either a birth or death date is incorrect, or the relationship is incorrect.
  • 307 Mother is also a child:: This person is their own mother. The parent-child relationship should be deleted or replaced with correct one.
  • 310 Mother was dead before birth: This person's mother died before their birth. The person's birth date, the mother's death date, or the relationship is wrong.
  • 401 Spouse is self: The person is married to themself. The marriage relationship should be deleted and, if known, replaced with the correct one.
  • 404 Marriage before birth: The person has a marriage date prior to their birth date. Either,or both the birth or marriage dates are wrong, or the relationship is incorrect. The correct marriage, or birth date should be entered if known. If the relationship is wrong it should be deleted or the correct relationship should be entered.
  • 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 has a marriage date after their death date. Either,or both the death or marriage dates are wrong, or the relationship is incorrect. The correct marriage, or death date should be entered if known. If the relationship is wrong it should be deleted or the correct relationship should be entered.
  • 407 Lived too long after marriage: The person lived over 115 years while married. Either the death or marriage dates are wrong or the relationship is incorrect. If the correct relationship, death or marriage date is known it should be entered.
  • 410 Marriage in future: Marriage date is in the future. The most common cause is a typo in the birth date.
  • 411 Marriage End Date in future: The marriage end date is in the furure. 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. One or both dates may be incorrect.
  • 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 end date can be determined, fix it.
  • 415 Marriage End Date too late: The difference between the person's birth date and their marriage end date is over 115 years.
  • 416 Marriage End Date after Death Date: The marriage end date is after the person's end date. One of the marriage end date or death date is incorrect.
  • 417 Death Date too long after Marriage End Date: The person's death and marriage end dates indicate that they lived over 115 years after the marriage end. One of these dates is incorrect.


Relationship Suggestions

  • 105 Duplicate sibling: Another profile exists with the same full name, parents, birth and death dates. Unless these two profiles are stillborn unnamed twins they are probably duplicates and should be merged. 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.
  • 106 Duplicates between global tree and unconnected: An unconnected profile exists with the same full name, and birth and death dates as this profile. It is probably a duplicate and the two profiles should be merged. (Orphan profiles are ignored) 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 (must be done for both profiles.
  • 112 Person is father and mother: This person is father to some children and mother to others. Parentage should be corrected as appropriate.
  • 113 Duplicate in relatives: This person has a relative appearing as two or more separate entries on the their profile.
  • 201 Father is self: This person is their own father. The relationship should be deleted or replaced with the correct father.
  • 202 Parents are same: This person's mother and father are the same person. The incorrect relationship should be deleted or replaced with correct one.
  • 207 Father is also a child: This person is their own father. The parent-child relationship 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. The relationship should be deleted or replaced with correct one.
  • 209 Father is also a sibling: This person's father is also their sibling. If there is no 201 error on this profile, the problem is in mother's children. Mother's children should be corrected.
  • 211 Duplicate sibling by Father: There is a profile with the same full name, birth and death dates and same father, but the mother is different. These two profiles may be duplicates, if so, they should be merged.
  • 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.
  • 308 Mother is also a spouse: This person's mother is also his wife. This is rarely true. The relationship should be deleted or replaced with the correct one.
  • 309 Mother is also a sibling: This person's mother is also their sibling. If there is no 301 error on this profile, the problem is in father's children. Father's children should be corrected.
  • 311 Duplicate sibling by Mother: There is a profile with the same full name, birth and death dates and same mother, but the father is different. These two profiles may be duplicates, if so, they should be merged.
  • 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.
  • 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.
  • 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.
  • 901 Unconnected empty public profile: This public profile has no relations: parents, children and marriage and no birth and death date or location data. This error is Connectors Project related is not usually part of the Data Doctors work.
  • 902 Unconnected empty open profile: This open profile has no relations: parents, children and marriage and no birth and death date or location data. This error is Connectors Project related is not usually part of the Data Doctors work.

Name Suggestions

Videos are available! Please see: Name Genre Theatre

Gender Suggestions

Videos are available! Please see: Gender Genre Theatre

  • 203 Father is Female: The gender of the father of this person is female. Correct the gender of the father or replace the current father with the correct one. (watch for a possible reversal of mother and father)
  • 204 Father has no Gender: This person's father doesn't have a gender. Set father's gender.
  • 303 Mother is Male: The gender of the mother of this person is male. Correct the gender of the mother or replace the current mother with the correct one. (watch for a possible reversal of mother and father)
  • 304 Mother has no Gender: This person's mother doesn't have a gender. Set mother's gender.
  • 402 Unknown gender of spouse: The person's spouse does not have their gender set. 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.
  • 501 Wrong male gender: Person with this name is most likely male, but the profile is marked as female. Either gender or name is probably incorrect. Correct gender or name.
  • 502 Missing male gender: Person with this name is most likely male, but no gender is checked on the profile . Enter the correct gender.
  • 503 Missing probably male gender: Person with this name should statistically be male, but is defined as female. Gender may be wrong or name may be incorrect.
  • 504 Missing probably male gender: Person with this name should statistically be male, but no gender has been set.
  • 505 Wrong female gender: Person with this name is most likely female, but the profile is marked as male. Either gender or name is probably incorrect. Correct gender or name.
  • 506 Missing female gender: Person with this name is most likely female, but no gender is checked on the profile . Enter the correct gender.
  • 507 Probably wrong female gender: Person with this name should statistically be female, but is defined as male. Gender may be wrong or name may be incorrect.
  • 508 Missing probably female gender: Person with this name should statistically be female, but no gender has been set.==>
  • 509 Missing gender: Person has no gender set and gender cannot be derived from name.
  • 510 Unique name without gender: Person has a unique name (only appears once in the database) and no gender defined. Gender cannot be derived from name.

Location Suggestions

Videos are available! Please see: Location Genre Theatre

  • 601 Wrong word in birth location: The birth location entered is not a valid geographic location.
  • 602 Y birth location: The field Birth place is filled with "Y" or "Y/" or "Y;" or "Yes", or begins with "Y/" or "Yes". These are invalid locations.
  • 603 USA too early in birth location: The country of birth is entered as the United States of America (USA), however the birth date is prior to 1776. Location fields should use the name that existed when the event took place.
  • 604 Birth location too short: The birth location field should contain a full description of the location all applicable geopolitical designations up to and including the country. Short forms for States and Countries should not be used.
  • 605 Number in birth location: There is only a number in the birth location field. The birth location field should contain a full description of the location all applicable geopolitical designations up to and including the country.
  • 606 Bogus birth location: Location is probably not correct.
  • 607 Misspelled word in birth location: One of the words in the birth location field is misspelled.
  • 608 Misspelled country in birth location: The last word in the birth location field, if it is a country, is misspelled.
  • 609 Wrong character in birth location: There is a character in the birth location field that is normally not used in describing a geopolitical location.
  • 610 Birth location in uppercase: All characters in the birth location are in uppercase. Birth locations should be entered in title case (First letter of each word captialized except words such as "and" and "of".)
  • 611 Birth location in lowercase: All characters in the birth location are in lowercase. Birth locations should be entered in title case (First letter of each word captialized except words such as "and" and "of".)
  • 612 Location too early in birth location: The country in the birth location did not exist when the birth took place. The birth location should be the name of the location as it existed when the birth took place.
  • 613 () in birth location : Parentheses ( ) are used within the birth location name. Parentheses are not allowed in location fields.
  • 614 Birth location too long: The birth location is too long. This error generally occurs when extraneous information such as the street, or hospital name is entered into the birth location. Such information properly belongs in the biography.
  • 631 Wrong word in death location: The death location entered is not a valid geographic location.
  • 632 Y death location: The field Death Place is filled with "Y" or "Y/" or "Y;" or "Yes", or begins with "Y/" or "Yes". These are invalid locations.
  • 633 USA too early in death location: The country of death is entered as the United States of America (USA), however the death date is prior to 1776. Location fields should use the name that existed when the event took place.
  • 634 Death location to short: The death location field should contain a full description of the location all applicable geopolitical designations up to and including the country. Short forms for States and Countries should not be used.
  • 635 Number in death location: There is only a number in the death location field. The death location field should contain a full description of the location all applicable geopolitical designations up to and including the country.
  • 636 Bogus death location: Location is probably not correct.
  • 637 Misspelled word in death location: One of the words in the death location field is misspelled.
  • 638 Misspelled country in death location: The last word in the death location field, if it is a country, is misspelled.
  • 639 Wrong character in death location: There is a character in the death location field that is normally not used in describing a geopolitical location.
  • 640 Death location in uppercase: All characters in the death location are in uppercase. Death locations should be entered in title case (First letter of each word captialized except words such as "and" and "of".)
  • 641 Death location in lowercase: All characters in the death location are in lowercase. Death locations should be entered in title case (First letter of each word captialized except words such as "and" and "of".)
  • 642 Location too early in death location: The country in the death location did not exist when the death took place. The death location should be the name of the location as it existed when the death took place.
  • 643 () in death location: Parentheses ( ) are used within the death location name. Parentheses are not allowed in location fields.
  • 644 Death location too long: The death location is too long. This error generally occurs when extraneous information such as the street, or hospital name is entered into the death location. Such information properly belongs in the biography.
  • 661 Wrong word in marriage location: The marriage location entered is not a valid geographic location.
  • 662 Y marriage location: The field Marriage Place is filled with "Y" or "Y/" or "Y;" or "Yes", or begins with "Y/" or "Yes". These are invalid locations.
  • 663 USA too early in marriage location: The country of marriage is entered as the United States of America (USA), however the marriage date is prior to 1776. Location fields should use the name that existed when the event took place.
  • 664 Marriage location too short: The marriage location field should contain a full description of the location all applicable geopolitical designations up to and including the country. Short forms for States and Countries should not be used.
  • 665 Number in marriage location: There is only a number in the marriage location field. The marriage location field should contain a full description of the location all applicable geopolitical designations up to and including the country.
  • 666 Bogus marriage location: Location is probably not correct.
  • 667 Misspelled word in marriage location: One of the words in the marriage location field is misspelled.
  • 668 Misspelled country in marriage location: The last word in the marriage location field, if it is a country, is misspelled.
  • 669 Wrong character in marriage location: There is a character in the marriage location field that is normally not used in describing a geopolitical location.
  • 670 Marriage location in uppercase: All characters in the marriage location are in uppercase. Marriage locations should be entered in title case (First letter of each word captialized except words such as "and" and "of".)
  • 671 Marriage location in lowercase: All characters in the marriage location are in lowercase. Marriage locations should be entered in title case (First letter of each word captialized except words such as "and" and "of".)
  • 672 Location too early in marriage location: The country in the marriage location did not exist when the marriage took place. The marriage location should be the name of the location as it existed when the marriage took place.
  • 673 () in marriage location: Parentheses ( ) are used within the marriage location name. Parentheses are not allowed in location fields.
  • 674 Marriage location too long: The marriage location is too long. This error generally occurs when extraneous information such as the street, or hospital name is entered into the marriage location. Such information properly belongs in the biography.

Privacy Suggestions

Videos are available! Please see: Privacy Genre Theatre

Biography Suggestions

Complete Biography Video Collection












  • 801 Big biography: The profile's biography is quite large. A big biography isn't necessarily an error. It is just a warning that the biography may be overly wordy.
  • 802 Empty biography: The profile's biography is empty. Since the biography contains the sources for the profile, this indicates that the profile is unsourced.
  • 803 Almost empty biography: The character count in the biography of this profile is very small. Since the biography contains the sources for the profile, a short biography may be indicative of an unsourced profile
  • 811 Uncleaned profile after merge: This profile is the result has been merged, however the biography has not been cleaned up and reorganized. Each biography should have one set of contents and one sources section.
  • 821 Heading starts with blank: A caption or a heading in the biography of this profile starts with a blank space. Wikitree biography syntax defines that a new line starting with a "=" is a Caption or Heading. Caption and headings must be left justified and start with a "=".
  • 822 Heading doesn't end with =: A caption or a heading in the biography of this profile does not end with a "=". Wikitree biography syntax defines that a caption or heading must start with one or more "="s and end with the same number of "="s.
  • 823 Heading doesn't start with =: A caption or a heading in the biography of this profile does not start with the same number of "="s as the end set of "="s. Wikitree biography syntax defines that a caption or heading must start with one or more "="s and end with the same number of "="s.
  • 824 Heading different number of =: A caption or a heading in the biography of this profile does not start with the same number of "="s as the end set of "="s. Wikitree biography syntax defines that a caption or heading must start with one or more "="s and end with the same number of "="s.
  • 825 Use separator line ----: The biography in this profile uses four or more "=" to simulate a separator line. Wikitree biography syntax uses four minuses ("-") on a line to make a separator line. Separator lines should not be built using "="s since this can cause the line to be rendered as a caption or heading.
  • 831 Multiple duplicated lines: The biography in this profile has one or more cases of repeated lines or paragraphs, possibly the result of merging or data imports. Duplicate lines and paragraphs should be deleted.
  • 835 Local file reference: The biography in this profile has references to files contained on the author, editor or creators's local computer. These files are not visible on the Internet. See the 835 help page for this error for an example.
  • 851 GEDCOM uncleaned Interpret date: The biography of this profile contains a warning from the GEDCOM import program that a date in the GEDCOM import could not be interpreted. If the correct date is in the indicated field, this warning may be deleted.
  • 852 GEDCOM uncleaned Parse Lastname: The biography of this profile contains a warning from the GEDCOM import program that the last name in the GEDCOM import could not be parsed. If the correct name is in the last name field, this warning may be deleted.

References Tag Suggestions

Complete Reference Tags Video Collection












Template Suggestions

Videos are available! Please see: Template Genre Theatre

  • 841 Template doesn't start with double {: A template in the biography of the profile does not start with double curly brackets "{{". All Wikitree templates must start with double curly brackets. See the Template help page for more details on the use of templates.
  • 842 Template doesn't end with double }: A template in the biography of the profile does not end with double curley brackets "{{". All Wikitree templates must end with double curly brackets. See the Template help page for more details on the use of templates.
  • 843 Missing template (spelling): There is an error in a template name in the biography of the profile. It could be a spelling mistake, a template that no loinger exists or a template that is not yet created.
  • 844 Out of use template: A template in the biography of this profile is being used incorrectly. This may mean that the template is a base template and is not to be used directly, the template is no longer active, or the template has been replaced.
  • DBE_845 Direct usage of base templates: The biography in the profile contains a base project template such as {{Project Box|etc}} or {{Sticker|etc}}. Base templates should not be used and should be replaced with the appropriate template, for instance {{Roll of Honor|etc...}}. See the Template help page for the proper use of templates.
  • DBE_846 Died before template time frame: The template used in the biography of the profile has a time constraint. The death date on the profile is prior the template date range. Please see the appropriate template help page for details.
  • DBE_847 Born after template time frame: The template used in the biography of the profile has a time constraint. The birth date on the profile is after the template date range. Please see the appropriate template help page for details.
  • DBE_848 Error in template parameters: A template in the biography of the profile has one or more unacceptable values. Please see the help page for the appropriate template for correct values.

Wikidata Suggestions

Videos are available! Please see: Wikidata Suggestions Theatre

Some WikiTree profiles are matched with a profile in Wikidata. See Wikidata. These suggestions point to the differences between the Wikitree and Wikidata items. When working on these suggestions, please keep in mind that Wikidata is not a source. Research all differences to determine which entry contains the most accurate data.

FindaGrave Suggestions

Complete FindAGrave Video Collection












Some WikiTree profiles are matched with a memorial on Find-A-Grave.com. These errors point to differences between the Wikitree profile and the Find-A-Grave.com memorial. When working on these errors, please keep in mind that Find-A-Grave is not a source. All differences should be researched to determine which entry contains the most accurate data.

Category Suggestions

These are new suggestions and pages are under construction.

  • 885 Using Top Level category
  • 886 Died before category time frame
  • 887 Born after category time frame

Links

  • Page with latest errors October 13th 2019 2019-10-13
  • See WikiTree+. for custom reports and statistics.

For older Suggestion Lists see:

Detail Suggestion Lists no longer available. Just totals:

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. Except 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 08:01, 5 October 2019. This page has been accessed 61,389 times.