Does anyone have an implementation process they would share as to which LTI apps you open/add in your instance of Canvas? We thought about having our faculty go through their department head, but just curious if anyone does anything else. There are so many to choose from! I appreciate any thoughts you care to share.
We don't have a formalized process, but we do try to have departments/faculty opt-in for most LTIs. For some big ones (such as our media management system) we'll do it at the account level, but in general we try to leave it at the lowest level possible. That's because each LTI adds another line to navigation, or widget to the editor, or another line in the external tools, which can get overwhelming if every single one of them is available for every class. Generally, our guideline is that faculty can request LTIs that require no additional funding for their course, and deans/dept heads can do the same for their department. However if funding is required, then further negotiation must occur to determine who's paying for it and who will be the point person with the LTI vendor.
Then I create a folder in our file management system (SharePoint) for each LTI that includes any documentation from the vendor, information on the vendor and point person, and the settings used to install the LTI. I also include a copy of the email(s) requesting the LTI so we can backtrack everything if needed. It's also handy for if another admin ever has to step in and take over Canvas.
Sorry I couldn't provide more specifics on a formalized process - we usually leave it pretty loose because each LTI is different, and is at a different level of support from the vendor by the time I get pulled in.
Thank you for your response, Anthony! Right now, we are doing a similar process to what you have in place. So it's good to know there are other college that have the same view. I like your system for tracking the request and the documentation you keep. Our college would like to use a project tracking system for faculty to request the implementation of an LTI. That way our department can also track the time spent on these requests as well as who and what is being requested. I appreciate your feedback; thanks so much!
We have taken the approach of hiding most apps from the EduAppCenter and only leaving six of them available (all free) to faculty. Faculty can still search the app center to see what is out there, but they have to make a formal request using an LTI template (developed in Word). This ensures we capture all details and can track each LTI through approval, testing, and implementation. The same applies for all non-app center LTIs. For the most part, we prefer to configure at the account-level and open for all, when possible.
Thanks for the info Shane! Sounds like you have a great plan in place; may have to borrow a few steps.
Hi Shane: Are you willing to share your request template that your staff use to request an LTI implementation? Thanks!
Thank you, Shane! This is great info! It definitely gives me a starting point on formulating a process for us.
At Ohio State we have created a process for requesting integrations in to Canvas.In addition to the core integrations, we have turned on the integrations that OSU has university wide license for such as Box, LockdownBroswer etc.
For any new integrations users must submit an online form. Once it’s been reviewed by internal support team, we take the integration through a security and legal review. This process can take anywhere from 2-3 months depending on schedules, complexity of the product and other issues associated with it. So in the online form we collect a lot of information from the requestor which gives us a lot of information about what is the purpose of this integration, who is buying /paying for the tool, who will support it, who is affected by this who is main contact point etc. This also allows us to enforce the idea that this is a time consuming process and requires detailed review by several groups and lot of resources before it is approved so they want to be mindful of that as well.
Once it has been cleared by Legal and Security, we install the integration in our QA environment .After thorough testing, we move it to production.
We are in our first semester of Canvas in production this Summer so we have not had to do this yet but we will be interested in looking at restricting integration to certain sub accounts when needed. If you have any questions please feel free to send me a message.
Thank you, Preeti, for taking the time to respond. I'm a bit amazed by your process, but certainly understand the need for it in a college the size of Ohio State. At this point, we may start with an online form, and I appreciate the points you've shared about what needs to be provided for a potential integration.