This session is all about souping up and fine tuning the course development engine at your institution, not just through best practices, but through custom-built tools that extend the Canvas platform to add pedagogical value, speed development, and aid continuous development tracking. It's instructional design empowered.
Presenter: Neal Legler - Utah State University
Location Map & Room: ARCHES
Login to "Add a comment" below!
Can you post your presentation on this site (or a link to it)? I am interested in the last part of the presentation, your overview of the course checker (I can't remember what you called it, but the thing you ran to check if course are ready!)...
Thanks for checking with me on this. Here is a link to the slides: INSTCON 2015 - Supercharge Course Development Process - Google Slides
For the course-development tracker, we don't really have a non-USU-specific version that is available for general use at the moment, so the only place where it is accessible is in our account admin space. However, I do have a screenshot in the slideshow, and if you are interested in talking more specifically about what we did, we can arrange a conversation sometime. A basic description of how it works is as follows:
Everything is developed in PHP on a Bootstrap CSS framework using a MySQL database and some JQuery.
I hope that helps! Thanks again for your interest.
We are only starting on our Canvas Journey. We go live in June '16. So when I see things like your CD Tracker, I get really excited about it! That would be an awesome tool for our department. Currently we don't have the talent to create something like this, so I will take the screen shot and description and go searching!!!! Hopefully as we go on this journey we will be picking up lots of knowledge... right now it is ALL overwhelming. Your workshop showed some really great goals for us!
BTW -- we are looking for an Instructional Designer (send great people our way) UTPB.edu
I attended your session, Awesome! Your school has done some amazing things. I was so impressed with the Design Tool.
Towards the end of your session you were talking about tracking and reporting tools. I'd like to get a few screenshots. Particularly, the sample report that shows the list of courses (with the icons on the side) that indicate if the course has a syllabus, assignments, etc. and if it's published. I'd also like to see the pie chart that you showed.
Is this reporting tool something that Canvas helped you write? Can you share this?
Thanks so much.
Hi @Sylvia_Ami ,
It is really embarrassing for me to be responding to your message one year later. I honestly need to login to the community much more often than I have been able to this past year to check on things and collaborate more with others. I am getting ready this year's presentation and thought to look back at last year's and came across this. I think I got lost in post InstCon15 catch-up and missed this message when you sent it earlier.
Here is a screenshot of our development tracker:
Here are the pie charts, made using highcharts.com:
These were all built in-house by our developer, Kenneth Larsen, using the Canvas APIs, so we didn't use any pro-services for this.
We have added a couple of features since last year. Now we can merge courses from the list (a new feature that will remove some of the N/A options that take up so much of our pie chart now), plus the ability to export a CSV file that lists one instructor per-row along with a horizontal list of their classes, start and end dates, assigned designer, and content deadline so that we can run it through a mail merge and send out "personalized" reminder emails ahead of the new semester.
We haven't really found a way to share the development tracker, since it's so specific to our operations, but we'd be happy to work with someone to give insights. Our design tools, as of a few months ago, are now being offered as a SAAS solution by CIDI Labs, a spinoff from USU: Cidi Labs | Instructional Design Tools for Canvas
Thanks for your patience, and sorry again for the insanely delayed reply.