-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assignment object due date extension #66
Comments
If we don't want to replicate that, but we want to use their extension, then JISC need to change that before we implement it differently here. |
I think @andrewhickey had an issue with that. |
Which events was this intended to be added to @garemoko? |
Both the assignment ones (graded and submitted) |
Ok nice, thanks @garemoko 👍 |
Note to self this is for |
@ryansmith94 do you know if that's still an issue? |
No it's no longer an issue according to example statements I've seen and their documentation. |
Edited the issue to remove that note. |
JISC branch has been merged into master. We are good to go here! |
* switch survey to submitted to remove conflict * disambiguate scorm content from module * scos dont have intros
JISC have an extension http://xapi.jisc.ac.uk/extensions/duedate which contains the assignment due date as an ISO 8601 timestamp. We should use this.
The text was updated successfully, but these errors were encountered: