I'm thrilled to announce the R package called "vvcanvas". This package provides a convenient interface to interact with the Canvas Learning Management System (LMS) API, enabling users to authenticate, retrieve course information, fetch specific details, and perform various operations within the Canvas LMS.
The package can be installed from CRAN directly using:
Alternatively, the development version can be installed from GitHub
How to Contribute
vvcanvas is an open-source project, and contributions from the community are highly encouraged. If you encounter any bugs, have feature requests, or would like to contribute code improvements, you can open an issue or submit a pull request on the GitHub repository.
I recently updated my Canvas LMS Mods (Basic) Chrome extension to provide some new enhancements to the course search and admin flyout menu inspired by ideas and requests I have seen from other users in the community.
My team is trying to replicate in one of our views how Canvas presents TODOs in its own UI. The TODO items endpoint (https://canvas.instructure.com/doc/api/users.html#method.users.todo_items) appears to be the correct one to use, although it's unclear what parameters Canvas itself may be using to for its presentation. As such, we have some questions about Canvas and the API.
When Canvas presents the TODOs in its own UI, what rules/boundaries determine the list of items that are being presented: 1. Does it present the user's most recent n number of TODOs? 2. Does it present the user's TODOs for the current term? 3. Does it present all of the user's TODOs ever? 4. Something else?
Learn about the Chrome extension that I've been developing as a personal side project to use with Canvas LMS to add some new features and help improve workflows. Most of the customizations so far are for the admin area of Canvas, but I am now working on adding some customizations that will add features in other areas of Canvas that could be useful to more users.
Following on from our CanvasCon 2018 talk, this article describes how we embraced the web’s shift to a decentralised stack (APIs, no-code, Notion, Zapier...) and created our own authoring system that creates engaging and responsive pages rendered in Canvas.