Enhance editing notifications to notify edits on the API directly

Description

From on May 4, 2015 13:0

Polling notifications should respect the Sakai event system as well so we know about edits in the original gradebook. This assumes that an edit fires an event (check this). If so, we can listen for it and add it to the cache.

Copied from original issue: steveswinsburg/gradebookNGGIT2-65

Activity

Neal Caidin August 3, 2017 at 12:51 PM

This issue was imported from github issues. The use of Github issues as a bug tracker was an experiment with the GradebookNG (now just called Gradebook) tool development, released with Sakai 11. The information here may not be 100% accurate, please update or comment if any of the fields need updating.

jeffpasch March 9, 2017 at 3:45 PM

not a good solution for this one. closing.

Steve Swinsburg July 7, 2016 at 4:52 PM

  • The event sending needs to be made consistent in the GradebookService

  • There needs to be an event listener in the GBNG business service to pick up the event. However as above the data isn't great so it would need a DB hit to pickup the rest of the details.

  • The event listener would then pop the editing notification into the map

Steve Swinsburg December 2, 2015 at 1:55 PM

The gradebook API is inconsistent in its posting of events. Some actions send the gradebook.updateItemScore event, others don't do anything.

For the event that is posted, the data is:
/gradebook/bd659b9b-4daa-403a-9b82-b5ddd38e33db/item 3bb/276aca5b-0820-4861-9046-b05e4527d952/99.0/instructor

Which translates to: /gradebook/siteid/assignmentname/studentuuid/grade/rolethatdidit

Won't Fix

Details

Affects versions

Components

Assignee

Reporter

Labels

Created December 2, 2015 at 1:55 PM
Updated August 14, 2017 at 12:45 PM
Resolved August 4, 2017 at 1:03 PM