Names
Each constituent may have an unlimited number of rows in the Name table, each indicating a way in which that constituent might be addressed. Each row is assigned a Name Type to distinguish its use. Generally, Name Types would include a Preferred Name, Formal Name, Maiden Name, and any number of personal salutations. They might also include Nicknames, Stage Names, Pen Names, or any other kind of name you want to define in the Name Type lookup table.
Within each Name row, there are individual fields for the First, Middle, and Last Name, the Title, and Suffix. When you enter data in those columns, the system will use that data to construct other fields in the same row. Each of those fields shows a particular variation of the name, used in differing situations. You may override any of the system-generated name fields if you or the constituent prefer a different form. When doing so, the override check box will become automatically checked for you. These system-generated fields are:
- Formatted Name - This is the constituent's full name, as it might appear on an address label. (Mr. John G. Smith, Jr.)
- Plural Name - This is the combined form of the constituent and his/her constituent spouse's formatted name. Both parties must have a Name row of the same Type in order for the system to generate this name. (Mr. and Mrs. John G. Smith, Jr.)
- Salutation Name - This is the formal salutation for the constituent's name, as it might appear in the salutation of a letter. (Mr. Smith)
- Combined Salutation Name - This is the combined form of the constituent and his/her constituent spouse's salutation name. Both parties must have a Name row of the same Type in order for the system to generate this name. (Mr. and Mrs. Smith)
The System Generated Names topic discusses the rules that the system uses to generate these name fields.
Each name row may be included or excluded when the system is searching for a constituent name in the Profile world, looking for a constituent whose information you want to display. For example, if a constituent's Name row has a Lookup field equal to Y (Yes) on both their Preferred and Maiden name types, then their information can by accessed by entering either name in the search form. This is especially useful if you only know one of the names. This also helps to prevent the creation of duplicate name rows. When you enter a new name row, the Lookup name flag defaults to Y; uncheck if you want exclude the name row from any constituent name searches.
Note: Millennium system administrators or the database administrator can configure audit logging for the Names data table. For more information, see Audit Log.
Preferred Name
While the system does allow a constituent to have multiple preferred names, or no preferred name at all, one and only one name row should be designated as the Preferred Name and that name is the one that will be used by the system in all default situations.
If your system administrator has enabled the Check Preferred Names system option and you attempt to enter more than one preferred name, you will receive a warning. And, if a constituent does not yet have a preferred name and you enter a new name record and you do not mark it preferred (or if you remove the preferred name designation from an existing name, leaving a constituent with no preferred name), you will receive a warning.
Names for Couple Constituents
Some institutions track the information for a married couple as one constituent in the Millennium database. This is indicated by a Basic Data Gender of 'C'. When creating Name rows in this case, you may use the standard Name Types, Husband Preferred and Wife Preferred to track the names of the two people involved. If those two name types are used for a constituent with a Gender of 'C', and if no Name row already exists with a Type of Preferred, then the system will automatically create that Name row, and use the information from the two individual Names to create the Preferred Name row for the couple.
Important! Once the Preferred Name row has been generated by the system in this way, it must be updated manually. It will not automatically be updated if the Husband Preferred or Wife Preferred Name rows are edited.
Event Name
If your institution makes use of the Event module of Millennium, you may choose to create a Name row of the type 'Event Name'. If such a name is present at the time that the constituent is registered as an Event Guest, the formatted name from the Event Name row will be used as the default for the Name Tag Line 1 text box in the Event Guest insert form. If no Event Name exists, the Preferred name will be used. The Preferred name is always used as the default for the other name information on the Event Guest form. The default information in the Event Guest form can be edited before the row is inserted. Edits made to that Name information in the Event Guest row are not reflected in the Name row in the Profiles World.
Contact Info and Name
If a constituent is maintained as a contact in a Contact Info row, his or her preferred name is stored in the Contact Info data table. If any updates are made to the title, first, middle, last, and/or suffix preferred name fields, the name fields in the Contact Info table will be automatically updated as well.
Name Field Descriptions
Name data is stored in the name data table. The following fields are included. The field labels and non-displaying designations that are listed here are those that the system uses by default. If you want to override these default settings, you must customize your display definition.
Note: Custom fields are included in the data table, and are available for any purpose that you want to define. These fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms.
|
Field Name Field Label |
Lookup Table |
Type SQL/Oracle Length [Default] {Check} |
Description |
|---|---|---|---|
|
namekey non-displaying |
none |
numeric/number 13,0 [0]
|
The primary key field for all rows in all tables. This field holds a permanent "time stamp" of the precise time and date the row was created. This uniquely identifies a row within the table. The field is indexed with the tag pk_name. It is also used to link Non-Constituent Name records to Relation records. (system field) |
|
nameid non-displaying |
none |
char 10
|
This field holds the ID number of the constituent who owns this row providing a link between this row and all others in all other tables which also belong to the same constituent. (system field) |
|
namedoc non-displaying |
none |
char 1 ['N']
|
This field holds a Y/N flag to indicate the existence of a linked document for this row. (system field) |
|
namedate no label |
none |
datetime/date
[getdate()]
|
The date that this name was last updated. This field is automatically entered by the system. (system field) |
|
nameuserid no label |
none |
varchar/varchar2 30 [suser_sname()]
|
The User ID of the operator that last edited this name. It is automatically entered by the system. (system field) |
|
nameugroup non-displaying |
none |
char 1 ['Z']
|
This field holds the Group letter that was associated with the User ID of the operator who last edited this row. (system field) |
|
no label |
none |
char 55
|
The last name of the constituent. This field should be used for corporate or foundation names. |
|
no label |
none |
char 30
|
The first name of the constituent. |
|
no label |
none |
char 30
|
The middle name of the constituent. |
|
no label |
none |
char 30
|
The suffix of the constituent's name. When displaying the name, the suffix will be separated from the last name by a comma and a space, unless that suffix is a Roman numeral, in which case the comma is omitted. When constructing the system-generated Salutation, Plural, and Plural Salutation names, the following data will trigger the use of the Dr. title instead of the suffix. M.D. |
|
Type |
char 6 [' ']
|
Indicates the type of name being recorded (for example, Preferred, Formal, Maiden). |
|
|
non-displaying |
none |
char 30
|
This field is constructed from the contents of the First, Middle and Last Name and Suffix fields according to the set of rules that follow. This field is primarily used for alphabetizing lists in reports because it nullifies inconsistencies that can occur due to the variations of names. (duPont, van Patton, McDonald, Mc Donald, etc.) The system constructs the field in the following way: 1. Convert all letters in namefirst, namemiddle, namelast, and namesuffix to uppercase. 2. Remove any characters from the same fields that are not Blank, slash, semicolon, characters "0" through "9", or characters "A" through "Z". 3. Trim any spaces off the namelast field and follow it with a forward slash. Directly after the forward slash, add the namefirst field followed by a space and the namemiddle field. Do not follow the namefirst field with a space if the namemiddle field is blank. 4. If the namesuffix field is blank, the formatting process is finished. If it is not blank, then follow the namefirst, namemiddle combination with a semicolon and append the namesuffix. Do not put a space between the semicolon and namesuffix. (system field) |
|
namekeyflg non-displaying |
none |
char 1 [N] {'N' or 'Y'} |
Indicates whether you want this name row to be available for use in a lookup query when accessing the constituent's information. |
|
namesource Source |
char 6 [' ']
|
Indicates the source of the information contained in this row. This field is driven by the Sources lookup table. |
|
|
namesndex non-displaying |
none |
char 6
|
An algorithm based on phonetics is applied to the Smashed Name field to "convert" the name to a soundex code. This code is used to identify similar sounding names to be displayed in the Name Lookup screen. (system field) |
|
namepoint non-displaying |
none |
numeric/number 10,0
|
This system-assigned field is no longer used or supported. (system field) |
|
namedflag non-displaying |
none |
char 1 ['N'] {'D' or 'N' or 'Y'} |
This field is a one character flag that is set to indicate that the constituent has a Death or Disbanded row. This flag triggers the appearance of the word DECEASED for individuals, and DISBANDED for corporations or foundations in the Name Lookup screen, the Title bar, or cross references. (system field) |
|
nameformn no label |
none |
varchar/varchar2 110
|
This field will contain the formatted configuration of the name information in this row. The formatted name is system-generated using a set of Name Formatting rules. You may override the default name form and manually enter a specific alternate name form in for this field. (system field) |
|
namefnum non-displaying |
none |
char 2 ['01'] {'01'} |
The file (table) number for the Name table. (system field) |
|
namecrdate non-displaying |
none |
datetime/date
[getdate()]
|
This field holds the date that this row was created. It may not be edited. (system field) |
|
nametitle no label |
char 30
|
Indicates the honorific title associated with this name row (for example, Mr., Ms., Dr., Reverend). |
|
|
namecomm no label |
none |
varchar/varchar2 4000
|
A free text Comment that may be entered and displayed with this Name row only. |
|
nameplural no label |
none |
varchar/varchar2 110
|
This field is designed to hold a combined, formatted name for the constituent and spouse. During data entry, you may accept the system-generated name for this field, or you may override that form of the name and type in the combined form that you (or the constituents) prefer. If the constituent has a Spouse (sp) relationship, then this field will hold a combined, formatted form of the names of the two constituents. During data entry, you may accept the system-generated name for this field, or you may override that form of the name and type in the combined form that you (or the constituents) prefer. If the constituent has a Life Partner (lp) relationship, then this field will hold a combined, formatted name, created by using the formatted names of the two constituents joined by 'and' (Mr. John Smith and Mr. Thomas Jones). |
|
nameflag1 Override (on maintenance form) |
none |
char 1 [N] {'Y' or 'N'} |
This field acts as a flag to the system as to whether the system should allow the user-entered data to override the system-generated nameformn (if flag is Y), or if there is no data for an override (if flag is N). |
|
nameflag2 Override (on maintenance form) |
none |
char 1 [N] {'Y' or 'N'} |
This field acts as a flag to the system as to whether the system should allow the user-entered data to override the system-generated nameplural (if flag is Y), or if there is no data for an override (if flag is N). |
|
namesalut Salutation Name |
none |
char 110
|
This field will contain the last name salutation form (Mr. Smith) of the name information in this row. The salutation name is system-generated using a set of Name Formatting rules. You may override the default name form and manually enter a specific alternate name form in this field. (system field) |
|
namecsalut Combined Salutation |
none |
char 110
|
This field is designed to hold a combined, last name salutation for the constituent and spouse. During data entry, you may accept the system-generated name for this field, or you may override that form of the name and type in the combined form that you (or the constituents) prefer. If the constituent has a Spouse (sp) relationship, then the system will generate a combined, last name salutation form of the names of the two constituents (Mr. and Mrs. Smith). If the constituent has a Life Partner (lp) relationship, then this field will hold a combined, last name salutation form, created by using the salutation names of the two constituents joined by 'and' (Mr. Smith and Mr. Jones). |
|
nameflag3 Override (on maintenance form) |
none |
char 1 ['N'] {'Y' or 'N'} |
This field acts as a flag to the system as to whether the system should allow the user-entered data to override the system-generated namesalut (if flag is Y), or if there is no data for an override (if flag is N). (system field) |
|
nameflag4 Override (on maintenance form) |
none |
char 1 ['N'] {'Y' or 'N'} |
This field acts as a flag to the system as to whether the system should allow the user-entered data to override the system-generated namecsalut (if flag is Y), or if there is no data for an override (if flag is N). (system field) |
|
namedate1 |
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. |
|
namedate2 |
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. |
|
namemny1 |
none |
money/number (19,4)/(16,2)
|
This custom field may be defined and used by your institution to track any monetary information associated with this data row. |
|
namemny2 |
none |
money/number (19,4)/(16,2)
|
This custom field may be defined and used by your institution to track any monetary information associated with this data row. |
|
namenum1 |
none |
numeric/number 10, 0
|
This custom field may be defined and used by your institution to track any numeric information associated with this data row. |
|
namenum2 |
none |
numeric/number 10, 0
|
This custom field may be defined and used by your institution to track any numeric information associated with this data row. |
|
nameyesno |
none |
char 1 ['N'] {'N' or 'Y'} |
This custom field may be defined and used by your institution to flag this data row for any purpose. |
|
namelook1 |
char 6
|
This custom field may be defined and used by your institution to track any lookup table driven information associated with this data row. |
|
|
namelook2 |
char 6
|
This custom field may be defined and used by your institution to track any lookup table driven information associated with this data row. |
|
|
namelook3 |
char 6
|
This custom field may be defined and used by your institution to track any lookup table driven information associated with this data row. |
|
|
nametext |
none |
varchar/varchar2 500
|
This custom field may be defined and used by your institution to track any free text information you want to associate with this data row. |
|
namepend non-displaying |
none |
char 1 ['N']
|
This field is a flag to indicate that this data row has linked information in the 'pending' Names table as a result of data entry by the constituent via the Online Constituent Directory. That linked info is pending incorporation into this data row. (system field) |
|
namepubfl non-displaying |
none |
char 1 ['N'] {Not Null} |
This field is a flag to indicate whether this data row will or will not be available for online publishing. This flag will be applicable when the Options for Publishing Data for the Name table are set to 'Published by Consent'. Otherwise, the corepub01 column flag in the Basic Data table will be used. |
|
nameupkey non-displaying |
none |
numeric/number 13,0
|
This field holds the Timekey of the pending data row that may be updated from the name_pending table. |
|
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. |
|
|
namedate4 |
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. |
|
namedate5 |
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. |
|
namedate6 |
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. |
|
namedate7 |
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. |
|
namedate8 |
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. |
|
namedate9 |
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. |
|
namedte10 |
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. |
|
namedte11 |
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. |
|
namedte12 |
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. |
|
namemny3 |
none |
money/number (19,4)/(16,2)
|
This custom field may be defined and used by your institution to track any monetary information associated with this data row. |
|
namemny4 |
none |
money/number (19,4)/(16,2)
|
This custom field may be defined and used by your institution to track any monetary information associated with this data row. |
|
namemny5 |
none |
money/number (19,4)/(16,2)
|
This custom field may be defined and used by your institution to track any monetary information associated with this data row. |
|
namemny6 |
none |
money/number (19,4)/(16,2)
|
This custom field may be defined and used by your institution to track any monetary information associated with this data row. |
|
namemny7 |
none |
money/number (19,4)/(16,2)
|
This custom field may be defined and used by your institution to track any monetary information associated with this data row. |
|
namemny8 |
none |
money/number (19,4)/(16,2)
|
This custom field may be defined and used by your institution to track any monetary information associated with this data row. |
|
namemny9 |
none |
money/number (19,4)/(16,2)
|
This custom field may be defined and used by your institution to track any monetary information associated with this data row. |
|
namemny10 |
none |
money/number (19,4)/(16,2)
|
This custom field may be defined and used by your institution to track any monetary information associated with this data row. |
|
namemny11 |
none |
money/number (19,4)/(16,2)
|
This custom field may be defined and used by your institution to track any monetary information associated with this data row. |
|
namemny12 |
none |
money/number (19,4)/(16,2)
|
This custom field may be defined and used by your institution to track any monetary information associated with this data row. |
|
namenum3 |
none |
numeric/number 10, 0
|
This custom field may be defined and used by your institution to track any numeric information associated with this data row. |
|
namenum4 |
none |
numeric/number 10, 0
|
This custom field may be defined and used by your institution to track any numeric information associated with this data row. |
|
namenum5 |
none |
numeric/number 10, 0
|
This custom field may be defined and used by your institution to track any numeric information associated with this data row. |
|
namenum6 |
none |
numeric/number 10, 0
|
This custom field may be defined and used by your institution to track any numeric information associated with this data row. |
|
namenum7 |
none |
numeric/number 10, 0
|
This custom field may be defined and used by your institution to track any numeric information associated with this data row. |
|
namenum8 |
none |
numeric/number 10, 0
|
This custom field may be defined and used by your institution to track any numeric information associated with this data row. |
|
namenum9 |
none |
numeric/number 10, 0
|
This custom field may be defined and used by your institution to track any numeric information associated with this data row. |
|
namenum10 |
none |
numeric/number 10, 0
|
This custom field may be defined and used by your institution to track any numeric information associated with this data row. |
|
namenum11 |
none |
numeric/number 10, 0
|
This custom field may be defined and used by your institution to track any numeric information associated with this data row. |
|
namenum12 |
none |
numeric/number 10, 0
|
This custom field may be defined and used by your institution to track any numeric information associated with this data row. |
|
namechk1 |
none |
char 1 ['N'] {'N' or 'Y'} |
This custom field may be defined and used by your institution to flag this data row for any purpose. |
|
namechk2 |
none |
char 1 ['N'] {'N' or 'Y'} |
This custom field may be defined and used by your institution to flag this data row for any purpose. |
|
namechk3 |
none |
char 1 ['N'] {'N' or 'Y'} |
This custom field may be defined and used by your institution to flag this data row for any purpose. |
|
namechk4 |
none |
char 1 ['N'] {'N' or 'Y'} |
This custom field may be defined and used by your institution to flag this data row for any purpose. |
|
namechk5 |
none |
char 1 ['N'] {'N' or 'Y'} |
This custom field may be defined and used by your institution to flag this data row for any purpose. |
|
namechk6 |
none |
char 1 ['N'] {'N' or 'Y'} |
This custom field may be defined and used by your institution to flag this data row for any purpose. |
|
namechk7 |
none |
char 1 ['N'] {'N' or 'Y'} |
This custom field may be defined and used by your institution to flag this data row for any purpose. |
|
namechk8 |
none |
char 1 ['N'] {'N' or 'Y'} |
This custom field may be defined and used by your institution to flag this data row for any purpose. |
|
namechk9 |
none |
char 1 ['N'] {'N' or 'Y'} |
This custom field may be defined and used by your institution to flag this data row for any purpose. |
|
namechk10 |
none |
char 1 ['N'] {'N' or 'Y'} |
This custom field may be defined and used by your institution to flag this data row for any purpose. |
|
nametxt1 |
none |
varchar/varchar2 255
|
This custom field may be defined and used by your institution to track any free text information you want to associate with this data row. |
|
nametxt2 |
none |
varchar/varchar2 255
|
This custom field may be defined and used by your institution to track any free text information you want to associate with this data row. |
|
nametxt3 |
none |
varchar/varchar2 255
|
This custom field may be defined and used by your institution to track any free text information you want to associate with this data row. |
|
nametxt4 |
none |
varchar/varchar2 255
|
This custom field may be defined and used by your institution to track any free text information you want to associate with this data row. |
|
nametxt5 |
none |
varchar/varchar2 255
|
This custom field may be defined and used by your institution to track any free text information you want to associate with this data row. |
|
nameadesrc non-displaying |
char 30
|
If this row is created or updated from data that originally came from the name_pending table, then this field will hold information about the data's import source. Data from the Online Constituent Directory will have a source of Online Directory. Data from Soft Edit users will have a source of Soft Edit. Data whose import source is the ADE Import Tool can be assigned a value (other than Online Directory or Soft Edit) from the ade_source lookup table by the user who executes the utility, or the source can be blank. |
Indices - Name
| Index | Primary | Foreign | Unique | Fields | Sort |
|
pk_name |
Y |
|
Y |
namekey |
ASC |
|
name02 |
Y |
Y |
|
nameid |
ASC |
|
name03 |
|
|
|
nametype |
ASC |
|
name04 |
|
|
|
namesmashd |
ASC |
|
name05 |
|
|
|
namesndex |
ASC |
|
name06 |
|
|
|
namedate |
ASC |
|
name07 |
|
|
|
nametext |
ASC |