Data_Doctors_Project_Images-214.png

Easy Suggestions

Privacy Level: Public (Green)
Date: 2 Dec 2020
Surnames/tags: data_doctors suggestions difficulty level
This page has been accessed 1,349 times.

This page details easy difficulty level suggestions both new WikiTree members and newly badged Data Doctors can work on comfortably, and make substantive contributions to WikiTree's one-world tree.

Suggestions and Data Doctors Project - Related Page Links
Suggestions Guidelines Suggestion Reports & Status Page Status Page Project Home Page
Intermediate Level Suggestions Advanced Level Suggestions Suggestions Groups & More Easy Level Suggestions (this page)






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

Contents

Easy Level Suggestions by Group

Easy Suggestions are basic format issues caused by typos, punctuation, omissions, name or date errors. (Examples: Brackets, Typos in any field, Headings).
They are organized by Suggestion Groups 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.
Running Time: 3:08

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


An Introduction to Dates and Dating Issues


Type & Link Name & Description
(links to the suggestion page)
Common Cause
Error101 Birth in future: Birth date is in the future. The most common cause is a typo in the birth date.
Error102 Death in future: Death date is in the future. The most common cause is a typo in the death date.
Error411 Marriage End Date in future: The marriage end date is in the future. The most common cause is a typo in the marriage date. Go to the Edit tab, click on "edit marriage" and correct the date if it can be determined from the marriage source.

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
Error711 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.
Error712 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
Error715 Wrong character in Prefix: In the Prefix there is unusual characterSee error description for details.
Error721 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.
Error722 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.
Error725 Wrong character in first name: A character not normally used in a name is in the first name field. See error description for details.
Error731 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.
Error732 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
Error735 Wrong character in preferred name: A character not normally used in a name is in the preferred name field. See error description for details.
Error741 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.
Error742 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.
Warning743 Prefix in middle name: The middle name field contains a term normally considered a prefix. See suggestion description for details.
Error745 Wrong character in middle name: A character not normally used in a name is in the middle name field. See error description for details.
Error751 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.
Warning749 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. To work on this suggestion, you must be a member of the Netherlands Project or work with Dutch Naming Conventions
Error751 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.
Error752 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.
Error753 Prefix in nicknames: The nicknames field contains a term normally considered a prefix. See suggestion description for details.
Warning755 Wrong character in Nicknames: In Nicknames there is unusual character.Usually a typo is the common cause.
Warning765 Wrong character in suffix: In the Suffix there is unusual character. This could be a misspelled suffix.
Error782 Number in current last name: In Current Last name numbers have been found. Typo or number in the wrong field.
Error783 Prefix in current last name: The current last name field contains a term normally considered a prefix. See error description for details.
Error785 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.
Error791 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.
Error792 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.
Warning793 Prefix in last name other: The Last Name Other field has text that should be in prefix/suffix.Entered the prefix in the wrong field.
Warning794 Wrong word in last name other: A word not normally used as a name is in the last name other field. Entered the wrong information in the Last Name Other field. See suggestion description for details.
Warning795 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.

Gender Suggestions

Running Time: 3:41

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

Introduction to Gender Group Suggestions
Type & Link Name & Description
(links to the suggestion page)
Common Cause
Error204 Father has no Gender: This person's father doesn't have a gender. Gender was not entered when the profile was created. Set father's gender.
Error304 Mother has no Gender: This person's mother doesn't have a gender.Gender was not entered when the profile was created. Set mother's gender.
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.

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
Error607 Misspelled word in birth location: One of the words in the birth location field is misspelled.Common cause is a typo. Correct the spelling.
Error608 Misspelled country in birth location: The last word in the birth location field, if it is a country, is misspelled.Common cause is a typo. Correct the spelling.
Error609 Wrong character in birth location: There is a character in the birth location field that is normally not used in describing a geopolitical location.Common cause is a typo. Correct the spelling.
Error610 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".)Usually caused by a gedcom import and never changed. Need to change the case of the text to title case.
Error611 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".)Usually caused by a gedcom import and never changed. Need to change the case of the text to title case.
Error613 () in birth location : Parentheses ( ) are used within the birth location name. Parentheses are not allowed in location fields.Either move the information to the biography if it does not belong in the location field, or remove the parentheses if the place name is correct within them.
Error637 Misspelled word in death location: One of the words in the death location field is misspelled.A typo is the common cause; correct spelling.
Error638 Misspelled country in death location: The last word in the death location field, if it is a country, is misspelled.A typo is the common cause; correct spelling.
Error639 Wrong character in death location: There is a character in the death location field that is normally not used in describing a geopolitical location.A typo is the common cause; correct spelling.
Error640 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".)Usually caused by a gedcom import and never changed. Need to change the case of the text to title case.
Error641 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".)Usually caused by a gedcom import and never changed. Need to change the case of the text to title case.
Error643 () in death location: Parentheses ( ) are used within the death location name. Parentheses are not allowed in location fields.Either move the information to the biography if it does not belong in the location field, or remove the parentheses if the place name is correct within them.
Error667 Misspelled word in marriage location: One of the words in the marriage location field is misspelled.Possible typo; correct spelling.
Error668 Misspelled country in marriage location: The last word in the marriage location field, if it is a country, is misspelled.Possible typo; correct spelling.
Error669 Wrong character in marriage location: There is a character in the marriage location field that is normally not used in describing a geopolitical location.Possible typo; correct spelling.
Error670 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".)Usually caused by a gedcom import and never changed. Need to change the case of the text to title case.
Error'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".)Usually caused by a gedcom import and never changed. Need to change the case of the text to title case.
Error673 () in marriage location: Parentheses ( ) are used within the marriage location name. Parentheses are not allowed in location fields.Usually caused by a gedcom import and never changed. Remove ( ).

Biography Suggestions

Biography Suggestions are generated from issues in the narrative section of the profile. The Easy level suggestions are errors of headings typos. Please see:
WikiTree Style and Guidelines - Biography Information
Biographies Editing Tips Text Sections

Running Time: 2:41

Mr. E Heading for WikiTree!


All about Biography Headings
Type & Link Name & Description
(links to the suggestion page)
Common Cause
Error
Play the .
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 "=".Typo in heading entry.
Error
Play the .
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.Typo in heading entry.
Error
Play the .
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. Typo in heading entry.
Error
Play the .
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. Caused by a typo; gedcom issue.
Error
Play the .
825 Uses 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. Caused by a typo; gedcom issue.

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
Type & Link Name & Description
(links to the suggestion page)
Common Cause
Error
Play the .
863 Missing <references /> tag: There is no "<references/>" tag under the Sources heading. All Wikitree profile biographies should contain a Sources heading and should have a "<references/>" tag just below the Sources heading.The gedcom import did not create the tag or is an old profile created before this requirement. Add the <references/> tag.
Error
Play the .
871 Use of angled double quotes in name of citation: Angled double quotes are used rather that double straight quotesUsually caused by editor software changes.
Warning945 Unused SPAN Anchors The profile has HTML span anchors that are not used for inpage linking. The span anchor is set by <span id='name'></span>, and this warning is for the <span id='name'></span> that does not have a link to a [[#name]] or [[#name|link text]]. in the profile. See the 945 Unused Span Anchors page for further explanation. Caused by deleting the link to the anchor, or copy & paste of the anchor from another profile.

Template Suggestions

Templates are a special part of wiki markup used on WikiTree to insert feature boxes on profiles and for special formatting.
To experiment with one, try putting {{Unsourced}} above the == Biography == headline on a profile's edit page and preview the changes.
Type & Link Name & Description
(links to the suggestion page)
Common Cause
Error
Play the .
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 Templates.Typo of starting double curly bracket.
Error
Play the .
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 Templates. Typo of ending double curly bracket.
Error 892 Free-Space Profile page used as template: Free-Space Profile pages cannot be used as templates. Usually caused by not following or understanding the WikiTree guidelines. See Free-Space Profile Help.
Error 893 Free-Space Profile page used as transclusion: Free-Space Profile pages cannot be used for transclusion. The typical cause is not following or understanding the WikiTree guidelines. See Free-Space Profile Help and Template Guidelines Help - Not approved: Content Templates.

Profile Completeness Suggestions

Managed profiles are checked for data completeness when the category [[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. 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
Warning452: Profile completeness - Father Status not set.: The father's status was not set when the profile was created where there are children listed.Check for and add proof, then set the status of the father's relationship.
Warning454 Profile completeness - Mother Status not set. The mother status is not set where there are children listed. Did not set the mother's status. Check for proof and then set the status of the mother's relationship.
Warning456 Profile completeness - Birth date Status not set. The birthdate status is not set where there is a date in the field. Check for proof and then set the status.
Warning458 Profile completeness - Birth location Status not set. The birth location status is not set where there is a location shown. Check for proof and then set the status.
Warning459 Profile completeness - Birth location Country not recognised. The country in the birth location field isn't recognized. This could result from a typo.
Warning460 Profile completeness - Birth Location Country not official. Location is not entered in the official form for that country. Check for proof and then set the status.
Warning462 Profile completeness - Death date Status not set. The deathdate status is not set where there is a date in the field. Check for proof and then set the status.
Warning464 Profile completeness - Death location Status not set. The deathdate status is not set where there is a date in the field. Check for proof and then set the status.
Warning465 Profile completeness - Death location Country not recognised. The country in the death location field isn't recognized. This could result from a typo. Check source and correct location.
Warning466 Profile completeness - Death Location Country not official. The location is not entered in the official form for that country. Gedcom issues, misunderstanding the location for the timeframe, or typos are causes. Check for a source and correct the location.
Warning470 Profile completeness - Unused Span Anchors: The profile has HTML SPAN anchors that are not used for inpage linking. Span anchor is set by and links to it are set by #name or link text. That creates the inpage link to the anchor and clicking on that link scrolls the page to the anchor location where you usually read more about something. This suggestion is the same as 945 - Unused Span Anchors Caused by deleting the link to the anchor, or copy & paste of the anchor from another profile.

This page is part of the Data Doctors Project.
 
Latest report: February 25th 2024.
Data Doctors Challenge: Orphaned_Profiles_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: DD Suggestions Help