Vendor Documentation
myCourses API access is available through Valence, D2L's extensibility technology which includes all the APIs, client libraries, and tools.
http://docs.valence.desire2learn.com/index.html
https://code.google.com/p/desire2learn-valence/
Academic Technology Support offers support to developers with regards to integration of approved projects with our myCourses environment at RIT.
ATS does not support or offer training for development with Valence. Support resources from the vendor through public channels are detailed at: http://docs.valence.desire2learn.com/about.html#support
Valence is governed by the concept of Calling Context for application access which may impact on the viability of your project. Valence applications only act under the auspice of a logged in user. An application will not be able to access information or perform actions outside of the access and permissions of the logged in user using the application. Valence applications will not be able to operate at a global level and access courses or features the logged in user does not have access to.
For example a student logged in to an application would not be able to access grades other than their own in a course and would not be able to manage grades. An instructor logged in to an application will only be able to manage the courses they are assigned to. A user logging in to an application would not be able to access items on behalf of another user.
All applications require a key to make calls to the Valence services.
Application Keys are issued for an individual application. Reuse or repurposing of an Application Key for another use will result in suspension of the key and suspension of the primary contact & associated parties from requesting future keys.
All requests for Key access must be placed by a faculty/staff member through our form***.
The requester will be considered the primary contact for that project.
External requests for key access submitted directly to the vendor will be denied.
Prior to each academic term Academic Technology Support will email the primary contact on a project who must respond to confirm the project is active and supported. If no response is received within seven days of the confirmation request the access key associated to that project will be suspended.
Key access is not granted directly to students. Any requests must be from a faculty/staff member who will be the primary contact for project. This sponsor is expected to maintain oversight of the project.
Per the agreement on the Key Request form, Academic Technology Support may request an archive of all active code for review at any time. Failure to supply the code within seven days of the request will result in suspension of the access key associated to that project.
Requests directly from a student
No direct student use, must be faculty/staff contact
Code access?
Account? Archive?
Active development against Dev
Approved by ATS for Prod access
Publishers contacted each academic term to verify it is an active and working tool.
No response within a week results in key deactivation
Exceptions may be made after review - Additional access, role permissions
Support contact statement
Web - Front page and link on all pages
Other - Help command includes support statement/contact
