Structure for database: MLIST
Field Field Name Type Width Dec
1 LAST Character 15
2 FIRST Character 15
3 SANSKRIT Character 15
4 ADDR1 Character 30
5 ADDR2 Character 30
6 CITY Character 24
7 ST_PROV Character 5
8 ZIP_POST Character 7
9 COUNTRY Character 20
10 AKEY Character 15
11 TEL_WORK Character 20
12 TEL_HOME Character 20
13 TEL_CELL Character 20
14 EMAIL Character 40
15 SEX Character 1
16 NAME_PREF Character 1
17 ID Numeric 6
18 ID_SPS Numeric 6
19 DATE_UPDAT Date 8
20 DATE_ENTRD Date 8
21 AFFIL Character 30
22 DATE_HF Date 8
23 DATE_PATH Date 8
24 DATE_LM Date 8
25 COMMENT Character 36
** Total ** 397
mlist.dbf is where the bulk of the data is stored.
Most of the fields above are self explanatory except these:
- AKEY
- A generated field for use in address searching and
unduplication. It is all the numeric digits in the address
and zip_post fields suffixed with the first alphabetic in those fields.
- NAME_PREF
- A single character telling what is the preferred method
of displaying the person's name.
- A - First Last
- B - Sanskrit Last
- C - Sanskrit First Last
- D - First Sanskrit Last
- E - Sanskrit
- F - Last+First+Sanskrit (untrimmed)
- ID and ID_SPS
- Unique numeric identifiers (the next in the sequence
is kept in system.dbf). If a person has a partner
the partner's ID is kept in ID_SPS (id of spouse).
- AFFIL
- A series of characters describing how
this person is affiliated with the center/fellowship.
The description of each character is contained in the
affil.dbf table (see below).
- DATE_HF, DATE_PATH, DATE_LM
- Hanuman Fellowship, Pathways subscription, Land Member.
These dates are maintained manually and so may not be totally current.
- COMMENT
- This field can be edited but it is also automatically
filled in.
When someone registers for a program in reg the program name is
automatically put in their mlist COMMENT field.