Summing today's meeting, here's the first phase plan:
0. Create INFORMIX DB with Fac/Staff/Student fields
1. UNISYS loads/updates INFORMIX DB with Student information "directly"
2. INFORMIX DB generates (eliminating Rhys):
- the 3 current Li files sent to Li servers
- svf.info sent to Austen for C&CI
- svfd.dat sent to Austen for expiration process
3. Create a client for C&CI to use to replace need for svf.info
4. Do #1,2,3 as appropriate for Fac/Staff
5. Create and use a verify API (removing this function from Li):
- when done, svfd.dat is the only file still needed (expiration
function not yet addressed)
- needs to handle "blue people" (aagaard customers) which we now
get via flat file from MCIS - create a client for MCIS?
Goals:
1. Have Fac/Staff, Student, Clinician verification information in
INFORMIX DB
2. Have UNISYS load/update INFORMIX DB directly
3. Eliminate Rhys svf processing, Austen fvf processing, Austen aagaard
processing
4. Use new verify API against INFORMIX DB, removing this function from Li.
Tom, Yonah, Pete, and Jim will start on step 0., involving Ping/Liz for
advise on DB design and step 1.
Date: 97/05/29