Data_Doctors_Project_Images-214.png

Intermediate Suggestions

Privacy Level: Public (Green)
Date: 10 Dec 2020
Surnames/tags: data_doctors suggestions WikiTree
This page has been accessed 675 times.
This page details intermediate difficulty level suggestions. Intermediate Suggestions' require knowledge of WikiTree functions and proper formatting.
Suggestions and Data Doctors Project - Related Page Links
Suggestions Guidelines Suggestion Reports & Status Page Status Page Project Home Page
Advanced Level Suggestions Suggestions Groups & More Easy Level Suggestions Intermediate Level Suggestions (this page)

The process and reports used are here: Suggestions Guidelines for WikiTree Members and Data Doctors.

WikiTree members and badged Data Doctors need to be familiar with WikiTree functions and proper formatting such as:

  • Inline citations and sourcing;
  • Template formatting;
  • Fields and how to populate them correctly, (Birth and death locations and dates, naming conventions for people and places, suffixes, prefixes, etc.)
Some suggestions at this level require specific skills associated with other WikiTree projects, or require being a badged member of the project.
Knowledge and skill with maneuvering through the reports, performing corrections, reporting and tracking procedures are necessary. Please see: Suggestions Guidelines for WikiTree Members and Data Doctors.

Contents

Intermediate Level Suggestions by Group

Suggestions are oganized by Suggestion Group in the tables below with links to each suggestion's help page for a full description, methods, and hints on how to correct the suggestion. Video links are provided where there is a topic video for the group, or individual suggestions videos.

Date Suggestions

Date Suggestions indicate issues in the birth, marriage or death Date Fields. See also: Estimated Dates.
Date Group Topic
Running Time: 3:08



Mr. E Just Wants Good Dates - Why Is That So Difficult?

An Introduction to Dates and Dating Issues


Click on
the image for the library of Suggestions Videos.

See links for the specific suggestions below.
Type & Link Name & Description
(links to the suggestion page)
Common Cause
Error
Play the .
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.
Error104 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.
Error111 Died too young to be parent: This person was under ten years old at death, but has children attached to the profile.This can be caused by incorrect linking to the profile.
Error 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.
Error310 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.
Error401 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.
Error404 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.
Error405 Marriage too long after birth: The person's marriage date is more than 115 years after their birth date.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.
Error406 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 enter the correct relationship.
Error410 Marriage in future: Marriage date is in the future. The most common cause is a typo in the birth date.
Error412 Marriage End Date before Marriage Date: The marriage end date is before the marriage date. One or both dates may be incorrect.
Error413 Marriage too long: The difference between the marriage date and the marriage end date is more than 115 years.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 enter the correct relationship.
Error414 Marriage End Date before Birth Date: The marriage end date is before the person's birth date.Either the death or marriage dates are wrong, or both, or the relationship is incorrect. If the correct birth or marriage end date can be determined, correct it.
Error415 Marriage End Date too late: The difference between the person's birth date and their marriage end date is over 115 years. Either the birth or marriage dates are wrong, or both, or the relationship is incorrect.
Error416 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.
Error417 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

Relationship issues arise from incorrect connections between parents, siblings, or spouses. Check Relationship Status for more information.
To find the relationship between any two WikiTree profiles, test the Relationship Finder.
Type & Link Name & Description
(links to the suggestion page)
Common Cause
Error105 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 need merging. If you find they are not the same person, you can mark the error as a False Error after looking at both profiles and sources.
Error106 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 need merging. (Orphan profiles are ignored). If you find they are not the same person, you can mark the suggestion as a False Suggestion (do this for both profiles) after looking at both profiles and sources.
Error112 Person is father and mother: This person is father to some children and mother to others. Parentage should be corrected as appropriate.
Error202 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. Incorrect linking of one or both parents caused this.
Error211 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 need merging.
Error311 Duplicate sibling by Mother: There is a profile with the same full name, birth, and death dates, and same mother, but the mother is different. These two profiles may be duplicates; if so, after careful comparison, they need merging.
Warning419 Unmarried parents with no marriage: These parents have a common child, but no marriage is recorded for them, usually caused by older faulty gedcom imports. Try to find a marriage record and enter the marriage. If one can't be found, note that in the Research Notes section.
Error421 Hidden marriage on public or open profiles: There is a hidden marriage between the two persons that is not viewable on the profile. That shouldn't be the case on public and opened profiles. The cause is not completely understanding how to use the check box when entering the marriage information. Uncheck the check box on edit marriage page.

Name Suggestions

WikiTree Style and Guidelines - Naming Conventions and Name Fields
Name Displays Name Field Guidelines Prefix Field Suffix Field
General Naming Conventions Special Naming Conventions Correcting a Last Name at Birth The Rules


Name Suggestions are errors or warnings in the profile's Name Fields.

The causes range from typos in the First, Middle or Last Name's entry to wrong data entered in the name fields such as numbers, punctuation or separators.
Type & Link Name & Description
(links to the suggestion page)
Common Cause
Warning
Play the .
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 suggestionsThe incorrect relationship should be deleted or replaced with the correct one. Incorrect linking of one or both parents caused this.
Error713 Suffix in prefix: The contents of the prefix field should normally be in the suffix field. See suggestion description for details.
Error714 Wrong word in prefix: A word not normally used as a suffix is in the suffix field. See error description for details.
Warning
Play the .
717 Unique name in Prefix: The prefix of this profile is unique on WikiTree. This could be a misspelled prefix. The video applies - substitute the Prefix field for the referenced .
Warning723 Prefix in first name: The first name field contains a term normally considered a prefix. See error description for details.
Warning724 Wrong word in first name: A word not normally used as a name is in the first name field. See error description for details.
Warning
Play the .
727 Unique name in First Name: First Name of this profile is unique on WikiTree. This could be a misspelled First Name. The video applies - substitute the First Name field for the referenced field in the video.
Warning733 Prefix in preferred name: The preferred name field contains a term normally considered a prefix. See error description for details.
Warning734 Wrong word in preferred name: A word not normally used as a name is in the preferred name field. See error description for details.
Warning
Play the .
737 Unique name in Preferred Name: Preferred Name of this profile is unique on WikiTree. This could be a misspelled Preferred Name. The video applies - substitute the Preferred Name field for the referenced field in the video.
Warning744 Wrong word in middle name: A word not normally used as a name is in the middle name field. See error description for details.
Warning
Play the .
747 Unique name in Middle Name: Middle name of this profile is unique on WikiTree. That could be an indication of misspelled Preferred Name. The video applies - substitute the Middle Name field for the referenced field in the video.
Warning754 Wrong word in nicknames: A word not normally used as a name is in the nicknames field. See suggestion description for details.
Warning
Play the .
757 Unique name in Nicknames: Nickname of this profile is unique on WikiTree. This could be a misspelled Suffix. The video applies - substitute the Nickname field for the referenced field in the video.
Error761 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.
Error762 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.
Warning763 Prefix in suffix: The suffix field contains a term normally considered a prefix. See error description for details.
Error764 Wrong word in suffix: A word not normally used as a name is in the suffix field. See error description for details.
Warning
Play the .
767 Unique name in Suffix: Suffix of this profile is unique on WikiTree. This could be a misspelled Suffix. The video applies - substitute the Suffix field for the referenced field in the video.
Error772 Number in Last Name at Birth : The last name at birth contains a number.Typo or wrong entry in the field.
Warning773 Prefix in last name at birth: The last name at birth field contains a term normally considered a prefix. See suggestion description for details.
Warning774 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.
Warning775 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.
Warning
Play the .
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. The video applies - substitute the Last Name at Birth field for the referenced field in the video. If you are not the Profile Manager, you cannot change the LNAB field unless you are on the Trusted List. See Correcting LNAB.
Warning778 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 and also Correcting LNAB
Error781 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.
Warning784 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.
Warning
Play the .
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. The video applies - substitute the Last Name field for the referenced field in the video.
Warning788 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.
Warning
Play the .
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. The video applies - substitute the Last Name Other field for the referenced field in the video.
Warning798 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.

Gender Suggestions

Running Time: 3:41


Gender Confusion: Missing, Misidentified, or Just Plain Wrong!

Introduction to Gender Group Suggestions

Click on the image for the library of Suggestions Videos.


Individual Suggestions Videos are linked below
Type & Link Name & Description
(links to the suggestion page)
Common Cause
Error
Play the .
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.
Error402 Unknown gender of spouse: The person's spouse does not have their gender set.Gender was not entered when the profile was created. If it can be confidently determined, set the spouse's gender on their edit page.
Error
Play the .
403 Single-sex marriage: Both spouses have the same gender. Same-sex marriage is not uncommon today, but it was rare in history. Gender was not entered when the profile was created. Verify that one of the partners does not have the wrong gender and edit if appropriate.
Error
Play the .
502 Missing male gender: Person with this name is most likely male, but no gender is checked on the profile. Gender was not entered when the profile was created. Enter the correct gender.
Error
Play the .
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.
Error
Play the .
504 Missing probably male gender: Person with this name should statistically be male, but no gender has been set. Gender status not checked when profile was created.
Error
Play the .
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.
Error
Play the .
506 Missing female gender: Person with this name is most likely female, but no gender is checked on the profile. Gender was not entered when the profile was created. Enter the correct gender.
Error
Play the .
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.
Error
Play the .
508 Missing probably female gender: Person with this name should statistically be female, but no gender has been set. Gender status was not set.
Error
Play the .
509 Missing gender: Person has no gender set and gender cannot be derived from name.Gender was not set.
Error
Play the .
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

Location Suggestions are errors or warnings in the profile's Location Fields.

The causes range from typos in the birth, marriage or death place entry, wrong data entered in the location fields such as numbers, punctuation or separators, Gedcom import data issues, or abbreviations.
  • WIkiTree Style & Guidelines mandate "using their location, not ours," which means that the name of the location may have changed over time, and need to use the location name at the time the person in the profile lived there. Use caution working on Location Too Early errors; it may be simple to remove that location, but also need to check the correct name at that time in history.
Type & Link Name & Description
(links to the suggestion page)
Common Cause
Error601 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.
Error602 Y birth location: The field Birth place is filled with "Y" or "Y/" or "Y;" or "Yes", or begins with "Y/" or "Yes". These locations were part of GEDCOM imports and never corrected. These are invalid locations.
Error603 USA too early in birth location: The country of birth is entered as the United States of America (USA)The birth date is prior to 1776. Location fields should use the name that existed when the event took place.
Error
Play the .
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.
Error605 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.
Error612 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.
Error614 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.
Warning615 Birth Location Country not recognised This suggestion is calculated only for orphaned profiles.Possible typo, or the location is not recognized in predefined countries, or missing in the predefined countries list. This suggestion is calculated only for orphaned profiles.
Warning616 Abbreviated Birth location Country not recommended This suggestion is calculated only for orphaned profiles. Location is abbreviated, which is not recommended location format on Wikitree. Accepted exceptions are USA and UK.
Warning 617 Ambiguous Birth location Country not recommended This suggestion is calculated only for orphaned profiles. Location is ambiguous, which is not helpful. Ambiguous, or a problem with a separator - usually a comma is missing between place and country.
Warning618 Birth location Country not preferred by project The location is recognized as the country in predefined countries list, but it is flagged as not recommended form due to ambiguity. Location is abbreviated or ambiguous, which is not very useful, or a separator issue if a comma is missing between place and country.
Error631 Wrong word in death location: The death location entered is not a valid geographic location.IThis error generally occurs when extraneous information is entered or the location did not exist at the time of death.
Error632 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.is filled with "Y" or "Y/" or "Y;" or "Yes", or begins with "Y/" or "Yes". These locations were part of GEDCOM imports and never corrected. These are invalid locations. Enter correct location
Error633 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.
Error
Play the .
634 Death location too short: The death location field should contain a full description of the location with all applicable geopolitical designations up to and including the country. Short forms (abbreviations) for States and Countries should not be used; correct locations.
Error635 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.
Error642 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.
Error644 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.
Warning645 Death Location Country not recognised This suggestion is calculated only for orphaned profiles.Location is abbreviated, which is not recommended location format on Wikitree. Accepted exceptions are USA and UK.
Warning646 Abbreviated Death location Country not recommended: This suggestion is calculated only for orphaned profiles. Location is abbreviated, which is not recommended location format on Wikitree. Accepted exceptions are USA and UK.
Warning647 Ambiguous Death location Country not recommended: This suggestion is calculated only for orphaned profiles.Location is ambiguous, which is not helpful, or a problem with a separator - usually a comma is missing between place and country.
Warning648 Death location Country not preferred by project The location is recognized as the country in predefined countries list, but it is flagged as not recommended form due to ambiguity.Location is abbreviated or ambiguous, which is not very useful, or a separator issue if a comma is missing between place and country.
Error661 Wrong word in marriage location: The marriage location entered is not a valid geographic location.The marriage location should be the name of the location as it existed when the marriage took place.
Error662 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.These were part of GEDCOM imports and never corrected, These are invalid locations. Enter correct location.
Error663 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.
Error
Play the .
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.
Error665 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.Check proof and enter correct location.
Error672 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.
Error674 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. Usually caused by a gedcom import and never changed. Move street, church, or other place to the biography.
Warning675 Marriage Location Country not recognised: This suggestion is calculated only for orphaned profiles.Possible typo, or the location is not recognized in predefined countries, or missing in the predefined countries list.
Warning676 Abbreviated Marriage location Country not recommended: This suggestion is calculated only for orphaned profiles.Location is abbreviated, which is not recommended location format on Wikitree. Accepted exceptions are USA and UK.
Warning677 Ambiguous Marriage location Country not recommended: This suggestion is calculated only for orphaned profiles. Location is ambiguous, which is not helpful, or a problem with a separator - usually a comma is missing between place and country.
Warning678 Marriage location Country not preferred by project: The location is recognized as the country in predefined countries list, but it is flagged as not recommended form due to ambiguity.Location is abreviated or ambiguous, which is not very useful, or a separator issue if a comma is missing between place and country.

Privacy Suggestions

The Privacy Suggestions Group involves two issues:
  1. Security settings on the Privacy tab of the profile appearing as a colored lock on the upper-right corner of profiles. Unless a member is a the Profile Manger, or on the Trusted List, he or she cannot work on the profile; and
  2. templates and project-managed profiles with Project Account, ProjectBox, Project-Protected profile issues.

Private and Public Profiles

To work on Privacy Suggestions, you need to be familar with these topics.
WikiTree Style and Guidelines - Privacy Information, Open a Profile, and Status Indicator Information
Privacy Information WikiTree's Privacy Policy Trusted List Information Data Doctors Private and Public Profiles Steps to open a profile (birth 150 years ago/death 100 Years Ago
Profile Managers and When to Contact Relationship Status Uncertain Status & Info Date Fields Status Options Non-Biological Status & Info

Many of these suggestions cannot be addressed if the Privacy Level is not "Open," In most cases, you will have to contact the Profile Manager. See the information above.


Privacy locks are located on the Privacy tab of profiles.


Privacy Suggestions deal with the profiles with incorrect privacy level and issues with status indicators. See the table above for details.
Type & Link Name & Description
(links to the suggestion page)
Common Cause
Error
Play the .
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.
Error 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.
Error 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.Check the source and correct date or check status.
Error 115 Still Living Status and entered death location: These profiles have Still living selected and death location entered.Check the source and correct date or check status.
Error 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.Review source and correct the status.
Error 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.Review source and correct the status.
Error 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.)Either contact the Profile Manager or take other action.
Error 121 Possible still living with death location: These profiles have some reason to be marked as living.check sources and correct or contact the Profile Manager.
Error 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.The profile was not researched for sources or dates were ommited.
Error 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.Either the profile should be opened or, if wrong, the birth date should be corrected.

PPP, Project Account, & ProjectBox Suggestions

  • It is important that you are very familiar with the profiles' project, timeframe and location of the profiles on the Suggestions Report for the following suggestions.
Ask any questions in the G2G with the tags Data Doctors and Privacy Group Suggestions, or the Data Doctors Google Group (if you are a member). If the question involves a particular suggestion, include a tag Suggestion ### and a profile link where the suggestion appears.
  • When a project decides it will manage a profile, the project's Project Account (PA) becomes a Profile Manager (PM) for the profile. The project might then designate it as a Project Protected Profile (PPP), and occasionally green lock the project-managed profiles. In that case, anyone who is not a PM, or on the Trusted List (TL) of the profile cannot directly resolve the suggestion, and must send a private message (pm) to the PA about an issue on the profile, or a comment on the specific profile the PA will receive.
In this group of suggestions, some sort of mismatches in the PPP, PB, and PA relationships exist, or the ProjectBox is used instead of the project sticker. This is where the list of projects helps as both the ProjectBox and sticker information are on the project page.
  • The crucial knowledge for working on the following suggestions are in this table. Especially important are bolded and italicized.
  • In addition to the topics below, review the Privacy Suggestions Group page for additional instruction.
WikiTree Style and Guidelines - Project Protected Profile, ProjectBox, and Project Account Information
Project Protection Project Protecting and Merging Project-Managed Profiles Project Boxes Template: Project Box Stickers
List of Projects Project Accounts Link to Project Accounts Pages List of Project Accounts WTIDs Communication Before Editing Special Situations

  • These suggestions are intermediate and advanced difficulty levels and require fully understanding the definitions, suggestions issues, and resolutions before working on them.
PPP (Project Protected Profile) icon
Look for this image on the profile for these suggestions (where PPP is in the title).
Type & Link Name & Description
(links to the suggestion page)
Common Cause
Error 922 PPP With Project Account and without ProjectBox: Profile is a PPP (Project Protected Profile), but doesn't have a Project Box. It is managed by some project. The Project box was removed from the profile.
Error923 PPP Without Project Account and with ProjectBox: The profile is a PPP (Project Protected Profile), but isn't managed by a project and has a project's Project Box template. Project management was not assigned to the profile.
Error 931 ProjectBox without Project Account : Profile isn't managed by a project and has that project's Project Box template. Project management was not assigned to the profile.
Error933 Project Account and without ProjectBox: Profile doesn't have a Project Box. It is already managed by some project. Project box was removed from the profile.

Biography Suggestions

Biography Suggestions are generated from issues in the narrative section of the profile. The Intermediate level suggestions are warnings of Gedcom junk and sections left which are not needed in WikiTree biographies.
WikiTree Style and Guidelines - Biography Information
Biographies Gedcom Information Gedcom Junk You Can Delete

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


Please review the videos, and understand what needs to be done
before working on the profiles.
Type & Link Name & Description
(links to the suggestion page)
Common Cause
Warning
Play the .
853 GEDCOM Junk: The biography contains GEDCOM sections that should not be on WikiTree. See Sections you can delete.

Please understand that there may be information that should remain on the profile within the Gedcom-created sources. Proceed with care and understanding.


References Tags and Inline Citations Suggestions

WikiTree Style and Guidelines - Sources and References
Sources Sources and References Sources and References Editing Tips

Click image to watch the full video
Running Time: 3:19 with timestamps index.
Click on the segment links below
to watch a particular topic.
Segment 1 Segment 2 Segment 3 Segment 4


Click on the image for the Complete Collection of Suggestions Videos.
Type & Link Name & Description
(links to the suggestion page)
Common Cause
Error
Play the .
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.
Error
Play the .
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>" tag showing the end of the citation. The end "</ref>" tag was not entered or entered incorrectly.
Error
Play the .
864 Almost empty <ref> tag: Profile has almost empty inline citations "<ref>"..."</ref>".Tags were entered without a citation entered.
Error
Play the .
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.Either source was not moved or was not researched and added.
Error
Play the .
866 Duplicated <references />: Profile has multiple "<references />" tags. One "<references />" tag should be located just below the Sources heading.Text was not combined after a merge.

Template Suggestions

Templates are a particular part of wiki markup used on WikiTree to insert feature boxes on profiles and for special formatting.
  • For Intermediate Suggestions, WikiTree members need to have advanced WikiTree skills working on templates and these suggestions.
To work on these issues, you must know what templates are and how they are used in WikiTree. See these pages for further description of the issues involved in these suggestions. WikiTree members need to have advanced WikiTree skills to work on templates.
WikiTree Style and Guidelines - Templates
Help - Templates Template Guidelines Creating a Template List of Templates

Type & Link Name & Description
(links to the suggestion page)
Common Cause
Error894 Missing Required parameter in template: Some template parameters must be entered for a template to work properly and they are not in the template. Not understanding how templates are used, or a change in the template design after the template was put on the profile.
Warning895 Using Deprecated parameter in template: Some template parameters are no longer used by a template and should be removed, since they serve no purpose. Caused by not understanding how templates are used, or a change in the template design after the template was put on the profile.
Warning896 Unknown parameter in template: Some template parameters were removed from a template, or there is a typo in the parameter name. Caused by not understanding how templates are used. or a change in the template design, or a typo.
Error897 Error in template parameters: Template parameters are checked for validity. Caused by not understanding how templates are used, or a change in the template design, or a typo.

Link Suggestions Group

The Link Suggestions Group are errors, and all are Intermediate difficulty level, which deal with broken links within WikiTree to external websites or pages.

They require knowledge of standard technical abbreviations representing terms and the terms' references, and also how links are used in WikiTree, internally and externally.
  • In addition to the WikiTree and suggestion information below, please refer to the Link Group Suggestions page for additional instructions and tips.
WikiTree uses links to both internal and external data:
  • Internal links link categories, pages, profiles within a page, and even to locations within the same page, appearing as underlined text.
  • External links connect to websites and pages outside of the WikiTree database. A good example is from Data Doctors Project pages to WikiTree Plus, or from this page to the Suggestion Pages linked below. Most commonly used by WikiTree members are linked sources in Wikitree profiles. These links also appear as underlined text within the page.
  • Link Templates have been created for both internal and external connections for WikiTree users, so familiarity with these link templates, and knowledge of Templates usage is necessary for working on Link Suggestions.
Because these are all intermediate difficulty-level suggestions, know the pages below, and the guidelines found.
  • Did you know? A link template to an external webpage is not a substitute for the full source citation? For example, the FindAGrave template should be used with the full source citation found on the "View Source tab from the FindAGrave memorial, not in place of it.
WikiTree Style and Guidelines - Links & Link Templates
Adding Links Link Templates Template Information


Link Suggestions are errors in the profile's external links, usually in the profile's source citations.

The causes range from:
  • typos in the URL entered in the link,
  • the domain has changed, or
  • an IP was used rather than the actual website URL.
Suggestions Type, Descriptions, & Page Links Difficulty Rating
961: Invalid domain name in link: Domain name (DNS) in link is not formed correctly. it should usually be in form like www.wikitree.com. Since it is not correct, the link leads to nowhere.
Type:Error
Intermediate
962 Domain name in the link is not resolved : The URL or domain name in the link is not resolved to any IP address. If the URL or domain name isn't resolved to an IP , the link can't work, since the computer to respond to the request doesn't exist. Usual causes are a typo, or the web server no longer exists, or its URL or domain name was changed. Causes are a typo -often there is a space in the DNS name, or IP used instead of DNS. IP is very unstable in the long term. Sooner or later it will not work. IP should never be used in the link.
Type:Error
Intermediate
965 Link error 404 Not Found: The link is pointing to a page that doesn't exist. Usual causes are a typo, or the page moved to another location, or the web server no longer has the page available.
Type:Error
Intermediate
966 Link error - various: The link is pointing to a server that doesn't exist. There can be various reasons for the error. Usually caused by a typo, or the web server does not exist. That can be temporary.
Type:Error
Intermediate
967 Link error in domain: The link is pointing to a server that doesn't exist. There can be various reasons for the error. Usually caused by a typo, or the web server does not exist. That can be temporary.
Type:Error
Intermediate

WIkidata Suggestions

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.
Type & Link Name & Description
(links to the suggestion page)
Common Cause
Warning541 WikidData - 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.
Warning543 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.
Warning546 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.
Warning551 Wikidata - Missing gender: Some WikiTree profiles are matched with a profile in Wikidata see Wikidata. The gender was not entered.
Warning552 Wikidata - Different gender: Gender data on the Wikitree profile differs from the gender data on the Wikidata item. One of the entries is incorrect, either in WikiTree or Wikidata.
Warning553 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. The birth date either was not verified or entered in the WikiTree profile.
Warning554 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. The birth date has not been sourced or fully entered in WikiTree.
Warning555 Wikidata - Different birth date: The birth date recorded on the Wikitree profile is different than birth date one recorded on the corresponding Wikidata item. The birth date either was not verified or entered incorrectly on the WikiTree profile or Wikidata.
Warning556 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. The death date either was not verified or entered in the WikiTree profile.
Warning557 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. The death date has not been sourced or fully entered in WikiTree.
Warning558 Wikidata - Different death date: The WikiTree profile has a death date that is different than the death date on the corresponding Wikidata item. The death date either was not verified or entered incorrectly on the WikiTree profile or Wikidata.
Warning559 Wikidata - Missing birth location: There is no birth location on the Wikitree profile. There is a suggested birth location on the corresponding Wikidata item. The birth location was not verified or entered in the WikiTree profile.
Warning561 Wikidata - Missing death location: There is no death location on the Wikitree profile. There is a suggested death location on the corresponding Wikidata item. The death location was not verified or entered in the WikiTree profile.
Warning564 Wikidata - Possible father: There is no father relationship identified in the Wikitree profile; however, there is a father identified on the corresponding Wikidata item. There may be a possible father for the person in the profile. The father of the person in the profile has not been entered or connected.
Hint566 Wikidata - Possible mother: There is no mother relationship identified in the Wikitree profile; however, there is a mother identified on the corresponding Wikidata item. There may be a possible mother for the person in the profile.The mother of the person in the profile has not been entered or connected.
Error
Play the .
567 Double Entry in Wikidata: The Item entry in Wikidata refers to two different profiles on WikiTree. There are duplicate profiles on WikiTree that need to be found and merged.

FindAGrave Suggestions

Some WikiTree profiles match with a memorial on Find-A-Grave.com. These suggestions point to differences between the Wikitree profile and the FindAGrave.com memorial.

  • The abbreviation for FindaGrave to use in comments or in emails is FAGM. The shorter acronym is offensive to many members and should not be used, or changed if it appears in a profile you work on.

When working on these suggestions, please keep in mind that FindaGrave is not a primary source. Research all differences to determine which entry contains the most accurate data. Often FindaGrave memorials have family listings, obituaries, gravestone photos, etc. that could be clues to finding primary sources.

For WIkiTree guidelines about using the memorials, please see: FindAGrave FAQ.

Click image to watch the full video
Running Time: 5:44
Click on the segment links
to watch that topic.
Segment 1 Segment 2
Click on the image for the library of Suggestions Videos.

See links for the specific suggestions below.
Type & Link Name & Description
(links to the suggestion page)
Common Cause
Warning
Play the .
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. The incorrect citation was used, or the memorial number was deleted.
Warning
Play the .
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.
Warning
Play the .
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.No source for the birth date, or no birthdate entered.
Error
Play the .
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. Proof for the birthdate hasn't been entered on WikiTree, or the birthdate was not completely entered.
Error
Play the .
575 FindAGrave - Different birth date: The birthdate recorded on the Wikitree profile is different from the birthdate recorded on the linked FindAGrave Memorial.One of the dates is incorrect and need to research to verify the correct date.
Warning
Play the .
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.No source for the death date, or no death date entered.
Error
Play the .
577 FindAGrave - Imprecise death date: The WikiTree profile has a death date, and the death date in the FindAGrave Memorial is more exact. The death date in Wikitree is estimated.
Error
Play the .
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. The death date is incorrect in WikiTree or FindAGrave.
Warning
Play the .
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. The birth location was not entered in WikiTree.
Warning
Play the .
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. The death location was not entered in WikiTree.
Hint
Play the .
585 FindAGrave - Multiple profiles link to same grave ID: Different WikiTree profiles are linked to the same FindAGrave Memorial. This may indicate family members connected to one Memorial, or duplicate WikiTree profiles connected to the same Memorial.
Hint
Play the .
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.Incorrect memorial link. Need to find the correct memorial and revise on the profile.
Hint
Play the .
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. Possible typo when the memorial was added on WikiTree, or FindAGrave removed the memorial. Search for the correct memorial, or remove the FindAGrave memorial reference and citation from the profile.
Hint591 FindAGrave - Possible father: Some WikiTree profiles are matched with a memorial on FindAGrave. If a memorial of the father is linked from WikiTree it is proposed as a possible fatherThe father relation is missing in WikiTree.
Hint592 FindAGrave - Possible mother: Some WikiTree profiles are matched with a memorial on FindAGrave. If a memorial of the mother is linked from WikiTree it is proposed as a possible motherThe mother relation is missing in WikiTree.

Profile Completeness Suggestions

WikiTree Style and Guidelines - Privacy Information
Relationship Status Uncertain Status & Info Date Fields Status Options Non-Biological Status & Info

Managed profiles are checked for data completeness when the category [[Category:Suggestions_-_Include_Profile_Completeness]] has been added to your own profile. (You can copy & paste this to your profile.)

These suggestions are “warnings” generated weekly for the Suggestions Reports, and indicate where status indicators were not checked for profile fields. Note that there may be a significant jump in the number of suggestions for the profiles you manage.

To eliminate these suggestions, you may opt-out from receiving these reports anytime by removing the category from your profile.

Type & Link Name & Description
(links to the suggestion page)
Common Cause
Warning455 Profile completeness - Birth date not set. The birth date field is blank.The birth date was omitted.
Warning457 Profile completeness - Birth Location not set. The birth location field is blank. The birth location was not entered.
Warning461 Profile completeness - Death date not set. The death date field is blank. The death date was omitted.
Warning463 Profile completeness - Death Location not set. The death location field is blank.The birth location was not entered.
Warning467 Profile completeness - Short Biography [<500. There is less than 500 characters of text in the Biography field. There are no sources or narrative entered.
Warning
Play the .
468 Profile completeness - GEDCOM Junk: The biography contains GEDCOM sections that should not be on WikiTree. See Sections you can delete. This suggestion is the same as 853 - GEDCOM Junk but with different limits caused by not editing the profile after a gedcom import.
Warning474 Profile completeness - Abbreviated Birth location Country not recommended: The birth location is abbreviated, which is not recommended in Wikitree location fields. Accepted exceptions are USA and UK. Location endings that are identified as invalid are defined in this table. Look for number 616 in "Accepted spelling" column. The table is maintained by Aleš and Data Doctors project in colaboration with other geographical projects. This suggestion is the same as 616 - Abbreviated Birth location Country not recommended The location is recognized as the country in predefined countries list, but it is flagged as not recommended form due to the usage of abbreviations.
Warning475 Profile completeness - Abbreviated Death location Country not recommended: The death location is abbreviated, which is not recommended in Wikitree location fields. Accepted exceptions are USA and UK.
Location endings that are identified as invalid are defined in this table, which is maintained by Aleš and Data Doctors project in colaboration with other geographical projects. This suggestion is the same as 646 - Abbreviated Death location Country not recommended
The location is recognized as the country in predefined countries list, but it is flagged as not recommended form due to the usage of abbreviations.
Warning477: Profile completeness - Ambiguous Birth location Country not recommended: The birth location is ambiguous, usually due to a separator issue such as a missing comma between place and country, or an incorrect separator was used. Location endings that are identified as invalid are defined in this table. Look for number 617 in "Accepted spelling" column. The table is maintained by Aleš and Data Doctors Project in colaboration with other geographical projects. This suggestion is the same as 617 - Ambiguous Birth location Country not recommended.The location is recognized as the country in predefined countries list, but it is flagged as not recommended form due to ambiguity.
Warning 478: Profile completeness - Ambiguous Death location Country not recommended: The death location is ambiguous, usually due to a separator issue such as a missing comma between place and country, or an incorrect separator was used. Location endings that are identified as invalid are defined in this table. Look for number 617 in "Accepted spelling" column. The table is maintained by Aleš and Data Doctors project in colaboration with other geographical projects. This suggestion is the same as 647 - Ambiguous Death location Country not recommended The location is recognized as the country in predefined countries list, but it is flagged as not recommended form due to ambiguity.

This page is part of the Data Doctors Project.
 
Latest report: February 18th 2024.
Data Doctors Challenge: Reference_Tags_XLIV 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




Images: 1
DD Cover Bordered
DD Cover Bordered

Collaboration


Comments

Leave a message for others who see this profile.
There are no comments yet.
Login to post a comment.

Categories: Data Doctors Project