Specifications for training-related data feeds

Jim Repa. Last modified 10/15/2003

I. Information to be posted via HTML form variables:

The following data fields are transferred from ehsweb to traincasters in "real-time" after a user registers on ehsweb and clicks a button to proceed to Traincasters.

II. Files to be sent from MIT to Traincasters

Files will be tab-delimited and will be encrypted via PGP and sent via FTP.

  1. dlc.text
    Field nameDescriptionMaximum
    length
    d_code DLC code such as 'D_CHEM' 15
    descriptionName of DLC50

  2. pi_supervisor.text
    Field nameDescriptionMaximum
    length
    username Kerberos username of the PI/supervisor 8
    fullnamefull name of supervisor (lastname followed by first name) 60

  3. reg_person.text
    Field nameDescriptionMaximum
    length
    kerberos_username user's Kerberos username (all uppercase) 8
    last_nameuser's last name (all uppercase) 30
    first_nameuser's first name (all uppercase) 30
    middle_nameuser's middle name (all uppercase) 30
    emailuser's email address 60
    mit_id user's MIT ID number (999999999 means "none") 9
    dlc D_xxxxx code for main department reported by the user 15
    supervisor_pi Kerberos username of the main PI or supervisor reported by the user 8
    facility code for the lab_suite or other facility where the user works. (We decided not to collect person to room-set information, so this field will be blank.) 15
    course_code01 a course code the user must take (uncompleted only) 15
    course_code02 a course code the user must take (uncompleted only) 15
    ...  
    course_code20 a course code the user must take (uncompleted only) 15

    Programming notes for the feed program on EHSWEB:

  4. facility.text
    Field nameDescriptionMaximum
    length
    facility_code unique code number for the lab or other facility 15
    facility_type Description of type of facility (lab-suite, machine-shop, etc.) 50
    facility_nameName or description of facility 50
    d_codeDLC code 15
    pi_usernameKerberos username of PI/supervisor 8
    room_list Comma-delimited list of building-room numbers (e.g., '16-301,16-302,16-305') 200

  5. course_req.text

    We might want to think about some of the fields in the next two files before finalizing them. What do we do about live courses in which a person is registered, if anything? How do we handle courses due to expire? Does MIT or does Traincasters determine when it is time to start reporting courses that are due to expire in a given number of days?

    Field nameDescriptionMaximum
    length
    username Kerberos username of trainee 8
    course_codecourse code for required course 10(?)
    needs_repeatWill course need to be repeated? 'Y' or 'N' 1
    expiration_date Date course will need to be repeated (mm/dd/yyyy) 10

  6. course_complete.text
    Field nameDescriptionMaximum
    length
    username Kerberos username of trainee 8
    course_codecourse code for required course 10(?)
    completion_date Date course was completed (mm/dd/yyyy) 10
    completion_notes How was course completed? web, live, signature-of-supervisor, etc. 40

III. Files to be pulled by MIT from Traincasters

Files will be tab-delimited and will be encrypted via PGP and pulled via FTP.

  1. course_complete.text

    Field nameDescriptionMaximum
    length
    username Kerberos username of trainee 8
    course_codecourse code for required course 10(?)
    completion_date Date course was completed (mm/dd/yyyy) 10
    completion_notes How was course completed? web, live, signature-of-supervisor, etc. 40

IV. Files to be transfered from SAP or K.C.'s training DB to ehsweb

Files be tab-delimited and will be encrypted via PGP and pulled via FTP. Fields should be variable-length.

  1. live_course.text

    Field nameDescriptionMaximum
    length
    username Kerberos username of trainee 8
    mitid MIT ID of trainee (required if there is no Kerberos username) 9
    course_option_codecourse option code, e.g., 100c, 111s, 260c, etc. (required field) 15
    course_section_codecourse section code (not needed) 15
    course_option_typehow course is taken: L=live, W=web, O=other (required field) 1
    registered_date Date user registered for course (mm/dd/yyyy) 10
    status Status of trainee in course. R=registered, C=completed (required field)1
    completion_date Date course was completed (mm/dd/yyyy) - required for completed courses 10
    instructor_kerbname Kerberos username of instructor (if known) 8
    instructor_name Full name of instructor (first middle last) - fill this in if instructor name is known but there is no instructor Kerberos username 60
    completion_notes Optional notes about completion of course or other option 40

    Notes: