Help:Conventions/Name suffix

DRAFT PAGE - NOT READY FOR USE.

About WeRelate (Administration)  •   Working here (Welcome •  Tips)
Help menu (Index)  •   Directories
FAQ  •   Support desk  •  Watercooler  •   Wikicode (Tools)


Contents

Conventions for data entry


Examples and tips

  • Examples of entries in the Name suffix field:
  1. Joseph Smith was known as "Joseph Smith, Jr." to distinguish him from his father, so "Jr." was entered in his Name suffix field.
  2. This Henry Lee was both the third in his family to be named "Henry Lee" and a Governor of Virginia, so his collaborators have chosen to enter "III, 9th Governor of Virginia" in his Name suffix field.
  • The Name suffix field can be used temporarily for the duration of a research project to help in the identification of pages in the project. As a courtesy to future readers, special care should be taken to remove temporary information from the Name suffix field at the end of the project.
  • When searching for an existing Person page, there is no specific field for searching name suffixes, so the Surname field may be used.
Example: As part of a disambiguation project, a researcher has added identifying information in the Name suffix field to some persons living in pasture areas of early Augusta county, Virginia. To quickly find these existing pages again, he could search on "pasture" in the Surname field to return these results.
  • Note: When editing a Person page, the first name row is the Primary display name, therefore entries in that row must be agreeable to the collaborators on that page. Alternate name rows are provided for entering alternate names. See Name row conventions for details.

Why enter data this way?

  • We specify a mixed case style for all name fields for consistency and because it is the community standard our members chose during the development of this site. Other researchers may have used all upper case in the past to mark certain individuals as belonging to a specific tree or family. This practice should not be used here, since Person pages do not belong to any one user or family, and we provide the option of defining User Trees to identify pages that belong to a user-defined group.

Related information and tasks