Profiles Lookup Tables S - Z
S
Salary Class
Table Name: salary_class
Used by the Salary Class field in the Jobs table to define a salary classification for this position. Generally, a class is expressed as a salary range such as $10,000 - $40,000 or $40,001 - $60,000.
Table Layout
This lookup table conforms to the Standard Lookup Table Layout.
School Names
Table Name: school_names
Used by the School field in the School Table to identify the school or department within an institution where the constituent studied. This lookup table is also used by the Pref School and Parent Pref School fields in the Basic Data Table to indicate the closest affiliation of an alumnus or the school with which a parent wants to be identified.
Table Layout
This lookup table conforms to the Standard Lookup Table Layout.
Screener Familiarity
Table Name: screener_familiarity
Used by the Familiarity field in the Screening table to describe the degree of knowledge the screener has (or believes he has) about the constituent being screened.
Table Layout
This lookup table conforms to the Standard Lookup Table Layout.
Screener Session
Table Name: screener_session
Used by the Session field in the Screener Table to identify the session where the rating was made. Names for the sessions are defined by your institution.
Table Layout
This lookup table conforms to the Standard Lookup Table Layout.
Solicitations
Table Name: solicitations
Used by the Solicit field in the Gift Transaction and Dues Transaction Tables to identify the solicitation that generated this transaction. This code is designed to track specific mailings or solicitations to determine the effectiveness of that solicitation on different groups of constituents. In order to gain maximum effectiveness from this technique, careful consideration must be given to the assignment of the various solicitations. This may involve the assignment of different control groups which will isolate particular demographic characteristics. As this technique is used over a period of time, more effective segmentation of solicitations can result.
By recording the appropriate solicitation that generated a gift with each transaction, the system is capable of generating reports that detail the response to a particular mailing or solicitation. An example might be that two different letters of solicitation might be written for the same campaign, one with a nostalgic theme and the other with a financial theme. By assigning different codes for the two letters, you would be able to analyze which of these approaches produced a better response from LYBUNT women over fifty years old, LYBUNT men over fifty years old, LYBUNT women under fifty years old and LYBUNT men under fifty years old, etc.
Table Layout
The set of fields that are used in the Solicitations lookup table (the table layout) differs from any other lookup table. The fields are described in the topic, Solicitations layout.
Source Types
Table Name: source_types
Used by the Source field in all tables to indicate the source for this information. Examples might be an immediate relative, non immediate relative, media, business associate, etc. This is useful in evaluating the information and need for verification.
Alternately, this field could also be used to indicate whether the information in the row belongs to the husband or wife, if your institution uses the technique of combing spouses on one ID.
Required Entries
You may add entries to this lookup table but should not change these codes and values.
| Code | Value |
|---|---|
|
blast |
Blast Email |
Table Layout
This lookup table conforms to the Standard Lookup Table Layout.
Stewardship Type
Table Name: stewardship_type
Used by the Stewardship field in the Proposal Table to identify the reporting cycle to be used throughout the stewardship period. You may want to report to the donor or the estate on an annual, semi-annual, monthly, etc. basis.
Table Layout
This lookup table conforms to the Standard Lookup Table Layout.
T
Table Groups
Table Name: table_groups
Used by the Group field in any lookup table to determine valid entries that may be recorded in the Group field of those lookup tables for the purpose of sorting or categorizing entries within a lookup table. This lookup table includes some values for specific lookup tables that may not be deleted. Additions may be made to this lookup table.
Required Entries
This lookup table is a collection of the values and codes used by other lookup tables in the Group field. Those used by lookup tables in the Events World only are shown in bold.
| Code | Value | Use |
|---|---|---|
|
$ |
$ |
Used by Memory Names to indicate the desired formatting of the data. |
|
C |
Corporation |
Used by Constituent Type to indicate the type of Basic Data display and maintenance templates to be used for that entry. |
|
clos |
Closed |
Used by Gift and Dues Batch Numbers to indicate the status of the batch. |
|
desc |
Descriptor |
Used by Memory Names to indicate the desired formatting of the data. |
|
F |
Foundation |
Used by Constituent Type to indicate the type of Basic Data display and maintenance templates to be used for that entry. |
|
for |
Non-USA |
Used by Countries to flag countries other than the USA. |
|
no |
No Format |
Used by Memory Names to indicate the desired formatting of the data. |
|
open |
Open |
Used by Gift and Dues Batch Numbers to indicate the status of the batch. |
|
rbio |
Biographical |
Used by Report Groups to categorize a group for the Biographical library of templates. |
|
rcomp |
Comparison |
Used by Report Groups to categorize a group for the Biographical library of templates. |
|
rdaily |
Daily |
Used by Report Groups to categorize a group for the Biographical library of templates. |
|
revent |
Event |
Used by Report Groups to categorize a group for the Biographical library of templates. |
|
rfin |
Financial & Giving Reports |
Used by Report Groups to categorize a group for the Financial library of templates. |
|
rmail |
Mailing Reports |
Used by Report Groups to categorize a group for the Mailing library of templates. |
|
rmemb |
Membership Reports |
Used by Report Groups to categorize a group for the Membership library of templates. |
|
rpldg |
Pledge Reports |
Used by Report Groups to categorize a group for the Pledge library of templates. |
|
rtrack |
Prospect Tracking Reports |
Used by Report Groups to categorize a group for the Prospect Tracking library of templates. |
|
rquery |
Search Query |
Used by Report Groups to categorize a group of saved Search Results. |
The following Table Groups required entries are used by the Events World Other Info lookup table to indicate the kind of Other Info data table, and the field within that table that will use the entry.
| Code | Value | Other Info Data Table | Other Info Data Table Field that Uses Entries with This Group Code |
|---|---|---|---|
|
av |
Audio Video Needs |
Audio Visual Needs |
oinfotype1 |
|
av2 |
Audio Video Needs 2 |
Audio Visual Needs |
oinfotype2 |
|
av3 |
Audio Video Needs 3 |
Audio Visual Needs |
oinfotype3 |
|
av4 |
Audio Video Needs 4 |
Audio Visual Needs |
oinfotype4 |
|
lodg |
Lodging |
Lodging |
oinfotype1 |
|
lodg2 |
Lodging 2 |
Lodging |
oinfotype2 |
|
lodg3 |
Lodging 3 |
Lodging |
oinfotype3 |
|
lodg4 |
Lodging 4 |
Lodging |
oinfotype4 |
|
spec |
Special Needs |
Special Needs |
oinfotype1 |
|
spec2 |
Special Needs 2 |
Special Needs |
oinfotype2 |
|
spec3 |
Special Needs 3 |
Special Needs |
oinfotype3 |
|
spec4 |
Special Needs 4 |
Special Needs |
oinfotype4 |
|
tourn |
Tourney Needs |
Tourney Needs |
oinfotype1 |
|
tourn2 |
Tourney Needs 2 |
Tourney Needs |
oinfotype2 |
|
tourn3 |
Tourney Needs 3 |
Tourney Needs |
oinfotype3 |
|
tourn4 |
Tourney Needs 4 |
Tourney Needs |
oinfotype4 |
|
trans |
Transportation |
Transportation |
oinfotype1 |
|
trans2 |
Transportation 2 |
Transportation |
oinfotype2 |
|
trans3 |
Transportation 3 |
Transportation |
oinfotype3 |
|
trans4 |
Transportation 4 |
Transportation |
oinfotype4 |
Major Gift Display
Millennium Drive provides an improved user experience for viewing Millennium data. Data is gathered from Biographical, Giving, Prospect Management, and from the Events world, and presented for viewing and analysis in a variety of ways.
Touch Points is a Constituents page in Millennium Drive. It is a timeline graph and listing of a constituent's interactions with your organization
In data dictionary language:
- relisa.table_mgo = 'Y'
- relisagrp.table_mgo = 'Y'
- relwhose.table_mgo = 'Y'
- relwhogrp.table_mgo = 'Y'
Table Layout
This lookup table varies from the Standard Layout. See Table Groups.
Task Status
Table Name: task_status
Used by the Status field in the Task table to describe the status and progress of the assignment that is described in the Task row
Required Entries
If certain conditions are met and settings are chosen, A user's Microsoft Outlook Tasks and Calendar can be updated when Tasks are entered in Millennium, and visa-versa. The following lookup table entries are required to facilitate the correct mapping between Millennium's Task Status and Outlook's Status. If other codes are used, then Millennium will set the Outlook status to Not Started when updating Outlook with Millennium data. Conversely, if codes other than these required entries are found in Millennium's Task Status field, then Outlook will not overwrite the Millennium Task Status field with the Status as it is set in Outlook.
You may add entries to this lookup table but should not change these codes and values.
| Code | Value |
|---|---|
|
0 |
Not Started |
|
1 |
In Progress |
|
2 |
Completed |
|
3 |
Waiting on Someone Else |
|
4 |
Deferred |
Table Layout
This lookup table conforms to the Standard Lookup Table Layout.
Tasks Type
Table Name: tasks_type
Used by the Type field in the Tasks table to classify the nature of the Task being described in the row. These classifications are defined by your institution but might include such things as: follow-up call, dinner invitation, campus visit, proposal presentation, etc. When a Task is linked to an Action, the Task Type field will default to the value of the Action Type field. For this reason, each entry in the Action Types lookup table should have an equivalent entry in the Tasks Type lookup table. And, if an entry in the Actions Type lookup table is marked Inactive, then the equivalent entry in the Tasks Type table should be marked Inactive as well.
Major Gift Display
Millennium Drive provides an improved user experience for viewing Millennium data. Data is gathered from Biographical, Giving, Prospect Management, and from the Events world, and presented for viewing and analysis in a variety of ways.
Touch Points is a Constituents page in Millennium Drive. It is a timeline graph and listing of a constituent's interactions with your organization
Table Layout
This lookup table varies from the Standard Layout. See Tasks Type Lookup Table Layout.
Tender
Table Name: tender
Used by the Tender field in the Gift and Dues Transaction Tables to describe the method by which the gift was received (cash, securities, gift in kind, barter, real-estate, etc.)
Required Entries
You may add entries to this lookup table but should not change these codes and values.
| Code | Value |
|---|---|
|
bank |
Bank Draft |
|
c |
Cash (recommended) |
|
cc |
Credit Card |
|
gik |
Gift in Kind |
|
sec |
Securities |
|
pp |
Personal Property (recommended) |
|
rp |
Real Property (recommended) |
Table Layout
This lookup table conforms to the Standard Lookup Table Layout.
Territory
Table Name: territory
This lookup table is used by the Territory field in the ZIP Code lookup table and in the Countries table. The ZIP Code or Countries tables allows you to classify your constituency into Districts, Regions, Territories, and Zones, based on their ZIP Codes or their non-USA status. These classifications are then automatically entered by the system into the constituent's Address record based on the ZIP Code entry in use when the Address row is for a USA address and a ZIP Code is entered. They are automatically entered based on the Countries entry in use when the Address is for a non-USA address. The Territories that you want to use in the ZIP Code table or Countries lookup tables must first be defined in the Territories lookup table. Territories may be defined in any way that your institution desires.
Table Layout
This lookup table conforms to the Standard Lookup Table Layout.
Titles
Table Name: titles
Used by the Title field in the Names row to standardize or specify the titles that may be used for the constituent's name.
Table Layout
This lookup table varies slightly from the standard layout. See Titles Lookup Table Layout.
Transaction Class
Table Name: transaction_class
The Giving and Dues Transaction tables include a field, Classification 1 and it may be used to classify transactions in some way that is specific to your institution and that is not already available in another field in the table. These fields use the Transaction Class lookup table. You may define the entries in any way that you choose.
Table Layout
This lookup table conforms to the Standard Lookup Table Layout.
Transaction Class 2
Table Name: transaction_class2
The Giving and Dues Transaction tables include a field, Classification 2 and it may be used to classify transactions in some way that is specific to your institution and that is not already available in another field in the table. These fields use the Transaction Class2 lookup table. You may define the entries in any way that you choose.
Table Layout
This lookup table conforms to the Standard Lookup Table Layout.
Z
ZIP Codes
Table Name: zipcodes
Used by the ZIP Code field in the Address Table. The standard entries in this lookup table are created by the conversion of data supplied by the USPS. These entries are provided to you at the time of your Millennium software installation and they include information about US ZIP Codes (only).
At the time that Millennium is installed, each ZIP Code entry includes data in the fields: ZIP Code, City, County, State, Time Zone, Longitude and Latitude. Your institution may define and add data to the fields: District, Region, Territory, and Zone, for the purpose of segmenting your constituency geographically. To do this, you must first define the entries you want to use in the Districts, Regions, Territories or Address Zones lookup tables.
Because this is an extremely large lookup table, it does not behave in exactly the same way that most Millennium tables do, either in data maintenance or in Lookup Table Maintenance.
When performing data maintenance on a constituent's Address information using the ZIP Code field, you will see that the table entries do not appear in the Address maintenance form as a pull down list. To use a ZIP Code, you must enter the code as if it were free text. The system will lookup that entry and will fill in the additional fields that are associated with the ZIP Code, into the Address row.
When performing data maintenance on the ZIP Code lookup table itself (through the Tools World) and you click on the ZIP Code listing, you will not immediately be given a display page containing all the entries (more than 43,000!) To enhance the speed of the display, you must point the system to your general field of interest! This may be done using the Zipcodes Options form. It will allow you to either enter at least three digits of the ZIP Code or enter a State and at least partial City information. Then, you may choose whether you want the display to show you the entries in order based on the Zipcode or on the State and City. When all options have been set, you may click on OK to access and display the table entries. From that display, the table conforms to standard data entry and maintenance behavior.
When creating an Address row that indicates the Country as being USA, if any of the fields that are associated with the ZIP Code table (City, State, ZIP Code, County, Time Zone, Longitude, Latitude, Region, District, Territory, or Address Zone) are left blank in the Address Insert form, then the system will automatically fill them in, using the data in the ZIP Code Lookup table. It will not overwrite any data that you entered on the current form, even if it differs from that in the lookup table.
When performing Address updates, if you access the update form and edit the ZIP Code field and manually edit any of the other associated ZIP Code fields at the same time, the system will update any of the "old" data (that you did not edit manually) in the row to conform to the table entry. It will not overwrite any data that you manually entered on the current update form.
Table Layout
This lookup table has a layout that is specific to this table. See ZIP Code Lookup Table Layout.