Project: Data Doctors

Categories: Profile Improvement Project | Data Doctors Project

This page is part of the Data Doctors Project.
 
Latest report: August 9th 2020 and the Spreadsheet.
Data Doctors Challenge: Reference_Tags_XVII 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
This project improves data in the WikiTree database by working on suggestions. It is a subproject of the Profile Improvement Project.

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 that equate to better genealogy overall. Good genealogy is based on sources, so all changes should be sourced.

For sources with different facts, we need to add our analysis so other WikiTree members can understand our reasoning. This is usually done in an optional 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.

Remember you can ask questions anytime in G2G. WikiTree is a worldwide genealogy community and we each participate with our own special knowledge and skills.

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

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

  • data_doctor.gif Answer this post in G2G and the badge will be awarded to you. Be sure you meet the requirements listed in the post. 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. Use the comment: "I am a member of the project."
  • 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". Use this format, for example: “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.

How to Get Started

First Steps

  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. (August 9th 2020)

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

Establish Your Data Doctor "Practice"

Data Doctors need to become familiar with all Suggestion Groups 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 Group.
  • Participate in the Weekly Challenges. Note: you must be familiar with the Suggestion and location and time period (or other criteria related to the topic suggestion) of the Weekly Challenge.
  • Any questions on the steps can be addressed to one of the Project Coordinators listed above.

Special Situations

  • There are times when profiles should not be worked on due to other projects' requests, project protected profiles, privacy settings, or certification issues.

England Project Orphan Trail Profiles

  • 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] it is an England-based profile of any location or time period AND [2] a graphic similar to this appears on the profile page:

Scotland Project Tartan Trail Profiles

  • Scotland Project Tartan 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] the profile is a Scotland-based profile of any location or time period AND [2] a graphic similar to either of these appear on the profile page:

Project Protected Profiles (PPP)

  • 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 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. While Pre-1700 Certification is not required to be a Data Doctor, it is recommended that you 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 those profiles.

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 tags: Pre-1500 and Data Doctors, so we know the origin of the corrections request and a Pre-1500-badged member will work on these, or you can leave these suggestions for Data Doctors who specialize in these suggestions.

Private and Public Profiles

Data Doctors cannot directly correct suggestions on private profiles. (These are Privacy Settings Green to Red). 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. See Suggestions Status Page below.

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.

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.
  • If you are a Data Doctor and a member of the Data Doctors Google Group (DDGG), you may post a question there. Include the Suggestion ### and a link to any profile it may concern.
  • Search for related subjects in the G2G forum searching for the DATA_DOCTORS tag.
  • You can ask questions in the G2G forum.
Please add the DATA_DOCTORS and Suggestion ### tags. (Create the tags by typing in data doctors, and Suggestion ### in the "Surnames/Tags box using underscores for spaces, and separate tags by commas, e.g. data_doctors, Suggestion_123).
If you need help with Pre-1500 era profiles, add the Pre-1500 to the question in G2G along with the tags above.
  • Check the Video Tutorials below.
  • Contact one of the Project Coordinators for individual help.

Video Tutorials

Videos Page Link
Guide, Content & More
Data Doctors Project Video Collection
The video collection library including added content and admission to the genre theatres for videos on WikiTree topics, Suggestion Group/Genre Topics, WikiTree+, and Suggestion Individual Video Tutorials (How-Tos).
WikiTree TV
Many videos on topics, instructions, the "Thons", projects and live chats created by the WikiTree Team, Leaders, and Members are available as well as 3rd party videos about WikiTree.

WikiTree TV is the program guide and links to current videos.
WikiTree Live Casts:
Aleš Trtnik discusses
WikiTree Plus+

Running Time: 56:48
It is WikiTree+, Mr E.
Play the It is WikiTree+, Mr E..

Data Doctors WikiTree+ Suggestions
Play the Data Doctors WikiTree+ Suggestions.

WikiTree+ is an independent service offered for free by Aleš. It is not a part of WikiTree website and uses data that is publicly available to everyone. WikiTree+ uses deep data analysis to find possible errors and opportunities for further research.

WikiTree Plus Info & Help
WikiTree+ Report Site
WikiTree+ Chrome Extension


Weekly Challenge & Annual Clean-a-Thon

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.

  • Data Doctors Project members may participate based on the suggestions' difficulty rating and their experience level. Check the Difficulty Rating of the suggestions included in the challenge in the tables below. Be sure to work in a timeframe and location you are familiar with.
  • Participants in the annual Clean-A-Thon may also find the ratings helpful. For participants' instructions, see the Spring Clean-a-Thon Tutorial.

Suggestions Groups - Descriptions, Difficulty Ratings and More

This section is revised and contains new content! (edited: 30 July 2020)

This section has been revised to show new procedures and reorganized information.

  • All WikiTree members are encouraged to work on their own and managed profiles' suggestions.

Suggestions are organized by Group (for WikiTree Suggestion Pages) and Genre (for videos) with links to each Individual Suggestion Page.

Suggestions are issues that appear on profiles in WikiTree in the data fields and biography/sources sections.

They are:

  • Errors are incorrect entries as the result of typos or imports of GEDCOM that need to be corrected;
  • Hints are results of inconsistencies in linking to external databases, like Ancestry or others, caused by a typo, an incorrect link to the profile, or an issue that needs investigating; or
  • Warnings are produced by uncommon data due to a typo or unique information on profiles and need to be reviewed.

Suggestions Status Page

Tracking Work on Suggestions

Suggestions Status Page Example
(aka Status Report)

Note: The INFO column located on the Suggestion List and on the Suggestion Status Page gives hints of what to look for in the profile to resolve the suggestion.

  • Where to access Suggestion Lists, reports, and pages
  • What the lists, reports, and pages are,
  • What the Suggestion Status Page is and how to complete it,
  • Explanation of the Data Doctors Project Info Box,
  • WikiTree+, and
  • Suggestions Spreadsheet information.


Importance of Setting the Status

  • Setting the Status (on the Suggestions Status Page) is important for two reasons:
  1. The status determines how the suggestion is handled in the future by the tracking system which is updated every Tuesday for the previous week's changes; and
  2. The status must be set to get credit for work done for a Data Doctors Weekly Challenge and the annual Clean-A-Thon.
  • NOTE: Working on suggestions may not give you "instant gratification". The reports are generated in WikiTree Plus weekly on Tuesday mornings (although may be delayed during RootsTech and the "Thons") based on the work done in the previous week in WikiTree. You will get immediate gratification knwoing that by working on suggestions, that improve profiles and the one-world tree overall.

Difficulty Ratings & Experience Levels

There is a Difficulty Rating for each suggestion defined as:
  • Easy- very basic format issues caused by typos, punctuation, omissions, name or date errors. (Examples: Brackets, Typos in any field, Headings);
  • Intermediate - requires knowledge of WikiTree functions and proper formatting. (Examples: Inline citations, Sourcing, Template formatting); or
  • Advanced - requires multiple steps, research, and combines more than one intermediate function to resolve. (Examples: Merging, Clean up Profile after merges, duplicate sources, gedcom cleanup)
There are suggestions to work on at every experience level (you decide your own level). On any level, please work on profiles only in the location[s] and timeframe[s] you are comfortable with and qualified for (i.e. you are badged for Pre-1700 or Pre-1500 Certifications; live in and/or research specific location[s]).
  • Beginners - work on Easy suggestions,
  • Intermediate - work on Intermediate and Easy suggestions,
  • Advanced & Expert - work on suggestions of all levels.

For suggestions on your own suggestions report or managed profiles, you can work on any suggestions in your report checking for "Suggestions" on your My WikiTree.

Suggestion Groups - Suggestions Descriptions & Difficulty Ratings

The following are the groups/genre of suggestions with the suggestions' descriptions, difficulty ratings, and links to each suggestion page. The image in each Suggestion Group heading links to the video "theatre" page. The type [error, hint, warning, etc.] is given along with the page link and video link for individual suggestions.

Date Suggestions

Click on the image for the library of Suggestions Videos.


Suggestions Type, Descriptions, Page & Video Links
Difficulty Rating
101 Birth in future: Birth date is in the future. The most common cause is a typo in the birth date.
Type: Error
Easy
102 Death in future: Death date is in the future. The most common cause is a typo in the death date.
Type: Error
Easy
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.
Type: Error
Play the .
Intermediate
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.
Type: Error
Intermediate
111 Died too young to be parent: This person was under ten years old at death, but has children attached to the profile.
Type: Error
Intermediate
113 Duplicate relative: This person has the same relative appearing as two or more relatives on the their profile.
Type: Error
Advanced
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.
Type: Error
Play the .
Advanced
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.
Type: Warning
Advanced
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 the attached relation profiles to estimate a birth or death date.
Type: Error
Play the .
Advanced
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.
Type: Warning
Advanced
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.
Type: Error
Play the .
Intermediate
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 relationship is incorrect.
Type: Error
Advanced
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.
Type: Error
Intermediate
301 Mother is self: This person is their own mother. The relationship should be deleted or replaced with the correct mother.
Type: Error
Advanced
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.
Type: Error
Play the .
Intermediate
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.
Type: Error
Intermediate
307 Mother is also a child: This person is their own mother. The parent-child relationship should be deleted or replaced with the correct one.
Type: Error
Advanced
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.
Type: Error
Advanced
401 Spouse is self: The person is married to him/her self. The marriage relationship should be removed and, if known, replaced with the correct one.
Type: Error
Intermediate
404 Marriage before birth: The person has a marriage date prior to their birth date. Either the birth or marriage dates are wrong, or both, 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.
Type: Error
Intermediate
405 Marriage too long after birth: The person's marriage date is more than 115 years after their birth date.
Type: Error
Intermediate
406 Marriage after death: The person has a marriage date after their death date. Either the death or marriage dates are wrong, or both, 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.
Type: Error
Intermediate
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.
Type: Error
Advanced
410 Marriage in future: Marriage date is in the future. The most common cause is a typo in the birth date.
Type: Error
Intermediate
411 Marriage End Date in future: The marriage end date is in the future. Correct the date if it can be determined from a source.
Type: Error
Easy
412 Marriage End Date before Marriage Date: The marriage end date is before the marriage date. One or both dates may be incorrect.
Type: Error
Intermediate
413 Marriage too long: The difference between the marriage date and the marriage end date is more than 115 years.
Type: Error
Intermediate
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.
Type: Error
Intermediate
415 Marriage End Date too late: The difference between the person's birth date and their marriage end date is over 115 years.
Type: Error
Intermediate
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.
Type: Error
Intermediate
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.
Type: Error
Intermediate

Relationship Suggestions



Suggestion Type, Descriptions with Page Links
Difficulty Rating
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.
Type: Error
Intermediate
106 Duplicates between the 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 suggestion as a False Suggestion (this must be done for both profiles).
Type: Error
Intermediate
112 Person is father and mother: This person is father to some children and mother to others. Parentage should be corrected as appropriate.
Type: Error
Intermediate
113 Duplicate in relatives: This person has a relative appearing as two or more separate entries on their profile.
Type: Error
Advanced
201 Father is self: This person is their own father. The relationship should be deleted or replaced with the correct father.
Type: Error
Intermediate
202 Parents are same: This person's mother and father are the same person. The incorrect relationship should be deleted or replaced with the correct one.
Type: Error
Easy
207 Father is also a child: This person is their own father. The parent-child relationship should be deleted or replaced with the correct one.
Type: Error
Advanced
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 the correct one.
Type: Error
Intermediate
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 the mother's children. The mother's children should be corrected. Type: ErrorAdvanced
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.
Type: Error
Intermediate
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.
Type: Error
Advanced
308 Mother is also a spouse: This person's mother is also his wife. This is rarely true. The relationship should be removed or replaced with the correct spouse.
Type: Error
Intermediate
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 the father's children. Father's children should be corrected.
Type: Error
Intermediate
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, after careful comparison, they should be merged.
Type: Error
Intermediate
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.
Type: Error
Advanced
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.
Type: Error
Intermediate
409 Marriage to duplicate person: The person married more than one person with the same name. If the spouses are duplicates, merge them.
Type: Error
Intermediate
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.
Type: Error
Advanced
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.
Type: Error
Advanced
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.
Type: Error
Advanced

Name Suggestions

Click on the image for the library of Suggestions Videos.


Suggestions Type, Descriptions, Page & Video Links
Difficulty Rating
511 Replaced: This suggestion has been replaced by 7x7 suggestions (i.e. 717, 727, etc.) described below. The video applies to the replacement suggestions. Substitute the field referenced for those suggestions
Type:Warning
Play the .
Intermediate
711 Separator in prefix: There is a separator in the prefix field. Examples include "/", "-", ",", "(" and ")". Separators should normally not be used in the prefix field. See suggestion description for details.
Type:Error
Easy
712 Number in prefix: There is a number in the prefix field. Numbers should not normally be used in the prefix. See suggestion description for details.
Type:Error
Easy
713 Suffix in prefix: The contents of the prefix field should normally be in the suffix field. See suggestion description for details.
Type:Error
Intermediate
714 Wrong word in prefix: A word not normally used as a suffix is in the suffix field. See error description for details.
Type:Error
Intermediate
715 Wrong character in Prefix: In Prefix there is unusual character.
Type:Error
Intermediate
717 Unique name in Prefix: Prefix of this profile is unique on WikiTree. This could be a misspelled prefix.
Type:Warning
Play the .
Intermediate
721 Separator in first name: There is a separator in the first name field. Examples include "/", "-", ",", "(" and ")". Separators should normally not be used in the first name field. See error description for details.
Type:Error
Easy
722 Number in first name: There is a number in the first name field. Numbers should not normally be used in the first name. See error description for details.
Type:Error
Easy
723 Prefix in first name: The first name field contains a term normally considered a prefix. See error description for details.
Type:Warning
Easy
724 Wrong word in first name: A word not normally used as a name is in the first name field. See error description for details. Type:WarningIntermediate
725 Wrong character in first name: A character not normally used in a name is in the first name field. See error description for details. Type:WarningEasy
727 Unique name in First Name: First Name of this profile is unique on WikiTree. This could be a misspelled First Name.
Type:Warning
Play the .
Intermediate
731 Separator in preferred name: There is a separator in the preferred name field. Examples include "/", "-", ",", "(" and ")". Separators should normally not be used in the preferred name field. See error description for details.
Type:Error
Easy
732 Number in preferred name: There is a number in the preferred name field. Numbers should not normally be used in the preferred name. See error description for details.
Type:Error
Easy
733 Prefix in preferred name: The preferred name field contains a term normally considered a prefix. See error description for details. Type:WarningIntermediate
734 Wrong word in preferred name: A word not normally used as a name is in the preferred name field. See error description for details. Type:WarningIntermediate
735 Wrong character in preferred name: A character not normally used in a name is in the preferred name field. See error description for details. Type:WarningEasy
737 Unique name in Preferred Name: Preferred Name of this profile is unique on WikiTree. This could be a misspelled Preferred Name.
Type:Warning
Play the .
Intermediate
741 Separator in middle name: There is a separator in the middle name field. Examples include "/", "-", ",", "(" and ")". Separators should normally not be used in the middle name field. See error description for details.
Type:Error
Easy
742 Number in middle name: There is a number in the middle name field. Numbers should not normally be used in the middle name. See error description for details.
Type:Error'
Easy
743 Prefix in middle name: The middle name field contains a term normally considered a prefix. See suggestion description for details. Type:WarningEasy
744 Wrong word in middle name: A word not normally used as a name is in the middle name field. See error description for details. Type:WarningIntermediate
745 Wrong character in middle name: A character not normally used in a name is in the middle name field. See error description for details.
Type:Warning
Easy
747 Unique name in Middle Name: Middle name of this profile is unique on WikiTree. That could be an indication of misspelled Preferred Name.
Type:Warning
Play the .
Intermediate
749 Middle Name used in Netherlands: Middle Name is used for a person born in the Netherlands. The concept of a middle name is not recognized in the Netherlands.Intermediate
751 Separator in nicknames: There is a separator in the nicknames field. Examples include "/", "-", ",", "(" and ")". Separators should normally not be used in the nicknames field. See error description for details.
Type:Error'
Easy
752 Number in nicknames: There is a number in the nicknames field. Numbers should not normally be used in the nicknames. See error description for details.
Type:Warning
Easy
753 Prefix in nicknames: The nicknames field contains a term normally considered a prefix. See suggestion description for details.
Type:Warning
Easy
754 Wrong word in nicknames: A word not normally used as a name is in the nicknames field. See suggestion description for details.
Type:Warning
Intermediate
755 Wrong character in Nicknames: In Nicknames there is unusual character.
Type:Warning
Easy
757 Unique name in Nicknames: Suffix of this profile is unique on WikiTree. This could be a misspelled Suffix.
Type:Warning
Play the .
Intermediate
761 Separator in suffix: There is a separator in the suffix field. Examples include "/", "-", ",", "(" and ")". Separators should normally not be used in the suffix field. See error description for details.Type:ErrorIntermediate
762 Number in suffix: There is a number in the suffix field. Numbers should not normally be used in the suffix. See error description for details.
Type:Error
Intermediate
763 Prefix in suffix: The suffix field contains a term normally considered a prefix. See error description for details.
Type:Warning
Intermediate
764 Wrong word in suffix: A word not normally used as a name is in the suffix field. See error description for details.
Type:Error
Intermediate
765 Wrong character in suffix: In Suffix there is unusual character.
Type:Warning
Easy
767 Unique name in Suffix: Suffix of this profile is unique on WikiTree. This could be a misspelled Suffix.
Type:Warning
Play the .
Intermediate
771 Separator in last name at birth: There is a separator in the last name at birth field. Examples include "/", "-", ",", "(" and ")". Separators should normally not be used in the last name at birth field. See error description for details.
Type:Error
Advanced
772 Number in Last Name at Birth : The last name at birth contains a number.Intermediate
773 Prefix in last name at birth: The last name at birth field contains a term normally considered a prefix. See suggestion description for details. Type:WarningIntermediate
774 Wrong word in last name at birth: A word not normally used as a name is in the last name at birth field. See error description for details.
Type:Warning
Intermediate
775 Wrong character in last name at birth: A character not normally used in a name is in the last name at birth field. See error description for details.
Type:Warning
Intermediate
777 Unique name in Last Name at Birth: Last Name at Birth of this profile is unique on WikiTree. This could be a misspelled Last Name at Birth.
Type:Warning
Play the .
Intermediate
778 Period in Last Name at Birth: A period is found in the in Last name at Birth field which is not allowed by WikiTree guidelines. See suggestion description for details.
Type:Warning
Intermediate
781 Separator in current last name: There is a separator in the current last name field. Examples include "/", "-", ",", "(" and ")". Separators should normally not be used in the current last name field. See error description for details.
Type:Error
Intermediate
782 Number in current last name: In Current Last name numbers have been found that indicates an error.
Type:Error
Easy
783 Prefix in current last name: The current last name field contains a term normally considered a prefix. See error description for details. Type:WarningEasy
784 Wrong word in current last name: A word not normally used as a name is in the current last name field. See suggestion description for details.
Type:Warning
Intermediate
785 Wrong character in current last name: A character not normally used in a name is in the current last name field. See suggestion description for details.
Type:Warning
Easy
787 Unique name in Current Last Name: Current Last Name of this profile is unique on WikiTree. This could be a misspelled Current Last Name.
Type:Warning
Play the .
Intermediate
788 Period in Current Last Name: A period is found in the Current Last Name field which is not allowed by WikiTree guidelines. See suggestion description for details.
Type:Warning
Intermediate
791 Separator in last name other: There is a separator in the last name other field. Examples include "/", "-", ",", "(" and ")". Separators should normally not be used in the last name other field. See error description for details and exceptions.
Type:Error
Easy
792 Number in last name other: There is a number in the last name other field. Numbers should not normally be used in the last name other. See error description for details.
Type:Error
Easy
793 Prefix in last name other: The Last Name Other field has text that should be in prefix/suffix.
Type:Warning
Easy
794 Wrong word in last name other: A word not normally used as a name is in the last name other field. See suggestion description for details.
Type:Warning
Easy
795 Wrong character in last name other: A character not normally used in a name is in the last name other field. See suggestion description for details.
Type:Warning
Easy
797 Unique name in Last Name Other: Last Name Other of this profile is unique on WikiTree. This could be a misspelled Last Name Other.
Type:Warning
Play the .
Intermediate
798 Period in Current Last Name: A period is found in the Period in Other Last Names field which is not allowed by WikiTree guidelines. See suggestion description for details.
Type:Warning
Intermediate
911 Swedish patronym DOTTER for male: Profile's gender is male and patronym indicates it should be female. Read more about patronyms.
Type:Error
Advanced
912 Swedish patronym SSON for female
Type:Error
Advanced
913 Swedish patronym DOTTER abbreviated
Type:Warning
Advanced

Gender Suggestions

Click on the image for the library of Suggestions Videos.


Suggestions Type, Descriptions, Page & Video Links
Difficulty Rating
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).
Type:Error
Play the .
Intermediate
204 Father has no Gender: This person's father doesn't have a gender. Set father's gender.
Type:Error
Easy
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)
Type:Error
Play the .
Intermediate
304 Mother has no Gender: This person's mother doesn't have a gender. Set mother's gender.
Type:Error
Easy
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.
Type:Error
Easy
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.
Type:Error
Play the .
Easy
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.
Type:Error
Play the .
Intermediate
502 Missing male gender: Person with this name is most likely male, but no gender is checked on the profile . Enter the correct gender.
Type:Error
Play the .
Easy
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.
Type:Error
Play the .
Intermediate
504 Missing probably male gender: Person with this name should statistically be male, but no gender has been set.
Type:Error
Play the .
Intermediate
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.
Type:Error
Play the .
Intermediate
506 Missing female gender: Person with this name is most likely female, but no gender is checked on the profile. Enter the correct gender.
Type:Error
Play the .
Intermediate
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.
Type:Error
Play the .
Intermediate
508 Missing probably female gender: Person with this name should statistically be female, but no gender has been set.
Type:Error
Play the .
Intermediate
509 Missing gender: Person has no gender set and gender cannot be derived from name.
Type:Error
Play the .
Intermediate
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.
Type:Error
Play the .
Intermediate

Location Suggestions

Click on the image for the library of Suggestions Videos.


Suggestions Type, Descriptions, Page & Video Links
Difficulty Rating
601 Wrong word in birth location: The birth location entered is not a valid geographic location. This may include street names which should not be in the location field.Intermediate
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.
Type:Error
Easy
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.
Type:Error
Intermediate
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.
Type:Error
Play the .
Intermediate
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.
Type:Error
Intermediate
606 Bogus birth location: Location is probably not correct.
Type:Error
Intermediate
607 Misspelled word in birth location: One of the words in the birth location field is misspelled.
Type:Error
Easy
608 Misspelled country in birth location: The last word in the birth location field, if it is a country, is misspelled.
Type:Error
Easy
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.
Type:Error
Easy
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 capitalized except words such as "and" and "of".)
Type:Error
Easy
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 capitalized except words such as "and" and "of".)
Type:Error
Easy
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.
Type:Error
Intermediate
613 () in birth location : Parentheses ( ) are used within the birth location name. Parentheses are not allowed in location fields.
Type:Error
Easy
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.
Type:Error
Intermediate
631 Wrong word in death location: The death location entered is not a valid geographic location.
Type:Error
Intermediate
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.
Type:Error
Easy
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.
Type:Error
Intermediate
634 Death location too 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.
Type:Error
Play the .
Easy
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.
Type:Error
Intermediate
636 Bogus death location: Location is probably not correct.
Type:Error
Intermediate
637 Misspelled word in death location: One of the words in the death location field is misspelled.
Type:Error
Easy
638 Misspelled country in death location: The last word in the death location field, if it is a country, is misspelled.
Type:Error
Easy
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.
Type:Error
Easy
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 capitalized except words such as "and" and "of".)
Type:Error
Easy
641 Death location in lowercase: All characters in the death location are in lowercase. Death locations should be entered in title case (The first letter of each word capitalized except words such as "and" and "of".)
Type:Error
Easy
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.Intermediate
643 () in death location: Parentheses ( ) are used within the death location name. Parentheses are not allowed in location fields.
Type:Error
Easy
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.
Type:Error
Intermediate
661 Wrong word in marriage location: The marriage location entered is not a valid geographic location.
Type:Error
Intermediate
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.
Type:Error
Easy
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.
Type:Error
Intermediate
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.
Type:Error
Play the .
Intermediate
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.
Type:Error
Easy
666 Bogus marriage location: Location is probably not correct.
Type:Error
Intermediate
667 Misspelled word in marriage location: One of the words in the marriage location field is misspelled.
Type:Error
Easy
668 Misspelled country in marriage location: The last word in the marriage location field, if it is a country, is misspelled.
Type:Error
Easy
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.
Type:Error
Easy
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 capitalized except words such as "and" and "of".)
Type:Error
Easy
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 capitalized except words such as "and" and "of".)
Type:Error
Easy
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.
Type:Error
Intermediate
673 () in marriage location: Parentheses ( ) are used within the marriage location name. Parentheses are not allowed in location fields.
Type:Error
Easy
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.
Type:Error
Easy

Privacy Suggestions

Click on the image for the library of Suggestions Videos.


Suggestions Type, Descriptions, Page & Video Links
Difficulty Rating
109 Profile should be open (birth date): This profile is locked but the birth date is greater than 150 years in the past. Either the profile should be opened or, if wrong, the birth date should be corrected.
Type:Error
Play the .
Intermediate
110 Profile should be open (death date): This profile is locked but the death date is greater than 100 years in the past. Either the profile should be opened or, if wrong, the death date should be corrected.
Type:Error
Intermediate
114 Still Living Status with Death Date: This profile has a death date entered, but also has the "still living" radio button under the death date checked.
Type:Error
Intermediate
115 Still Living Status and entered death location: These profiles have Still living selected and death location entered.
Type:Error
Intermediate
118 Still living death location status with death date: This profile has a death date entered, but also has the "intentionally blank because still living" radio button under the death location checked.
Type:Error
Intermediate
119 Still living in death location status with death location: This profile has a death location entered, but also has the "intentionally blank because still living" radio button under the death location checked.
Type:Error
Intermediate
120 Possible still living with death date: This profile has a death date entered, but there is some reason within the profile to question the death (such as an active email account.)
Type:Error
Intermediate
121 Possible still living with death location: These profiles have some reason to be marked as living.Intermediate
212 Profile should be open (Child birth date): This error is similar to error's 109 and 110, but are identified for profiles with no birth and death date and their children were born more than 135 years ago.
Type:Error
Intermediate
312 Profile should be open (Child birth date): This error is similar to error's 109 and 110, but are identified for profiles with no birth and death date and their children were born more than 135 years ago.
Type:Error
Intermediate

Biography Suggestions

Click on the image for the Complete Collection of Suggestions Videos.


Suggestions Type, Descriptions, Page & Video Links
Difficulty Rating
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.
Type:Warning
Play the .
Advanced
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.
Type:Warning
Play the .
Advanced
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.
Type:Warning
Play the .
Advanced
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.
Type:Error
Play the .
Advanced
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 "=".
Type:Error
Play the .
Headings
Play the Headings.
Advanced
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.
Type:Error
Play the .
Advanced
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.
Type:Error
Play the .
Advanced
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.
Type:Error
Play the .
Easy
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.
Type:Error
Play the .
Easy
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.
Type:Error
Play the .
Advanced
835 Local file reference: The biography in this profile has references to files contained on the author, editor or creators' local computer. These files are not visible on the Internet. See the 835 suggestion page for an example.
Type:Error
Play the .
Advanced
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.
Type:Warning
Play the .
Advanced
852 GEDCOM uncleaned Parse Last name: 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.
Type:Warning
Play the .
Intermediate
853 GEDCOM Junk: The biography contains GEDCOM sections that should not be on WikiTree. See Sections you can delete.
Type:Warning
Play the .
Intermediate

</References> Tags and Inline Citations <ref> Suggestions

Click on the image for the Complete Collection of Suggestions Videos.

Suggestions Type, Descriptions, Page & Video Links
Tag You're It!
Play the Tag You're It!.
Difficulty Rating
861 Inline citation doesn't start with "<ref>": Inline citations must start with "<ref>" and end with "</ref>". The biography in this profile contains one or more inline citations ending in "</ref>", but there is no matching "<ref>" sign showing the beginning of the citation.
Type:Error
Play the .
Intermediate
862 Inline citation doesn't end with </ref>: Inline citations must start with "<ref>" and end with "</ref>". The biography in this profile contains one or more inline citations beginning with "<ref>", but there is no matching "</ref>" sign showing the end of the citation.
Type:Error
Play the .
Intermediate
863 Missing <references /> tag: The biography of this profile does not contain a "<references/>" tag. All Wikitree profile biographies should contain a Sources heading and should have a "<references/>" tag just below the Sources heading.
Type:Error
Play the .
Easy
864 Almost empty <ref> tag: Profile has almost empty inline citations "<ref>"..."</ref>".
Type:Error
Play the .
Intermediate
865 Unchanged <ref>Insert reference here</ref> tag : Inline citation form "<ref>"Insert reference here"</ref>" was added by the toolbar button but no citation was inserted.
Type:Error
Play the .
Intermediate
866 Duplicated <references />: Profile has multiple "<references />" tags. One "<references />" tag should be located just below the Sources heading.
Type:Error
Play the .
Intermediate
867 Too many Inline citations: Profile has too many inline citations "<ref>"..."</ref>".
Type:Error
Play the .
Advanced
868 Inline citations after <references /> tag: Profile has inline citations "<ref>"..."</ref>" after the "<references/>" tag that displays them. Such citations are not displayed on the profile.
Type:Error
Play the .
Advanced
869 Duplicated named Inline citations: Profile has two or more named inline references, where the name is the same.
Type:Error
Play the .
Advanced
870 Missing named Inline citations: Profile is using named inline reference "<ref name="SomeName" />", that is not defined by "<ref name="SomeName">"..."</ref>".
Type:Error
Play the .
Advanced
DBE_871 Use of angled double quotes in name of citation: Angled double quotes are used rather that double straight quotes due to editor software changes.
Type:Error
Play the .
Advanced

Template Suggestions

Click on the image for the library of Suggestions Videos.


Suggestions Type, Descriptions, Page & Video Links
Difficulty Rating
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.
Type:Error
Play the .
Easy
842 Template doesn't end with double }: A template in the biography of the profile does not end with double curly brackets "{{". All Wikitree templates must end with double curly brackets. See the Template help page for more details on the use of templates.
Type:Error
Play the .
Easy
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 longer exists or a template that is not yet created.
Type:Error
Advanced
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.
Type:Error
Advanced
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, and the Category:Templates to find the types of templates to review.
Type:Error
Advanced
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.
Type:Error
Advanced
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.
Type:Error
Advanced
848 Error in template parameters: A template in the biography of the profile has one or more unacceptable values. Please see the suggestion page for the appropriate template for correct values.
Type:Error
Advanced
849 Template parameter doesn't exist:Template parameters may have changed after its use on the profile or could be a typo in parameter name. Please see the suggestion page for the appropriate template for correct values.
Type:Error
Advanced

Wikidata Suggestions

Click on the image for the library of Suggestions Videos.


Suggestions Type, Descriptions, Page & Video Links
Difficulty Rating
Some WikiTree profiles are matched with a profile in Wikidata. See Wikidata. These suggestions point to differences between the Wikitree and Wikidata items. When working on these suggestions, please keep in mind that Wikidata is not a source. All differences should be researched to determine which entry contains the most accurate data.
541 Wikidata - Clue for Father: This suggestion indicates that there is a father on WikiData and the profile has no father connected on the WikiTree profile. There is also a possibility of some error in either WikiTree or WikiData that should be found and resolved. See Wikidata.
Type:Warning
Intermediate
542 Wikidata - Possible Father on WikiData: Some WikiTree profiles are matched with a profile in WikiData. See Wikidata. This suggestion indicates that there is a father on WikiData that can be connected to a WikiTree profile. There is also a possibility of some error on either WikiTree or WikiData that should be found and resolved.
Type:Warning
Intermediate
543 Wikidata - Clue for Mother: This suggestion indicates that there is a mother on WikiData and the profile has no mother connected on the WikiTree profile. There is also a possibility of some error in either WikiTree or WikiData that should be found and resolved. See Wikidata.
Type:Warning
Intermediate
544 Wikidata - Possible Mother on WikiData: Some WikiTree profiles are matched with a profile in WikiData. See Wikidata. This suggestion indicates that there is a mother on WikiData that can be connected to a WikiTree profile. There is also a possibility of some error on either WikiTree or WikiData that should be found and resolved.
Type:Warning
Intermediate
546 Wikidata - Possible Spouse on WikiData: Some WikiTree profiles are matched with a profile in WikiData. See Wikidata. This suggestion indicates that there is a spouse on WikiData that can be connected to a WikiTree profile. There is also a possibility of some error on either WikiTree or WikiData that should be found and resolved.
Type:Warning
Intermediate
551 Wikidata - Missing gender: Some WikiTree profiles are matched with a profile in WikiData see Wikidata.
Type:Warning
Intermediate
552 Wikidata - Different gender: Gender data on the Wikitree profile differs from the gender data on the Wikidata item.
Type:Warning
Intermediate
553 Wikidata - Empty Birth Date: The WikiTree profile has a corresponding Wikidata item with the birth date set but the WikiTree profile has no birth date entered.
Type:Warning
Intermediate
554 Wikidata - Imprecise birth date: The birth date recorded on the Wikitree profile is less precise than the birth date recorded on the corresponding Wikidata item.
Type:Warning
Intermediate
555 Wikidata - Different birth date: The birth date recorded on the Wikitree profile is different than birth date one recorded on the corresponding Wikidata item.
Type:Warning
Intermediate
556 Wikidata - Empty death date: The WikiTree profile has a corresponding Wikidata item with the death date set but the WikiTree profile has no death date entered.
Type:Warning
Intermediate
557 Wikidata - Imprecise death date: The death date recorded on the Wikitree profile is less precise than the death date recorded on the corresponding Wikidata item.
Type:Warning
Intermediate
558 Wikidata - Different death date: The WikiTree profile has a birth date that is different than the birth date on the corresponding Wikidata item.
Type:Warning
Intermediate
559 Wikidata - Missing birth location: There is no birth location on the Wikitree profile. There is a suggested birth location on the corresponding Wikidata item.
Type:Warning
Intermediate
561 Wikidata - Missing death location: There is no death location on the Wikitree profile. There is a suggested death location on the corresponding Wikidata item.
Type:Warning
Intermediate
563 Wikidata - Possible duplicate by father: The father identified in the Wikitree profile is different from the one in the corresponding Wikidata This may indicate a possible duplicate father on Wikitree.
Type:Hint
Advanced
564 Wikidata - Possible father: There is no father relationship identified in the Wikitree profile, however, there is a father identified on the corresponding Wikidata item. This may be a possible father for this profile person.
Type:Hint
Intermediate
565 Wikidata - Possible duplicate by mother: The mother identified in the Wikitree profile is different from the one in the corresponding Wikidata This may indicate a possible duplicate mother on Wikitree.
Type:Hint
Intermediate
566 Wikidata - Possible mother: There is no mother relationship identified in the Wikitree profile, however, there is a mother identified on the corresponding Wikidata item. This may be a possible mother for this profile person.
Type:Hint
Intermediate
567 Double Entry in Wikidata: The Item entry in Wikidata refers to two different profiles on WikiTree.
Type:Error
Play the .
Intermediate
568 Wikidata - Unconnected branches to the global tree: This suggestion is no longer calculated as of 20 July 2020.
Type:Hint
Suggestion Deleted
569 Wikidata - Unconnected orphans to the global tree: This suggestion is no longer calculated as of 20 July 2020
Type:Hint
Suggestion Deleted


FindaGrave Suggestions

Click on the image for the library of Suggestions Videos.
Mr E Figures Out Find A Grave
Play the Mr E Figures Out Find A Grave.


Suggestions Type, Descriptions, and Page & Video Links
Difficulty Rating
Some WikiTree profiles are matched with a memorial on Find-A-Grave.com. These suggestions point to differences between the Wikitree profile and the Find-A-Grave.com memorial. When working on these suggestions, 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. Often times Find-A-Grave memorials have family listings, obituaries, gravestone photos, etc. that could be clues to finding primary sources.
571 FindAGrave - Link without Grave ID: The WikiTree profile has a link to a FindAGrave memorial, but the Find A Grave memorial number is missing.
Type:Error
Play the .
Intermediate
572 FindAGrave - Link without matching Grave: The WikiTree profile is linked to a non-existent FindAGrave Memorial. The memorial may have been deleted, merged, or may have never existed.
Type:Error
Play the .
Intermediate
573 FindAGrave - Empty birth date: The WikiTree profile has a link to a FindAGrave Memorial with a birth date set but the corresponding WikiTree profile has no birth date entered.
Type:Hint
Play the .
Intermediate
574 FindAGrave - Imprecise birth date: The WikiTree profile has a birth date entered, and the birth date on the linked FindAGrave Memorial is more exact.
Type:Hint
Play the .
Intermediate
575 FindAGrave - Different birth date: The birth date recorded on the Wikitree profile is different from the birth date recorded on the linked FindAGrave Memorial.
Type:Hint
Play the .
Intermediate
576 FindAGrave - Empty death date: The WikiTree profile has a link to a FindAGrave Memorial that has a death date set, but the WikiTree profile has no death date entered.
Type:Hint
Play the .
Intermediate
577 FindAGrave - Imprecise death date: The WikiTree profile has a death date, and the death date in the FindAGrave Memorial is more exact.
Type:Hint
Play the .
Intermediate
578 FindAGrave - Different death date: The WikiTree profile linked to the FindAGrave Memorial with the death date set, but the WikiTree profile has no death date entered.
Type:Hint
Play the .
Intermediate
579 FindAGrave - Missing birth location: There is no birth location on the Wikitree profile, and there is a suggested birth location on the linked FindAGrave Memorial.
Type:Hint
Play the .
Intermediate
581 FindAGrave - Missing death location: There is no death location on the Wikitree profile, and there is a suggested death location on the linked FindAGrave Memorial.
Type:Hint
Play the .
Intermediate
585 FindAGrave - Multiple profiles link to same grave ID: Different WikiTree profiles are linked to the same FindAGrave Memorial. This might indicate family members connected to one Memorial or duplicate WikiTree profiles connected to the same Memorial.
Type:Hint
Play the .
Intermediate
586 FindAGrave - Link to merged Grave ID: The WikiTree profile has a link to FindAGrave Memorial, but the FindAGrave Memorial was merged into another Memorial.
Type:Error
Play the .
Intermediate
587 FindAGrave - Link to nonexistent Grave ID: The WikiTree profile has a link to a FindAGrave Memorial which has been deleted, merged or is the incorrect FindAGrave Memorial.
Type:Error
Play the .
Intermediate


Profile Completeness Suggestions

Managed profiles are checked for data completeness when the category Suggestions - Include Profile Completeness has been added to your own profile.
These suggestions are “warnings” generated weekly for the Suggestions Reports. Note that there may be a significant jump in the number of suggestions
for the profiles you manage, and you may opt-out from receiving these reports anytime by removing the category from your profile
.



Suggestion Type, Descriptions, and Page Links
Difficulty Rating
454 Profile completeness - Mother Status not set. The mother status is not set where there are children listed.
Type: Warning
Easy
455 Profile completeness - Birth date not set. The birthdate field is blank.
Type: Warning
Intermediate
456 Profile completeness - Birth date Status not set. The birthdate status is not set where there is a date in the field.
"Type: Warning"
Easy
457 Profile completeness - Birth Location not set. The birth location field is blank.
Type: Warning
Intermediate
458 Profile completeness - Birth location Status not set. The birth location status is not set where there is a location shown.
"Type: Warning"
Easy
459 Profile completeness - Birth location Country not recognised. The country in the birth location field isn't recognized. This could result from a typo.
Type: Warning
Easy
460 Profile completeness - Birth Location Country not official. Location is not entered in the official form for that country.
Type: Warning
Easy
461 Profile completeness - Death date not set. The deathdate field is blank.
"Type: Warning"
Intermediate
462 Profile completeness - Death date Status not set. The deathdate status is not set where there is a date in the field.
Type: Warning
Easy
463 Profile completeness - Death Location not set. The death location field is blank.
"Type: Warning"
Intermediate
464 Profile completeness - Death location Status not set. The deathdate status is not set where there is a date in the field.
Type: Warning
Easy
465 Profile completeness - Death location Country not recognised. The country in the death location field isn't recognized. This could result from a typo.
Type: Warning
Easy
466 Profile completeness - Death Location Country not official. Location is not entered in the official form for that country.
Type: Warning"
Easy
467 Profile completeness - Short Biography [<500. There is less than 500 characters of text in the Biography field.
Type: Warning
Intermediate

Links

  • Page with latest suggestions August 9th 2020 2020-08-09
  • 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 suggestions
    • 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 suggestions. Calculations are now exact except Before and After qualifiers.
    • 400 Mclean-3147 suggested finding all partners with the 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 07:05, 5 August 2020. This page has been accessed 80,353 times.