[Contrib: Evaluation System] Status of Michigan work on evalsys

[Nicola Monat-Jacobs]

Jim -

Most these seem like new features, but if any of them do need to be merged in to 1.3.x (like EVALSYS-1068), please mark their 1.3.x status as merge if you can.

Thanks!

- Nicola

On Feb 2, 2011, at  7:04 AM, Jim Eng wrote:

> We have merged a few things to trunk since our last meeting:
> 
> EVALSYS-792	Preview of assigned evaluations should show names of actual evaluatees
> EVALSYS-863 	Make copying templates a local configuration option
> EVALSYS-861	Need a new property for selection of evaluations based on a locally defined selector
> EVALSYS-1068	Need SQL scripts to migrate from evalsys 1.2.x to 1.3.x
> 
> We have another piece of work that is ready to merge except for some final testing and verification:
> 
> EVALSYS-1031	Need an easy and routine way to update users assigned to an eval
> 
> We are working on a small cluster of issues related to email notifications.  Our current process for composing and sending emails seems to be a significant improvement over the system used in trunk (and 1.2.x and 1.3.x) of evalsys (cutting the time to process notifications by 80 percent or more).  This is most likely due to a custom database query that selects relevant information more efficiently.  That's at the heart of the work we are doing.  But we are also offering that as part of an improved user experience in which notifications are consolidated into a single email per student in most cases instead of sending multiple emails.  Here are the tickets:
> 
> EVALSYS-770	Fix inefficient TQ single-email-per-student notification queries/code design
> EVALSYS-1055	Separate admin settings related to scheduling email jobs into two sections
> EVALSYS-771	Support single-email-per-student email notification
> EVALSYS-765	Email Confirmation of Submission
> 
> We also have an implementation of an import mechanism in a separate project that depends on evaluation-api.  At this point, that has some Michigan-specific logic, but by the time eval 1.4.0 is ready, it should be useful to other people interested in import/export of eval data.  The initial work for that was done under this unresolved ticket:
> 
> EVALSYS-763	Provide import of Evaluations from XML files   
> 
> That project now has its own JIRA project: https://jira.sakaiproject.org/browse/EVALPORT
> 
> 
> 
> 
> _______________________________________________
> evaluation mailing list
> evaluation at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/evaluation
> 
> TO UNSUBSCRIBE: send email to evaluation-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"