Geni naming conventions - data entry examples

Geni naming conventions - data entry examples

Formerly titled “Coalition for the Standardization of Geni Naming Conventions – Convention Workshop”
Last updated 8 December 2023

Concept project to support disccussion http://www.geni.com/discussions/101031

Companion project to Geni naming conventions - data entry.

If you are prepared and want to be part of this project, please register as a collaborator here ;-).

Possible objectives to try and achieve in finding guidelines on how to set profiles using the naming fields:

We want our fields to be:

• Genealogically relevant
• Historically relevant
• Reduce effort and time spent on maintenance and merges
• Easy to use
• As Accurate and legible as possible accross borders and history

Suggested order in which to address fields in respect of naming convention decisions in order of difficulty expected on finding agreement on how to use specific fields:

1. Name at Birth
2. Prefix
3. First Name
4. Middle Name
5. Suffix
6. Last name
7. Display name
8. AKA & About me. (These seperated out as they in many ways depends on the decisions on how to use the other fields.)

Requirements

Test case 1 ;-)

First name: Jennifer Legal Middle name: Lynn Birth: Young M1: Howe M2: Rowe M3: Hutchings Current legal surname: Forbes

• **Preferences set to Display all fields for this example***

EXAMPLE 1:

How I would set your profile for 'optimum performance' based on the current functionality of the fields:

TIP: imagine the fields had no names at all, but they function as they do today in respect of matches, display and search functionality and you want to set them to eliminate maximum errors in the merge considering that people could have a display setting any which way round.....

1. Prefix: <Blank>
2. First name: Jennifer Lynn
3. Middle name: <Blank>
4. Refer whole conversation from: http://www.geni.com/discussions/100368?msg=738619
5. Birth: Young
6. Last name: Young
7. AKA: Howe Rowe Hutchings Forbes. More usually: Howe, Rowe, Hutchings, Forbes.
8. Display name: Jennifer Lynn Forbes or <BLANK> depending on personal preference on living profiles
9. Suffix <Blank>
10. About me: Blank

EXAMPLE 2

How I would set your profile if I was to follow a genealogical approach:

1. Prefix: <Blank>
2. First name: Jennifer Lynn
3. Middle name: <Blank>
4. Last name: Young
5. Birth: Young
6. AKA: Howe Rowe Hutchings Forbes. More usually: Howe, Rowe, Hutchings, Forbes.
7. Display name: Jennifer Lynn Forbes
8. Suffix <Blank>
9. About me

EXAMPLE 3

How I would set your profile if you were used to American norm?:

1. Prefix: <Blank>
2. First name: Jennifer
3. Middle name: Lynn
4. Last name: Forbes
5. Birth: Young
6. AKA: Howe Rowe Hutchings Forbes. More usually: Howe, Rowe, Hutchings, Forbes.
7. Display name: Jennifer Lynn Forbes
8. Suffix <Blank>
9. About me

EXAMPLE 4

How I would set your profile if you followed findgrave:

1. Prefix: <Blank>
2. First name: Jennifer
3. Middle name: Lynn
4. Last name: Howe Rowe Hutchings Forbes
5. Birth: Young
6. AKA: <Blank>
7. Display name: Jennifer Lynn Forbes
8. Suffix <Blank>

More to follow.

How I Remi Pedersen, genealogists, would use the namefields when I'm using the genealogical way of writing names:

1. Prefix: <Blank>
2. First name: Jennifer Lynn
3. Middle name: <Blank>
4. Last name: Young
5. Birth: <Blank>
6. AKA: Jennifer Lynn Howe, Jennifer Lynn Rowe, Jennifer Lynn Hutchings, Jennifer Lynn Forbes
7. Display name: <Blank>
8. Suffix <Blank>

   ---

If you use comma separated names in the AKA field, chronologically, profiles will sort, search, display and source correctly, without need for a display name that over rides member preferences.

First name: Mary
Middle name: (blank) (or: nickname in quotes ‘Polly’)
Last name: Smith
Birth surname: Kent
AKA: widow Jones, widow Allen