Request Technology Adoption

If you are developing a new learning technology or would like to recommend a tool for adoption into the wider Learning Technology Environment, a number of things will need to be considered. Key issues include the privacy and security of the data collected and stored; the standards for integration and event handling used; and the suitability and sustainability of the technology for ongoing UBC support.


Adoption Guidelines

Primary guidelines for wider institutional adoption, integration, and support of new learning technology are as follows.

Early Integration: Generally, while technology is in experimental / development / pilot stages, UBC does not support integration with institutional data sources or other learning technologies within the Learning Technology Environment (this includes all current centrally supported tools). Exceptions may exist where technology cannot effectively be tested without some level of integration.

Privacy Considerations: In order for any technology to be considered for institutional adoption (and integration), it must be able to integrate into the Learning Technology Environment in a FIPPA-compliant way. For all new technology that utilizes UBC identity data, a Privacy Impact Assessment will also need to be completed. When technology comes from an external vendor, an agreement with the vendor around confidentiality and security of data may also be required.

Integration Standards: UBC privileges standards-based approaches to integration, using integrations such as Learning Tools Interoperability (LTI) or LTI Advantage and authentication services such as Shibboleth, CAS and ELDAP. It is also desirable that technology adopt standards-based methods of storing and emitting learning events, such as Caliper or xAPI, for learning analytics.

Pilot Process: Learning technology requires piloting with instructors to generate evidence of value for the institution before consideration of institutional adoption. A pilot evaluation framework has been established to support this process. Upon completion, evaluation reports are reviewed by the Learning Technology Environment Operations Committee before going to the LT Hub Leadership or Learning Technology Leadership Team, as appropriate, for decisions about institutional adoption.

Central Support Criteria: In order for the LT Hub support group to onboard a learning technology as a managed support service, the technology needs to demonstrate a degree of impact (numbers of users / faculties that will benefit) and/or uniqueness of functionality (differentiation with other tools within the Learning Technology Environment that are currently supported). Best effort support will be provided for adopted technology that falls outside this criteria.

Code Review: Where the LT Hub is requested to administer new technology, peer review of the code base and system dependencies may be required. Technology may also be scrutinized for sustainability of service and the ability to resolve functional issues and security bugs in a timely fashion.


Development Recommendations

If you are developing a new learning technology, here are best practices for aligning with ecosystem requirements:

  • Consult with the LT Hub at the start of the project to understand how the proposed technology may fit within the overall Learning Technology Environment and align approaches for coding, data privacy, event handling, and integration with institutional practices.
  • Consider involving LT Hub development resources to oversee development.
  • Utilize LT Hub peer review to review code during development.
  • Consult with LT Hub about evaluation support for piloting and evaluating the technology, once developed.

Technology Requests

If you are interested in investigating the integration of a new/developed learning technology into the Learning Technology Environment, contact the LT Hub to arrange a meeting with our team to discuss the next steps. These steps include:

  1. Conducting a market scan to determine if any other technology contains the particular desired functionality.
  2. Investigating the use of other technologies already available in the UBC Learning Technology Environment for the same purpose.
  3. Confirming the technical specifications and privacy requirements of the new technology meet UBC standards.
  4. Potentially organizing a limited pilot of the new technology.