[Contrib: Evaluation System] Seeking update on "in-progress" work for evaluation system

[Nicola Monat-Jacobs]

Thanks Jim. But OOTB in 1.4.x consolidated emails are NOT turned on right?
So my notifications should be fine right?


On Thu, Dec 6, 2012 at 11:24 AM, Jim Eng <jimeng at umich.edu> wrote:

> Nicola,
>
> We are reworking the consolidated email code that is in 1.4.0.  That work
> is nearly done.
>
> As a result of UCB and unicon work on emails that you mentioned, we
> learned that the requirements we gathered about two years ago were
> incorrect, and that is probably why you are seeing problems in 1.4.0.  We
> had tcons with everybody we could find who was using or considering using
> consolidated notifications.  Our understanding from that process was that
> either all emails would be consolidated notifications (specifically those
> using ConsolidatedAvailable and ConsolidatedReminder templates) and that
> nobody using consolidated emails wanted to send individual emails except
> for submitted confirmations.  So the current implementation in trunk and
> 1.4.x made the choice either individual emails or consolidated emails.
>
> Last year, after most of that work was done, UCB decided to start using
> evalsys and they thought email processing was totally broken in trunk
> because they could not send any individual emails when they had selected
> consolidated emails.  They committed changes that disabled the consolidated
> email processing and added options to "force send e-mail creation
> notifications" and "force send e-mail available notification".  After that
> was committed to trunk, we discussed it on the list, as I recall, and we
> concluded that the control email pages needs to be revised once again to
> reflect Berkeley's need (and probably your needs) without breaking things
> for other people.  Daphe circulated some sketches, as I recall, showing a
> UI that allows configuration of email settings for each type of email (e.g.
> available, reminder, created, etc).  For example, this would handle cases
> where someone wanted individual announcement emails but consolidated
> reminders, which is not possible now. I'm guessing no work has started on
> that.
>
> Michigan's current work has to do with processing consolidated
> announcement and reminder emails.  It will not include the cool changes
> Daphne suggested for the control email page.
>
> Jim
>
>
>
> On Dec 6, 2012, at 12:58 PM, Nicola Monat-Jacobs wrote:
>
> Thanks Aaron, that's what I originally thought, but those "Affects
> Versions" were throwing me off.
>
>
> On Thu, Dec 6, 2012 at 9:39 AM, Aaron Zeckoski <azeckoski at unicon.net>wrote:
>
>> First - all the UCB changes are in trunk only so if you are
>> experiencing issues in 1.4 (which is tagged before any of that work
>> was done) then it is unrelated to the UCB work. None of the UCB work
>> as been released (at least not that I am aware of) so it and all
>> related features are all for future release and only being run by UCB
>> currently.
>>
>> In general I would guess those affects versions are not correct.
>> Certainly that is the case for
>> https://jira.sakaiproject.org/browse/EVALSYS-1259 since it refers to
>> functionality that is not in 1.4.0. Same thing for
>> https://jira.sakaiproject.org/browse/EVALSYS-1261.
>>
>> -AZ
>>
>>
>> On Thu, Dec 6, 2012 at 11:21 AM, Nicola Monat-Jacobs
>> <nicola at longsight.com> wrote:
>> > Folks -
>> >
>> > I believe this is related to the EvalSys changes coming from UCB, but
>> I'm a
>> > bit confused about the JIRAs related to "in progress" notifications. I
>> know
>> > some work was done here which, I think, introduced a new notification? I
>> > remember seeing some notes about some of it getting rolled back? I'm
>> > assuming some of these plans are in confluence but I just can't find
>> them.
>> >
>> > Also, looking at the JIRAs makes me more confused:
>> >
>> > EVALSYS-1259: Affects Version is 1.4.0, Fix version is 1.5.0. But there
>> > doesn't seem to be an actual commit here. Okay, maybe its somewhere
>> else?
>> >
>> > EVALSYS-1261: Affects version is 1.3.0 and fix version is 1.5.0, but
>> looks
>> > like only commits to Unicon's branch?
>> >
>> > Basically, when I'm running 1.4.x, what do I have to do to get
>> functional
>> > notifications? Do I need some patches from 1.5 or what? Right now we're
>> > experiencing EVALSYS-1259.
>> >
>> > Also, 'available' notifications seem to be going out when the
>> notification
>> > is created, not when its open (if that date is set to sometime in the
>> > future). Is anyone else experiencing this?
>> >
>> > Thanks,
>> > Nicola
>> >
>> > _______________________________________________
>> > 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"
>>
>>
>>
>> --
>> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>>
>
> _______________________________________________
> 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"
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/evaluation/attachments/20121207/400ef760/attachment.html