BOG Fee Waiver Project Meeting Minutes

June 22, 2015 3:00-4:00 p.m.

Participants :  Lee McDonald, Nina Van,  Kevin Harral, Ryan Anthony remotely,  Chien Shih, Mahmood Hasan, Jim Clow, Linda Koyama

1. Process flow by Jim
   
   1. Students log in and complete a Open CCCApply or Bog Application which goes to the OpenCCCApply Center.  Import process grabs the applications and info is stored in an Oracle table (szrbogw).
   2. The users will go into the SWABOGW Banner form to correct those applications that are  in suspense.
   3. SWABOGM Form will be used for common matching.
   4. A trigger will load into the data into our Banner tables.
   5. FHDA can determine how many times a day RVPBST should run.
2. Report from Lee:  If it didn't match to someone is already in Banner, it will load straight and will not go into suspense form, similar to how the current OpenCCCApply applications work.  Lee suspects that a large percentage will most likely match since they will be coming in with the CCCID.
3. Lee was waiting for the applications to be redownloaded.  Ryan can reset the applications any time he needs to and the users entered more applications today.  
4. Where we are now:  Lee was having connection issues this morning.  He notified Vicki, Ryan, and Jim and hasn't heard back.  Hasan and Linda need to be included in any future e-mails from Lee.
5. To meet the June 30th timeline, we need to have Lee's code in the FHDA environment this week to test the download. 
6. Lee has been waiting for the applications to be redownloaded since he updated the format file.  Lee has not been receiving e-mails sent from ETS since Thursday.
7. Lee is having connection issues getting into PRODN.  We can't compile the form until the view is in place.  Lee sent the new XML format file on the 16th.  
8. Ryan received the new XML format file, redownloaded the applications and put it back on the Merced desktop like he did the first time.
9. When Lee is running Oracle SQL developer on Merced, he is having trouble compiling the view because the error message states he isn't connected to the database.
10. Lee will send the forms today to Vicki, and cc Hasan and Linda to compile as soon as the view is in place.
11. Ryan will download the latest SQL developer on Merced.
12. The form needs to be added to Banner security....Lee will send explicit instructions.  It will need to be in a security class that the appropriate users belong to or give them direct access to it.
13. Once the security is set up, ETS will go through a test of the  forms and see test data.
14. Jim informed Lee that there is a missing field is SZRBOGW_source_cd that needs to be added to the table so that he can compile the view.
15. Lee needs to compile the trigger after the view is in place.  The code should be ready for testing tomorrow morning.  The trigger needs to be compiled into Banner.
16. Tomorrow by early afternoon, we should have a prototype system in place.
    1. Lee will hand over the two forms.
    2. ETS will compile into the Banner library.
    3. Lee will hand over the trigger code.
    4. ETS will grant the security.  
    5. Ryan will receive the import procedure.
17. Lee will not be working on Friday; he'll be moving.
18. Hasan and Lee will touch base by phone on a daily basis this week.
19. Kevin and Nina will send the list of users' CWIDs who will need access to the forms to Jim and Bill. Baldwin.
20. Hasan will touch base with Lee during his PMO staff meeting via conference call.