Co-Op Student Evaluation Project

Meeting Minutes - 04/11/05

• General Information

• Change printed forms
  
  • Remove boxes from around responses
  • Try to condense the evaluation to use as few sheets of paper as possible.
• Problem submitting student form
  Jim has been able to recreate the error that he got trying to submit a student form. He said that the steps that he followed were as follows: first, he filled out the form a few times with incorrect information, then he submitted it with all correct information. He said that it then reported that it had submitted correctly and that he could view the data, but when he went to view it on the administration and department sides, many of the questions weren't answered.
  Update: We have found that the cause of this was that one of the fields that he submitted had more than the 2,000 characters in it, which is the current maximum limit in the database. We are currently looking into fixing this problem.
• Problem with analysis reporting
  Dan is currently looking into this.
• Problem editing forms
  
  • Jim pointed out that when he tried to edit a form through the online editing functionality he was unable to and was instead redirected to the login page.
    Patrick confirmed this problem, and said that it is a known problem when using our system with Internet Explorer. We are currently looking into fixing this.
• Student ID isn't working
  This is a known issue, since the system is not currently communicating with LDAP. Mark has agreed to send Dan some sample strings for using the LDAP functionality, and they have agreed to meet on Wednesday (4/13/05) at 6:00pm if neeeded.
• Searching specifically by employer or student evaluation status
  After discussion, it was decided that we would split up the evaluation status box so that the user has the option to search for only employer or student evaluation status or both.
• Validation for first set of questions on student work report forms
  It was decided that we would hard-code the desired questions into the JSP and do special validation on those questions.
• Merging our test database with ITS' database
  
  • Involves
    
    • Creating scripts
    • Validating that the system works with the data after the merge
  • Chris suggested that we create a new schema from scratch, put our required data into it, and then copy the old data into the new schema.
  • Mark will set aside the required space on the test database
  • Chris will create the scripts to create the new schema, including any data required by our system
  • After both of the above are done, they will move the data to the new schema — this will be done by Friday (4/15/05)
• Import process
  
  • This is not currently included in our test plan
  • This will definitely need to be tested
    It was decided that this will be tested by ITS — after doing the merge, they will run a test insert using an actual script.