0.6 release tasks

Information

This contains information related to the 0.6 release tasks
JIRA tracking: http://bugs.sakaiproject.org/jira/browse/EVALSYS

Key:

Complete=

Testing/QA=

In Progress=

ToDo=

Defer to next milestone=

Critical Tasks

1. Locking Aaron Zeckoski
   1. Create locking methods and tests in the DAO
   2. Update the logic layer to use the locking methods
2. Evaluation Bean split and rewrite - EVALSYS-22
   1. Split out answers request bean Will Humphries
   2. Split out evaluationBean into 3 classes
      1. Evaluation creation - session bean
      2. Evaluation modification - request bean
      3. Evaluation util class
         1. Update evaluation related buttons to links on the control panel view
   3. Destroy old evaluation bean
3. Restore full functionality of evaluation bean - Kapil Ahuja - EVALSYS-43
4. Write Block item functionality Rui Feng
   1. adding new block items
   2. reordering items
   3. modifying block items
   4. previewing block items
   5. render and submit block item answers for users
5. Use System Settings everywhere Kapil Ahuja
   1. Ensure that system settings are being enforced - EVALSYS-15.
6. Multiple evaluation submissions Will Humphries - EVALSYS-41
   1. students can fill out evaluations multiple times only if the system setting allows it
   2. check that only one entry is allowed per evaluation per context per student
7. Internationalization Rui Feng
   1. other strings in producers and use the locale to render all dates
8. Rendering items Rui Feng
   1. Rendering of the various types in related page properly
   2. should be broken out into multiple methods and util files
   3. Get rid of code duplication for rendering the various item types
   4. Maybe use multiple view producers to handle rendering of multiple items
9. Preview Modified / New Items Will Humphries
10. Administrative Tools Kapil Ahuja
    1. Add/ Modify / Remove scale - EVALSYS-16 (moved to 0.7, see JIRA for details)
11. Date utils and making sure that the minimum length of evaluation is enforced Kapil Ahuja - EVALSYS-24 (moved to 0.7, see JIRA for details)
12. User input Rui Feng
    1. Make sure dates are input using a date widget
    2. Make sure text is input using WYSIWYG
    3. Make sure no user input can cause XSS attacks
    4. Check that no user input can cause an exception

Non-critical Tasks

1. debug: EvalStart page only show public template (it should include private template)
2. TAKE EVAL
   1. Revisit the 3 TODO's of order of options in ITEM_DISPLAY page. Rui Feng
3. Remove 2 TODO's from EvaluationBean of initializing 100 items. See note there.
4. the radio button of the first template need to selected by default for Start Eval Page
5. Create a include file for preview_eval.html and take_eval.html.
6. Actual sending email:
   1. logic, functionality-- Actual sending email
      1. get siteID
      2. get UserInfo, get userEmail
      3. use EmailService to send email
   2. For sending email we need details of users in a course. So from SITE API get list of users. Then from USER API get details of each user.
   3. For actual sending email refer to the Email API (Email Service class).
7. On settings page if you use Cancel button several times...sometime something goes wrong.
8. If you remove items randomly many times you get null pointer in remove producer because of some N/A not set in template Bean (seem to be fixed but need more robust testing).
9. Improvement: move the setScale to logic layer and clean it more.
10. Add a comment question to all evaluations (use system setting to determine this)
11. In EvaluationDAOImpl.java see why DetachedCriteria not working.
12. Resolve bug: Item page check box "N/A" not value binding correctly when "preview" button was clicked before "save" button clicked
13. Resolve bug: Item Page radio button group "category" not value binding correctly when "preview" button was clicked before "save" button clicked
14. In assign eval page: Javascript checks on the HTML page (to be done by BeanGuards).
15. In eval settings page: Javascript checks on the HTML page (to be done by BeanGuards), Calendar should be deferred for a while...it would be supplied by Antraing.
16. Also, we would use date widgets so don't worry about all this. Use dates wigets by Antranig (see this attached file which is transcript of chat with Antraing