In 2.4.0+ (after SAK-6207), logged events don't include context (siteId). Looking at SAK-6207 events should begin with: /gradebook/SITEID/(...)
Logged events are of the following form instead:
| /gradebook/1/New item | gradebook.newItem |
| /gradebook/1/2/instructor | gradebook.updateItemScores |
| /gradebook/1/instructor | gradebook.downloadRoster |
| /gradebook/1/new gb | gradebook.newItem |
Even if the contextId is not a siteId, it is usefull that this gets logged in the logged event REF field. In this case (and for specific case of SiteStats), I can be aware that this context is not a siteId so i can retrieve the siteId (if it makes sense) and associate the events with it (so SiteStats can manage Gradebook events).
Nuno Fernandes - 21-Dec-2007 01:50 Louis,
Even if the contextId is not a siteId, it is usefull that this gets logged in the logged event REF field. In this case (and for specific case of SiteStats), I can be aware that this context is not a siteId so i can retrieve the siteId (if it makes sense) and associate the events with it (so SiteStats can manage Gradebook events).
Thanks,
Nuno
hey Nuno,
disregard my previous comment - actually i used the gradebookId as the contextId but i should have used the gradebookUid as the contextId. the gradebookUid is the same as the as the siteId in which the gradebook is located.
Louis Majanja - 21-Dec-2007 10:59 hey Nuno,
disregard my previous comment - actually i used the gradebookId as the contextId but i should have used the gradebookUid as the contextId. the gradebookUid is the same as the as the siteId in which the gradebook is located.
Even if the contextId is not a siteId, it is usefull that this gets logged in the logged event REF field. In this case (and for specific case of SiteStats), I can be aware that this context is not a siteId so i can retrieve the siteId (if it makes sense) and associate the events with it (so SiteStats can manage Gradebook events).
Thanks,
Nuno