Basic Data
The Basic Data row is the fundamental information associated with a constituent. Every constituent will have one and only one Basic Data row. The creation of that row is the action that defines a constituent on the system. The information that is displayed from Basic Data will vary depending on whether the constituent is an Individual, a Corporation, or an Organization. Therefore, there are three standard "versions" of the Basic Data row. While all Basic Data table rows contain the same set of data columns, some of those fields will be used by all three types, some by two of the three, and some by only one type of constituent.
For example, the Basic Data includes a field for marital status. That field will be unused in Basic Data rows belonging to corporations or foundations. It will not appear in the data maintenance forms (standard) or in the display (standard) of the Basic Data for those constituents.
These variations are controlled by the Group field from the Constituent Type lookup table entry that you choose for the data row. Once the Basic Data row is created, if the Constituency Type is edited in a way that changes the constituent from a person to a corporation or other (based on the information in the Group field of the entries in the Constituent Type lookup table), or vice versa, the system will automatically edit the Basic Data row and remove the data from fields that do not apply to the new Constituent Type.
If the type is changed from Person to Corporation or Other, those fields are: coresex, coremaritl, corechflag, corechnum, corebirthd, coressnum, coreparpyr, coreparsch, coreprefyr, coreprfsch, coreethnic, corebcntry, coregrnpyr, corebrthyr, corebrthmn, corebrthdy.
If the type is changed from Corporation or Other to Person, those fields are: coreindust (Corporation only), corefntype (Foundation/Organization Only), coretotemp, corekwnemp, corealmemp, corerlkey1, corerlkey2, corecorpid, coreallsub, corekwnsub, corepropm1, corepropd1, corepropm2, corepropd2, corepropm3, corepropd3, coremduem1, coremdued1, coremduem2, coremdued2, coremduem3, coremdued3, coremduem4, coremdued4, coremnamt1, coremxamt1, coremrat1, coremnamt2, coremrat2, coremnamt3, coremxamt3, coremrat3, matchcomm, coremtchid.
Note: Millennium system administrators or the database administrator can configure audit logging for the Basic Data table. For more information, see Audit Log.
Basic Data - Individuals
In general, the Basic Data row for Individuals contains fields for which there is but one set of information per constituent, such as birthdate, gender, marital status, birth country, etc. In addition, while the Education table may hold several rows of information about actual attendance and degrees held, the Basic Data holds information about the year and school that the constituents prefer as their primary association, either for themselves or for their children.
You may associate any number of Citizenship rows with a Basic Data row belonging to an Individual. These may be used to track information on nationality, citizenship, passports, visas, etc.
You can attach, or link, multiple Attribute rows to a Basic Data row. These Attributes always display with the Basic Data row to which they are attached. And if the Display Linked Attributes in the Attribute Display User Option is checked, they will also display with the constituent's other attributes. These linked Attributes might be used to record additional constituency types that apply to the constituent (an alumnus who is also a parent, for example).
You can also attach a photo to a constituent's basic data form (see Attachments).
The Data Maintenance, Link New to Existing and Data Maintenance, Link Existing to Existing topics discuss the creation and maintenance of linked Attributes in more detail.
An individual's Marital Status field is automatically updated when certain other data is entered in Millennium.
- If a spousal Relationship is created, the Marital Status for both constituents is set to Married.
- If a spousal Relationship is changed to Divorced Spouse/Divorced Spouse, the Marital Status for each is set to Divorced.
- If a spousal non-constituent Relationship is changed to Surviving Spouse/Deceased Spouse, the Marital Status for the constituent is set to Surviving Spouse.
- If a Death data row is created for either of a spousal constituent pair, the Marital Status is set to Surviving Spouse/Deceased Spouse, appropriately.
Basic Data - Corporations
The Basic Data for corporations includes information relevant to the corporate constituent. Information can be maintained about the parent corporation, subsidiaries, number of employees, proposal deadlines, and matching information.
When inputting a parent corporation, the system automatically creates the appropriate parent corporation/subsidiary relationship for the parent corporation and the subsidiary. In doing this, the system links the parent corporation and subsidiary Basic Data rows. On the subsidiary's Basic Data display, the name of the parent corporation appears as a hyperlink and executing that jump takes you to the Basic Data for the parent corporation. If a parent corporation name on an existing Basic Data row is removed, then the system will automatically delete the relevant parent corporation/subsidiary relationship.
When an Employment row is created for an individual that identifies a constituent corporation as the employer, the Known Employees field in the corporation's row is updated. In addition, if the CAE Category is 'A' (Alumni) on the Basic Data row for the individual, then the Alumni Employee field will also be incremented in the Basic Data row belonging to the corporation. Note that "Known Employees" refers to those employees who also have a constituent row in Millennium and therefore are "known" to the system. Alumni Employees are the subset of the Known Employees who are categorized as Alumni by their CAE Category.
Matching Information
Information about a corporation's matching policies is maintained in the Basic Data row. When the information is present and another constituent identifies the corporation as an employer, this matching information is available for use in determining whether to prompt for the creation of a matching giving transaction, and the calculation of the default amount for such a transaction.
Matching information may be handled in one of the following ways:
- You may manually enter data regarding the corporation matching policies, just as you enter any other data.
- If the corporation uses a foundation or other corporate entity to transmit and administer matching gifts, you may link from the corporation to the ID number of the actual matching entity (another constituent in the database) as the 'Match Through ID'. The Match Through constituent will be shown as a hyperlink in the display. If the Pull Matching Ratios from the Corporation system option is set to No, the matching information from the actual matching entity will automatically be copied to the original, corporate constituent's Basic Data row. If the Pull Matching Ratios from the Corporation system option is set to Yes, the matching information from the matching entity will not be copied to the original, corporate constituent's Basic Data row. See coremtchid for more information and a list of the fields that will be automatically updated.
- If your institution makes use of the optional Millennium component, CorrectGM, you may link from the corporation to a matching entity in that database. If the Pull Matching Ratios from the Corporation system option is set to No, then certain of the matching information will automatically be copied to the original corporation's Basic Data. See corempkey for more information and a list of the fields that will be automatically updated.
If a link is established either via the Match Through or the CorrectGM option, AND the Pull Matching Ratios from the Corporation system option is set to No, edits that are made to the matching entity's matching information will automatically be carried over to the original constituent's Basic Data. If the Pull Matching Ratios from the Corporation system option is set to Yes, edits that are made to the matching entity's matching information will not carry over to the original constituent's Basic Data.
Up to three matching gift ratios for different gift size ranges can be maintained, along with free text data on matching guidelines. These gift ranges and the associated ratios are used to calculate a default amount for the insert form for a matching pledge based on an employee's donation. That calculation is based solely on the gift size ranges of the ratios and the amount of the original donation - not on the multitude of other possible matching policies that the corporation may have in effect. The gift size ranges must be distinct, not overlapping, except for the amounts that are the 'boundaries' for the ranges. For instance, the first range might be $0 - $1000, the second range $1000 - $5000, and the third range $5000 - $10,000. If other factors (such as the donor's employment level or the purpose of the donation) affect the expected amount of the matching pledge, the default amount should be edited when the matching pledge transaction is created.
Basic Data for corporations also includes fields to maintain up to four dates to show when a corporation pays matching gifts. There are also four fields to indicate up to four different proposal deadlines.
Basic Data - Organizations
The Basic Data for an Organization includes information relevant to a variety of kinds of organizations. Information can be maintained about a parent corporation, subsidiaries, number of employees, and proposal deadlines. Current financial data such as total assets, and expenditures can be documented.
When inputting the corporation of a corporate foundation, the system automatically creates the appropriate parent corporation/foundation relationship on the parent corporation and foundation rows. In doing this, the system links the two rows through this relationship. A click of the left mouse button on the parent corporation name hyperlink will take you to the Basic Data for the parent corporation.
When an Employment row is created for an individual that identifies a constituent foundation as the employer, the Known Employees field in the foundation's row is updated. In addition, if the CAE Category is 'A' (Alumni) on the Basic Data row for the individual, then the Alumni Employee field will also be incremented in the Basic Data row belonging to the foundation. Note that "Known Employees" refers to those employees who also have a constituent row in Millennium and therefore are "known" to the system. Alumni Employees are the subset of the Known Employees who are categorized as Alumni by their CAE Category.
Matching Information
Information about a foundation's matching policies is maintained in the Basic Data row. When the information is present and another constituent identifies the foundation as an employer, this matching information is available for use in determining whether to prompt for the creation of a matching giving transaction, and the calculation of the default amount for such a transaction.
Matching information may be handled in one of the following ways:
- You may manually enter data regarding the foundation matching policies, just as you enter any other data.
- If the foundation uses another foundation or a corporate entity to transmit and administer matching gifts, you may link from the foundation to the ID number of the actual matching entity (another constituent in the database) as the 'Match Through ID'. The Match Through constituent will be shown as a hyperlink in the display. If the Pull Matching Ratios from the Corporation system option is set to No, the matching information from the actual matching entity will automatically be copied to the original, foundation constituent's Basic Data row. If the Pull Matching Ratios from the Corporation system option is set to Yes, the matching information from the matching entity will not be copied to the original, foundation constituent's Basic Data row. See coremtchid for more information and a list of the fields that will be automatically updated.
- If your institution makes use of the optional Millennium component, CorrectGM ©, you may link from the foundation to a matching entity in that database. If the Pull Matching Ratios from the Corporation system option is set to No, then certain of the matching information will automatically be copied to the original foundation's Basic Data. See corempkey for more information and a list of the fields that will be automatically updated.
If a link is established either via the Match Through or the CorrectGM option, AND the Pull Matching Ratios from the Corporation system option is set to No, edits that are made to the matching entity's matching information will automatically be carried over to the original constituent's Basic Data. If the Pull Matching Ratios from the Corporation system option is set to Yes, edits that are made to the matching entity's matching information will not carry over to the original constituent's Basic Data.
Up to three matching gift ratios for different gift size ranges can be maintained, along with free text data on matching guidelines. These gift ranges and the associated ratios are used to calculate a default amount for the insert form for a matching pledge based on an employee's donation. That calculation is based solely on the ratio gift size ranges and the amount of the original donation - not on the multitude of other possible matching policies that the corporation may have in effect. The gift size ranges must be distinct, not overlapping, except for the amounts that are the 'boundaries' for the ranges. For instance, the first range might be $0 - $1000, the second range $1000 - $5000, and the third range $5000 - $10,000. If other factors (such as the donor's employment level or the purpose of the donation) affect the expected amount of the matching pledge, the default amount should be edited when the matching pledge transaction is created.
Basic Data for foundations also includes fields to maintain up to four dates to show when a foundation pays matching gifts. There are also four fields to indicate up to four different proposal deadlines.
CAE Category
When a Basic Data row is inserted, Millennium automatically populates the CAE Category field with the CAE that is associated with the Constituent Type that you have entered. This association is determined by the value of the table_cfae field in the Constituent Types (constituent_types) lookup table. And, if a Basic Data row is updated, and that update includes a change to the Constituent Type, Millennium will automatically update the CAE Category to the CAE that is associated with the Constituent Type via this table_cfae field.
For example, a Constituent Type of Alumni is associated with a CAE of 'Alumni'. If you insert a new constituent, with a Constituent Type of Alumni, into the database, the CAE field will auto-populate with 'Alumni'. In another example, a Constituent Type of Major Donor is associated with a CAE type of <blank>. If you update a record for a constituent with a Type of Individual and change her Constituent Type to Major Donor, the CAE field will auto-populate with a <blank>.
This behavior occurs automatically even if you have entered contradictory information for the CAE Category in the insert or update form. You may, however, override the automatic entry of the CAE Category by editing the Basic Data row once it has been created or updated. When you manually edit this field, the system will accept your inputted CAE in preference to the CAE that is associated with the Constituent Type lookup entry.
Display Death with Basic Data
If the Display Death with Basic Data system option is activated at your organization, then a constituent's Death record displays with Basic Data. If a constituent does not have a Death record, then the Death section header will not show. The Edit button menu to the left of a constituents Basic Data record lists the and items for you to use to create a new Death record for a constituent. For more information, see the System Options and Death topics.
Basic Data Field Descriptions
Basic constituent data is stored in the corebio 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. In addition, the Description will indicate whether the field is part of the default display for Individuals (I), Corporations (C), and/or Organizations (O). If you want to override these default settings, you must customize your display definition.
Field Name Field Label |
Lookup Table |
Type SQL/Oracle Length [Default] {Check} |
Description Utilized by Basic Data rows belonging to Individuals (I), Corporations (C), and/or Organizations (O). |
---|---|---|---|
corekey non-displaying |
none |
numeric/number 13,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.(System column) I,C,O |
coreid 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 column) I,C,O |
coredoc 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 column) I,C,O |
coredate no label |
none |
datetime/date
[getdate()]
|
The date that this Core row was last updated. This field is automatically entered by the system.(System column) I,C,O |
coreuserid no label |
none |
varchar/varchar2 30 [suser_sname]
|
The User ID of the operator that last edited this Core row. It is automatically entered by the system.(System column) I,C,O |
coreugroup 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 column) I,C,O |
coreconst Constituent Type |
Constituent Types |
char 6 [' ']
|
The Constituent Type field is used to classify constituents according to the standards or needs of your institution. You may have a need to categorize your constituents in a way other than the more rigid categories established by the CAE. This lookup table and field allow you to do so. (for example, Alumni, Friend, Individual, Patient, Foundation, Corporation, Religious Organization, etc.). (Don't confuse this field with the CAE Category.). I,C,O |
coresex Gender |
none |
char 1
{'C' or 'M' or 'F' or 'X' or ' '} |
Indicates the gender of this constituent. The field
may be left blank, it may be M for male, it may be F for female, X for non-binary, or it
may be C to indicate that this row is a combined row for a spousal pair. I |
coremaritl Marital Status |
Marital Status |
char 6 [' ']
|
Indicates the marital status of this constituent. If this field is set to Married and then a Death data row is entered for the constituent, this field is automatically set to Deceased Spouse, and if there is a constituent spouse, this field is set to Surviving Spouse. If a non-constituent spousal Relationship is changed to Deceased Spouse/Surviving Spouse, the Marital Status is also changed accordingly. If a spousal I |
corechflag
|
none |
char 2
{'>=' or '=' or ' '} |
Indicates your certainty of the information in the corechnum field. This field may be blank, it may be "=" or it may be ">=" (to indicate that you know that the constituent has at least the number of children indicated in corechnum, but you are not confident that is the exact number of children). I |
corechnum
|
none |
char 2
|
Indicates the number of children that you know the constituent to have. I |
corebirthd Birthday |
none |
datetime/date
|
Indicates the birth date of this constituent. Note that each institution may choose to use this field OR the separate month, day and year fields (corebrthmn, corebrthdy, corebrthyr) and edit their display and data maintenance definitions accordingly. Using one option will not automatically populate the field(s) for the other option. I |
coressnum Social Security Number |
none |
char/ 240
|
Indicates the value of the Social Security Number of this constituent. Value will be stored in this data row encrypted, but displayed as unencrypted. Field only accepts numeric entries. |
corealtid Alternate ID Number |
none |
char 20
|
An alternate ID for this constituent. Often used if the constituent resides on another database within the institution. I,C,O |
coreparpyr Parent Year |
none |
char 4
|
Indicates the year that this constituent's youngest child will graduate from the institution. This is a four-digit year between 1600 and 2200. I |
coreparsch Parent School |
Schools |
char 6 [' ']
|
Indicates the school within your institution from which this constituent's youngest child will graduate. I |
coreprefyr Preferred Year |
none |
char 4
|
Indicates the class with which this constituent prefers to be associated. This is a four-digit year between 1600 and 2200. I |
coreprfsch Preferred School |
Schools |
char 6 [' ']
|
Indicates the school within the institution which this constituent prefers to be associated. I |
coreethnic Ethnic Group |
Ethnic Groups |
char 6 [' ']
|
Indicates the ethnic group with which this constituent is to be associated. I |
coreindust Industry |
Industries |
char 6 [' ']
|
Indicates the industry with which this corporation is affiliated. C |
corefntype Type |
Foundation Types |
char 6 [' ']
|
Indicates the type of foundation or organization represented in this row. O |
coretotemp Total Employees |
none |
numeric/number 10,0 [0]
|
Indicates the total number of employees for the corporation. C,O |
corekwnemp Known Employees |
none |
numeric/number 10,0 [0]
|
Indicates the total number of employees of this corporation who have a constituent row in Millennium (and thus are "known" to the system.). This field is automatically updated when a Jobs row is created for a constituent that indicates an employment link between that individual and this corporation. (System column) C,O |
corealmemp Alumni Employees |
none |
numeric/number 10,0 [0]
|
Indicates the total number of alumni employees. This field is automatically updated when a Jobs row is created for a constituent that indicates an employment link between that individual and this corporation and the individual has a CAE Category of A (Alumni). (System column) C,O |
corerlkey1 non-displaying |
none |
numeric/number 13,0 [0]
|
If the corecorpid field includes the ID Number of a parent company, then this field will hold a copy of the key field from one half of the Relationship row that records that relationship. C,O (System column) |
corerlkey2 non-displaying |
none |
numeric/number 13,0 [0]
|
If the corecorpid field includes the ID Number of a parent company, then this field will hold a copy of the key field from the other half of the Relationship row that records that relationship. (System column) C,O |
corecorpid Parent Corporation |
none |
char 10
|
This field displays the name of the parent corporation. During data entry the name or the ID number may be entered. C,O |
coreallsub Subsidiaries |
none |
numeric/number 10,0 [0]
|
Indicates the total number of subsidiaries this constituent parent corporation has. C,O |
corekwnsub Known Subsidiaries |
none |
numeric/number 10,0 [0]
|
Indicates the number of subsidiaries who are also constituents (and therefore "known" to the system) for this corporation. (System column) C,O |
corepropm1 Proposal Deadlines |
none |
char 2
|
Indicates the first proposal deadline month. C,O |
corepropd1 Proposal Deadlines |
none |
char 2
|
Indicates the first proposal deadline day. C,O |
corepropm2 Proposal Deadlines |
none |
char 2
|
Indicates the second proposal deadline month. C,O |
corepropd2 Proposal Deadlines |
none |
char 2
|
Indicates the second proposal deadline day. C,O |
corepropm3 Proposal Deadlines |
none |
char 2
|
Indicates the third proposal deadline month. C,O |
corepropd3 Proposal Deadlines |
none |
char 2
|
Indicates the third proposal deadline day. C,O |
corepropm4 Proposal Deadlines |
none |
char 2
|
Indicates the fourth proposal deadline month. C,O |
corepropd4 Proposal Deadlines |
none |
char 2
|
Indicates the fourth proposal deadline day. C,O |
corecrdate Create Date |
none |
datetime/date
[getdate]
|
Indicates the date that this constituent's row was created on the system. This field is automatically entered by the system and may reflect the date of conversion if your prior system did not maintain this data. (System column) I,C,O |
corecfae CAE Category |
CAE Categories |
char 6 [' ']
|
Indicates the category for this constituent as defined by the CAE. When a new basic data row is inserted, the triggers will automatically populate this field with contents of the table_cfae field of the constituent_types table. If a basic data row is updated, and that update includes a change in coreconst (Constituent Type), the update triggers will automatically change the value of corecfae. Override this behavior by editing the data row after insert or after update, and manually entering a corecfae code I,C,O |
coresource Source |
Source |
char 6 [' ']
|
Indicates the source of the information contained in the Basic Data row. I,C,O |
Matching Due Dates |
none |
char 2
|
Indicates the month from the first of four dates this company may use as a deadline for accepting matching gift forms. C,O |
coremdued1 Matching Due Dates |
none |
char 2
|
Indicates the day from the first of four dates this company may use as a deadline for accepting matching gift forms. C,O |
coremduem2 Matching Due Dates |
none |
char 2
|
Indicates the month from the second of four dates this company may use as a deadline for accepting matching gift forms. C,O |
coremdued2 Matching Due Dates |
none |
char 2
|
Indicates the day from the second of four dates this company may use as a deadline for accepting matching gift forms. C,O |
coremduem3 Matching Due Dates |
none |
char 2
|
Indicates the month from the first of four dates this company may use as a deadline for accepting matching gift forms. C,O |
coremdued3 Matching Due Dates |
none |
char 2
|
Indicates the day from the third of four dates this company may use as a deadline for accepting matching gift forms. C,O |
coremduem4 Matching Due Dates |
none |
char 2
|
Indicates the month from the first of four dates this company may use as a deadline for accepting matching gift forms. C,O |
coremdued4 Matching Due Dates |
none |
char 2
|
Indicates the day from the fourth of four dates this company may use as a deadline for accepting matching gift forms. C,O |
Default Account |
Chart of Accounts |
char 6 [' ']
|
The Default Account Number field allows you to identify an account number that will automatically be filled into the Insert form for gift or dues transactions for this constituent, when used in connection with the Default form creation of transactions. If you enter the word, "default" in the Account Number field of the Gift or Dues Default form, the transaction will be created, using the Default Account Number field in Basic Data as the Account Number for the Transaction. You may ignore this account number when creating gifts or dues transactions by using the Insert rather than the Default form or by entering an account rather than the word, "default" in the Default definition. When an account is entered for this field, the Account name from the lookup table is also copied to the coreacctnm field and it is that data that is shown in the display of Basic Data. I,C,O |
Title Bar |
none |
char 60
|
The Title Bar field is a free text field of up to sixty characters. The text in this field will display in the title bar after the name. Some possible uses for this field might be to designate a Top Prospect, VIP or to remind operators Do Not Release Info. This field is simply free text and it is not the same as linking rows or entering data that will automate any other features. I,C,O |
corepoint non-displaying |
none |
numeric/number 10,0
|
This system-assigned field is no longer used or supported. (System column) |
coremnamt1 Min. Match Amount |
none |
money/number (19,4)/(16,2) [0]
|
Indicates the minimum gift amount that this company will match for the first of three possible, distinct ratio range amounts If your institution uses the optional Millennium component, Correct GM, this field will be updated automatically in accordance with the most current matching data available from Higher Education Publishing. See Correct GM. C,O |
coremxamt1 Max. Match Amount |
none |
money/number (19,4)/(16,2) [0]
|
Indicates the maximum gift amount that this company will match for the first of three possible, distinct ratio range amounts. If your institution uses the optional Millennium component, Correct GM, this field will be updated automatically in accordance with the most current matching data available from Higher Education Publishing. See Correct GM. C,O |
1st Match Ratio |
none |
char 3
|
Indicates the first of a set of distinct matching gift ratios for this company, based on the size of the original transaction. Each of these ratios may be associated with one, distinct gift amount range. When an individual's gift transaction is entered and that individual is employed by a matching gift corporation, the system will compare the individual's gift to the gift amount ranges in the corporation's Basic Data row and prompt for the creation of a match pledge or match potential transaction for the corporation, using the appropriate ratio for the size of the individual's gift to calculate a default amount of the matching gift for the insert form. If necessary, due to other matching guidelines, the amount should be edited before creating the matching pledge. If you are entering fewer than three ratios, you must use the first (the top field box) first.
If an Employment row identifies this constituent as the employer, AND if this coremratl field shows a matching ratio, the Employment row is automatically updated to set the jobsmflag field (Matching Company?) to Y. If your institution uses the optional Millennium component, Correct GM, this field will be updated automatically in accordance with the most current matching data available from Higher Education Publishing. See Correct GM. C,O |
coremnamt2 Min. Match Amount |
none |
money/number (19,4)/(16,2) [0]
|
Indicates the minimum gift amount that this company will match for the second of three possible ratios.
If your institution uses the optional Millennium component, Correct GM, this field will be updated automatically in accordance with the most current matching data available from Higher Education Publishing. See Correct GM. I,C,O |
coremxamt2 Max. Match Amount |
none |
money/number (19,4)/(16,2) [0]
|
Indicates the maximum gift amount that this company will match for the second of three possible ratios.
If your institution uses the optional Millennium component, Correct GM, this field will be updated automatically in accordance with the most current matching data available from Higher Education Publishing. See Correct GM. I,C,O |
coremrat2 2nd Match Ratio |
none |
char 3
|
Indicates the second set of distinct matching gift ratios for this company, based on the size of the original transaction. Each of these ratios may be associated with one, distinct gift amount range. When an individual's gift transaction is entered and that individual is employed by a matching gift corporation, the system will compare the individual's gift to the gift amount ranges in the corporation's Basic Data row and prompt for the creation of a match pledge or match potential transaction for the corporation, using the appropriate ratio for the size of the individual's gift to calculate a default amount of the matching gift for the insert form. If necessary, due to other matching guidelines, the amount should be edited before creating the matching pledge.
If you are entering fewer than three ratios, you must use the first (the top field box) first.
If your institution uses the optional Millennium component, Correct GM, this field will be updated automatically in accordance with the most current matching data available from Higher Education Publishing. See Correct GM. C,O |
coremnamt3 Min. Match Amount |
none |
money/number (19,4)/(16,2) [0]
|
Indicates the minimum gift amount that this company will match for the third of three possible, distinct ratios.
If your institution uses the optional Millennium component, Correct GM, this field will be updated automatically in accordance with the most current matching data available from Higher Education Publishing. See Correct GM. C,O |
coremxamt3 Max. Match Amount |
none |
money/number (19,4)/(16,2) [0]
|
Indicates the minimum gift amount that this company will match for the third of three possible, distinct ratios.
If your institution uses the optional Millennium component, Correct GM, this field will be updated automatically in accordance with the most current matching data available from Higher Education Publishing. See Correct GM. C,O |
coremrat3 3rd Match Ratio |
none |
char 3
|
Indicates the third set of distinct matching gift ratios for this company, based on the size of the original transaction. Each of these ratios may be associated with one, distinct gift amount range. When an individual's gift transaction is entered and that individual is employed by a matching gift corporation, the system will compare the individual's gift to the gift amount ranges in the corporation's Basic Data row and prompt for the creation of a match pledge or match potential transaction for the corporation, using the appropriate ratio for the size of the individual's gift to calculate a default amount of the matching gift for the insert form. If necessary, due to other matching guidelines, the amount should be edited before creating the matching pledge.
If you are entering fewer than three ratios, you must use the first (the top field box) first.
If your institution uses the optional Millennium component, Correct GM, this field will be updated automatically in accordance with the most current matching data available from Higher Education Publishing. See Correct GM. C,O |
corelattr non-displaying |
none |
char 1
{'N' or 'Y'} |
A flag to indicate whether or not this row has attached Attribute rows. (System column) I,C,O |
corebcntry Birth Nation |
Countries |
char 6 [0]
|
Indicates the country of birth for the constituent. I |
coretbltyp non-displaying |
Table Groups |
char 6 [0]
|
This is a copy of the Group field from the Constituent Type Lookup table entry that was chosen for the coreconst field. It signals the system for the appropriate use of the Individual, Corporation or Organizational form of the Basic Data page. It is automatically assigned by the system. (System column). I,C,O |
coreanon non-displaying |
none |
char 1 ['N'] {'N' or 'Y'} |
This field is reserved for future use by Millennium. (System column) |
corefnum non-displaying |
none |
char 2 ['00'] {'00'} |
The table number of the current table. (System column) I,C,O |
corecomm not labeled |
none |
varchar/varchar2 4000
|
A free text Comment that may be entered and displayed with this Basic Data row only. I,C,O |
matchcomm Matching Guidelines |
none |
varchar/varchar2 255
|
A free text Comment, used for additional details about a corporation or organization's matching gift policies. C,O |
coreactive Active |
none |
char 1 ['Y'] {'N' or 'Y'} |
This flag indicates whether the Basic Data row belongs to an "active" constituent. I,C,O |
corequidm Match Quid |
none |
char 1 ['N'] {'Y' or 'N'} |
If the constituent is a matching gift company, this flag indicates whether they will or will not match the quid pro quo portion of the original constituent's gift. C,O |
coregrnpyr Parent Year |
none |
char 4
|
Indicates the year that this constituent's youngest grandchild will graduate from the institution. This is a four-digit year between 1600 and 2200. I |
Default Account |
Chart of Accounts |
varchar/varchar2 80
|
This field holds a copy of the Account Name for the Default Account (corerest). I,C,O |
coredate1
|
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. I,C,O |
coredate2
|
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. I,C,O |
coremny1
|
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. I,C,O |
coremny2
|
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. I,C,O |
corenum1
|
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. This field is available for Profile Searches. I,C,O |
corenum2
|
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. I,C,O |
coreyesno
|
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. I,C,O |
corelook1
|
Corebio Lookup1 |
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. I,C,O |
corelook2
|
Corebio Lookup2 |
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. I,C,O |
corelook3
|
Corebio Lookup3 |
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. I,C,O |
coretext
|
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. I,C,O |
corepublsh Publish |
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 Basic Data table are set to 'Published by Consent'. Otherwise, the corepub00 field flag in the Basic Data table will be used. I,C,O |
Match Through |
none |
char 10
|
If the constituent is a Corporation or Foundation that matches donations made by its employees or others, but if the matching funds are actually administered and delivered by another entity (such as a foundation created specifically for such a purpose), this field is used to hold a copy of the ID Number of that entity - also a constituent. If thePull Match Ratios from the Corporation system option is set to No, then the matching information from the 'Match Through' constituent is automatically copied to the corresponding fields for the original constituent. The following fields will be copied: coremrat1, coremxamt1, coremnamt1, coremduem1 coremdued1, coremrat2, coremxamt2, coremnamt2, coremduem2, coremdued2, coremrat3, coremxamt3, coremnamt3, coremduem3, coremdued3, coremduem4, coremdued4, corequidm, corespmfl, coreretmfl, matchcomm, corempkey. Note that if your institution uses the optional Millennium component CorrectGM, and if the constituent you identify in this field as the Match Through entity already has a link to an entity in the Match Parent table, that same linkage will be established for the initial constituent using the corempkey field. During giving data entry if you have activated the option to have the system suggest matching pledge or match potential transactions, and if the coremtchid field is populated in the Basic Data for the matching employer, the insert form for the Match Pledge or Match Potential will automatically show the Match Through ID as the source of the pledge or potential, rather than the actual employer. C, O |
coreuserec User Name |
none |
char 30
|
If your site uses the optional Millennium component,Online Constituent Directory, this field is used to store the constituent's user name for logging onto your institution's member website. I, C, O |
corepwdec Password |
none |
char 240
|
If your site uses the optional Millennium component,Online Constituent Directory, this field is used to store the encrypted value of the constituent's password for logging onto your institution's member website. I, C, O |
corepub00
|
none |
char 1 ['N'] {Not Null} |
If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's Basic Data information may or may not be used for publication on your institution's website. (Note that your institution will need to set the Basic Data information for all constituents via the eDirectory under Options for Publishing Tables.) I, C, O |
corepub01
|
none |
char 1 ['N'] {Not Null} |
If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's Name information may or may not be used for publication on your institution's website. (Note that your institution will need to set the Name information for all constituents via the eDirectory under Options for Publishing Tables.) I, C, O |
corepub02
|
none |
char 1 ['2'] {Not Null} |
If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's Address information may or may not be used for publication on your institution's website. (Note that your institution will need to set the Address information for all constituents via the eDirectory under Options for Publishing Tables.)
'2' = 'Do Not Hide' '1' = 'Hide the Phone Number' '0' = 'Hide'
I, C, O |
corepub03
|
none |
char 1 ['N'] {Not Null} |
If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's Attribute information may or may not be used for publication on your institution's website. (Note that your institution will need to set the Attribute information for all constituents via the eDirectory under Options for Publishing Tables.) I, C, O |
corepub04
|
none |
char 1 ['N'] {Not Null} |
If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's Relation information may or may not be used for publication on your institution's website. (Note that your institution will need to set the Relation information for all constituents via the eDirectory under Options for Publishing Tables.) I, C, O |
corepub05 (not currently available for use) |
none |
char 1 ['N'] {Not Null} |
If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's Giving information may or may not be used for publication on your institution's website. (Note that your institution will need to set the Giving information for all constituents via the eDirectory under Options for Publishing Tables.) I, C, O |
corepub06
|
none |
char 1 ['N'] {Not Null} |
If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's Employment information may or may not be used for publication on your institution's website. (Note that your institution will need to set the Employment information for all constituents via the eDirectory under Options for Publishing Tables.) I, C, O |
corepub07
|
none |
char 1 ['N'] {Not Null} |
If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's Education information may or may not be used for publication on your institution's website. (Note that your institution will need to set the Education information for all constituents via the eDirectory under Options for Publishing Tables.) I, C, O |
corepub08 (not currently available for use) |
none |
char 1 ['N'] {Not Null} |
If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's Dues information may or may not be used for publication on your institution's website. (Note that your institution will need to set the Dues information for all constituents via the eDirectory under Options for Publishing Tables.) I, C, O |
corepub26
|
none |
char 1 ['N'] {Not Null} |
If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's Phone information may or may not be used for publication on your institution's website. (Note that your institution will need to set the Phone information for all constituents via the eDirectory under Options for Publishing Tables.) I, C, O |
corepub28 (not currently available for use) |
none |
char 1 ['N'] {Not Null} |
If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's Membership information may or may not be used for publication on your institution's website. (Note that your institution will need to set the Membership information for all constituents via the eDirectory under Options for Publishing Tables.) I, C, O |
corejoint (not currently available for use) |
none |
char 1 ['N'] {Not Null} |
This field acts as a flag to indicate that any transactions that are created for this constituent should always, automatically be set to activate the Joint with Spouse option. I |
corespcrd (not currently available for use) |
none |
char 1 ['N'] {Not Null} |
This field acts as a flag to indicate that any transactions that are created for this constituent should always, automatically be set to activate the Credit for Spouse option. I |
coreothcrd (not currently available for use) |
none |
char 1 ['N'] {Not Null} |
If the constituent has any Relationship rows which have the Credit for Other (relothcrd) flag set to 'Y', the system will automatically set this flag to Y. (System column) I,C,O |
coreretmfl
|
none |
char 1 ['N'] {Not Null} |
If this row belongs to a corporation or other type of constituent that provides matching gifts, this field is used to flag whether they will do so for retired employees, as well as active employees. If your institution uses the optional Millennium component, Correct GM, this field will be updated automatically in accordance with the most current matching data available from Higher Education Publishing. See Correct GM. (System column) C, O |
corespmfl
|
none |
char 1 ['N'] {Not Null} |
If this row belongs to a corporation or other type of constituent that provides matching gifts, this field is used to flag whether they will do so for gifts made by the spouse of employees. If your institution uses the optional Millennium component, Correct GM, this field will be updated automatically in accordance with the most current matching data available from Higher Education Publishing. See Correct GM. (System column) C, O |
non-displaying |
none |
numeric/number (13,0)
{null} |
If your institution uses the optional, Correct GM component of Millennium, and if this row belongs to a corporation or other type of constituent that provides matching gifts, this field is used to track the link to a corresponding row in the Match Parent table with a copy of the key field from that table. When such a link is established, AND if the Pull Matching Ratios from the Corporation system option is set to No, the system automatically copies data from the Match Parent table into the coremnamt1, coremxamt1, coremnamt2, coremxamt2, coremnamt3, coremxamt3, coremrat1, coremrat2, coremrat3, coreretmfl, and corespmfl columns. When the Match Parent table is periodically updated (a regular function of the CorrectGM component) those same fields will also be updated on the basis of this linkage IF the Pull Matching Ratios from the Corporation system option is set to No. (System column) C, O |
corebrthyr
|
none |
char 4
{null} |
This field, along with corebrthmn and corebrthdy, provide an alternative to the use of the corebirthd field. This is a four-digit year between 1600 and 2200. Your institution has the option to modify the display and maintenance definitions of the Basic Data row and replace the corebirthd (a true datetime/date field which includes all three pieces of the date) with all or some of the fields corebrthyr, corebrthmn, and corebrthdy which store the three pieces of information in separate columns. Using one option will not automatically populate the field(s) for the other option. I |
corebrthmn
|
none |
char 2
{null} |
See corebrthyr. |
corebrthdy
|
none |
char 2
{null} |
See corebrthyr. |
corehintec
|
none |
varchar 60
{null} |
If your site uses the optional Millennium component,Online Constituent Directory, this field is used to store a constituent's hint question. This would usually be a question provided by the constituent, along with an answer (coreanswec), used to verify the identity of the constituent before e-mailing a forgotten password for logging onto your website (corepwdec). (System column) I, C, O |
coreanswec
|
none |
varchar 20
{null} |
If your site uses the optional Millennium component,Online Constituent Directory, this field is used to store a constituent's answer to a hint question (corehintec). This is used to verify the identity of the constituent before e-mailing a forgotten password for logging onto your website (corepwdec). (System column) I, C, O |
coreupkey non-displaying |
none |
numeric/number 13, 0
|
This field holds the Timekey of the pending data row that may be updated from the corebio_pending table. |
corepend Pending |
none |
char 1 ['N'] {Not Null} |
This field is a flag to indicate that this data row has linked information in the 'pending' Corebio 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 column) |
core1passw
|
none |
char 1 ['N'] {Not Null} |
This field is a flag to indicate that the user must change their password the next time the log in. |
coreltmout
|
none |
datetime/date [getdate]
{null} |
This field holds the date and time the 20 minute lockout started. After 20 minutes from this date and time the user can attempt their login again. |
corestmout
|
none |
datetime/date [getdate]
{null} |
This field holds the last date and time the user was actively logged in. |
coreattmpt
|
none |
numeric/number 3, 0 ['0'] {Not Null} |
This field holds the number of successive invalid log ins a user has attempted. After the third attempt the user will be locked out for 20 minutes. |
corepub09
|
none |
char 1 ['N'] {Not Null} |
If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's Comments information may or may not be used for publication on your institution's website. (Note that your institution will need to set the Comments information for all constituents via the eDirectory under Options for Publishing Tables.) I, C, O |
corepub81
|
none |
char 1 ['N'] {Not Null} |
If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's email (via internetaddress table) information may or may not be used for publication on your institution's website. (Note that your institution will need to set the email (via internetaddress table) information for all constituents via the eDirectory under Options for Publishing Tables.) I, C, O |
corepub69
|
none |
char 1 ['N'] {Not Null} |
If your site has purchased the optional Millennium component, Online Constituent Directory, this field is used to indicate whether any of this constituent's custombio information may or may not be used for publication on your institution's website. (Note that your institution will need to set the custombio information for all constituents via the eDirectory under Options for Publishing Tables.) I, C, O |
|
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. I,C,O |
coredate4
|
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. I,C,O |
coredate5
|
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. I,C,O |
coredate6
|
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. I,C,O |
coredate7
|
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. I,C,O |
coredate8
|
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. I,C,O |
coredate9
|
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. I,C,O |
coredte10
|
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. I,C,O |
coredte11
|
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. I,C,O |
coredte12
|
none |
datetime/date
|
This custom field may be defined and used by your institution to track any date information associated with this data row. I,C,O |
coremny3
|
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. I,C,O |
coremny4
|
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. I,C,O |
coremny5
|
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. I,C,O |
coremny6
|
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. I,C,O |
coremny7
|
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. I,C,O |
coremny8
|
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. I,C,O |
coremny9
|
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. I,C,O |
coremny10
|
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. I,C,O |
coremny11
|
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. I,C,O |
coremny12
|
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. I,C,O |
corenum3
|
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. I,C,O |
corenum4
|
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. I,C,O |
corenum5
|
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. I,C,O |
corenum6
|
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. I,C,O |
corenum7
|
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. I,C,O |
corenum8
|
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. I,C,O |
corenum9
|
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. I,C,O |
corenum10
|
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. I,C,O |
corenum11
|
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. I,C,O |
corenum12
|
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. I,C,O |
corechk1
|
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. I,C,O |
corechk2
|
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. I,C,O |
corechk3
|
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. I,C,O |
corechk4
|
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. I,C,O |
corechk5
|
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. I,C,O |
corechk6
|
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. I,C,O |
corechk7
|
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. I,C,O |
corechk8
|
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. I,C,O |
corechk9
|
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. I,C,O |
corechk10
|
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. I,C,O |
coretxt1
|
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. I,C,O |
coretxt2
|
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. I,C,O |
coretxt3
|
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. I,C,O |
coretxt4
|
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. I,C,O |
coretxt5
|
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. I,C,O |
corelook4
|
Corebio Lookup4 |
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. I,C,O |
corelook5
|
Corebio Lookup5 |
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. I,C,O |
corelook6
|
Corebio Lookup6 |
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. I,C,O |
|
none |
datetime/date
|
Indicates the date and time the constituent last logged on to the Online Constituent Directory. |
Alternate ID 2 |
none |
char 20
|
An alternate ID for this constituent. I,C,O |
corealtid3 Alternate ID 3 |
none |
char 10
|
An alternate ID for this constituent. I,C,O |
corealtid4 Alternate ID 4 |
none |
char 10
|
An alternate ID for this constituent. I,C,O |
corealtid5 Alternate ID 5 |
none |
char 20
|
An alternate ID for this constituent. I,C,O |
coreadesrc non-displaying |
ade_source |
char 30 |
If this row is created or updated from data that originally came from the corebio_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.
|
coreuserip | none |
char 40 |
If your site uses the optional Millennium component,Online Constituent Directory, this field is used to store the IP Address of the computer that the constituent used to log on to your institution's member website.
|
corephoto | <placeholder> | ||
coreyercpt Year-end receipts?
|
none |
char 1 |
Selecting this option results in the constituent receiving one single tax receipt at the end of the year. Leave blank to issue tax receipts throughout the year as payments are received. |
corecolsta Collection Status
|
none |
char 6 |
This field is used by your institution to identify and categorize constituents who are delinquent with payments and/or outstanding pledges.
|
coredefdiv Default Division Name
|
campaign_division |
char 12 |
This field places your donors into categories that you have customized to suit your organization. Some examples are geography, demographics and giving history. When the data row is displayed, the value associated with this field is what you will be shown. |
coreisrcpt Issue Serialized Receipt
|
none |
char 1 |
Select this option to indicate that a constituent should receive a serialized tax receipt for gifts, pledge payments, and dues transactions. Valid values are Y (Yes), N (No), and H (Hold). |
corelang Language Preference
|
language_preference |
char 6 |
Indicates the preferred language of the constituent. |
corestatdt non-displaying
|
none | datetime | This field is maintained by the system, and records the date the constituent's corestatus was last changed. |
corestatus Constituent Status
|
none |
char 6 |
This field is used by your institution to give a constituent an Active or Inactive status (such as Active, Inactive - deceased, Inactive - moved, Inactive - removed by request). I,C,O
|
coreddivnm Default Division Name |
campaign_division |
varchar 120 |
This field is maintained by the system, and contains the value corresponding to the selected coredefdiv code. |
Custom Fields
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.
Indices - Basic Data
Index | Primary | Foreign | Unique | Fields | Sort |
---|---|---|---|---|---|
pk_corebio | Y | Y | corekey | ASC | |
uq_coreid | Y | coreid | ASC | ||
corebio03 | Y | coreconst | ASC | ||
corebio04 | coreprefyr | ASC | |||
corebio05 | coreparpyr | ASC | |||
corebio06 | Y | coreprfsch | ASC | ||
corebio07 | corerest | ASC | |||
corebio08 | coressnum | ASC | |||
corebio09 | corealtid | ASC | |||
corebio10 | corecorpid | ASC | |||
corebio11 | coredate | ASC | |||
corebio12 | coreuserid | ASC | |||
corebio13 | corerlkey1 | ASC | |||
corebio14 | coreuserec | ASC | |||
corebio15 | coremtchid | ASC | |||
corebio16 | coresex | ASC | |||
corebio17 | coreethnic | ASC | |||
corebio18 | coremaritl | ASC | |||
corebio19 | corebirthd | ASC | |||
corebio20 |
corebrthyr, |
ASC | |||
corebio21 | corenum1 | ASC | |||
corebio22 | corealtid2 | ASC | |||
corebio23 | corealtid3 | ASC | |||
corebio24 | corealtid4 | ASC | |||
corebio25 | corealtid5 | ASC |