0.8 release tasks

Information

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

Key:

Complete=

Testing/QA=

In Progress=

ToDo=

Defer to next milestone=

Critical Tasks

JIRA bugs and issues remaining from 0.7 (assigned within JIRA)
Expert Items ~aaronz
1. Templates for the expert item process
2. Preload a small set of expert items
3. Producers for expert items
Existing items
1. Allow users to reuse existing items (except block parents)
2. Create view for inserting existing items into templates
Allow instructors to add items to evaluations assigned to them
1. Create new view from wireframe
2. Use basic hierarchy code
3. Update the logic layer to return the instructor related items
4. Update everything that gets templateitems to use the logic layer and not the lazy loaded list from the hibernate object
Administrative Tools ~kapsahuja22
1. Remove scale - EVALSYS-95
2. Modify scale - EVALSYS-16 (carry over task EVALSYS-99 assigned to Antranig).
3. Add scale - EVALSYS-96 (carry over task EVALSYS-99 assigned to Antranig).
Administrative Tools - EVALSYS-99 - Antranig.
User input ~kapsahuja22 - to be carried over to 0.9 release
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
Email functionality (continued) ~rwellis
1. Scheduling emails (Quartz scheduler)
2. Links in emails work to take an eval
Scheduling for evals (registering start, due, etc...) and switching eval states ~rwellis
1. Scheduling evaluation state changes (inQueue -> Active -> Due -> Closed -> Viewable)
Test external contexts providers ~rmoyer@umd.edu
AJAX reordering ~spfjr@umd.edu
1. reordering of template items on the modify template items view
2. reordering of template items within a block in the modify block view
Ensure that all current functionality is working ~fengr@vt.edu, Lisa-UM?
1. verify that i18n applied to all strings
2. verify that no broken links or buttons exist on any page
3. check that user cannot cause exceptions with input
4. check that no exceptions occur
Expert item creation (admin tool) ~aaronz
Modifying items
1. Change control panel to a "templates" and "evaluations" view
2. Create "items" view to support choosing and listing existing items
3. Allow users to remove unlocked items

Non-critical Tasks

Preview New Items ~whumphri (1.0+)
1. http://bugs.sakaiproject.org/jira/browse/EVALSYS-9
Evaluation Bean split and rewrite - EVALSYS-22 ~whumphri (1.0+)
1. http://bugs.sakaiproject.org/jira/browse/EVALSYS-22
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
debug: EvalStart page only show public template (it should include private template)
TAKE EVAL
the radio button of the first template need to selected by default for Start Eval Page
Create a include file for preview_eval.html and take_eval.html.
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).
On settings page if you use Cancel button several times...sometime something goes wrong.
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).
Improvement: move the setScale to logic layer and clean it more.
Add a comment question to all evaluations (use system setting to determine this)
In EvaluationDAOImpl.java see why DetachedCriteria not working.
Resolve bug: Item page check box "N/A" not value binding correctly when "preview" button was clicked before "save" button clicked
Resolve bug: Item Page radio button group "category" not value binding correctly when "preview" button was clicked before "save" button clicked
In assign eval page: Javascript checks on the HTML page (to be done by BeanGuards).
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.
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