ilios / lti-dashboard

LTI Application for the Ilios dashboard.

Ilios: Curriculum Management from UCSF

About

The Ilios Curriculum Management System addresses the needs of the Health Professions educational community by providing a user-friendly, flexible, and robust web application to collect, manage, analyze and deliver curricular information.

Ilios creates a comprehensive view of curricula by tracking events, learning content and activities over time. The system facilitates day-to-day administration and the delivery of information to learners; enhances curricular development, review and innovation; and reduces overhead for internal and accreditation reporting. The end result is a powerful tool creating complete and accurate pictures of complex, integrated, multi-year curricula.

Ilios manages learners and instructors and their relationships to curricular materials and activities, enabling the tracking of educational hours, roles and role transitions for participants both internal and external to an institution. Ilios also provides a robust, scalable delivery mechanism for user-centric calendar and scheduling information, with direct access to critical course information, materials, and other educational systems and services.

Ilios leverages the power of your existing online learning. With its comprehensive API, Ilios allows you to integrate with external data sources and systems. For schools using online learning systems such as Moodle or Canvas, Ilios provides a backbone of curricular information to make that deployment more robust and to complement the rich online tools, activities and materials already in use.

More Information and user documentation is available at iliosproject.org

Install and Update Instructions

Instructions for a new Install

Update Ilios

Upgrading From Ilios 2.x

Frontend Theming

For information about customizing the look and feel of the Ilios frontend for your respective institution, please visit docs/custom_theming.md for more information.

API Information

If you want to connect to the Ilios API a good place to start is docs/ilios_api.md.

Interacting with Ilios from the command line

Ilios provides a command line interface, see docs/custom_cli_commands.md for a list of available commands and how to use them.

Get Ilios

Download the latest distribution or clone the codebase.

Contact

For more information on Ilios please contact:

The Ilios Project * UCSF School of Medicine * 530 Parnassus Avenue * Box 0840 * San Francisco, CA 94143

Email: [email protected]

Development of Ilios

To get a development instance of Ilios up and running quickly, please review the steps in our Quick Setup Guide for Ilios for what is recommended and required.

lti-dashboard's Issues

switch to new page title library

see ilios/frontend#4246

school switcher and programyear switcher not working

does nothing.

Extra slash in auth/token requests

When we redirect to authorize the request we ned up with API//auth/token instead of API/auth/token.

switch to npm

update dashboard template.

follow frontend update.

refs ilios/frontend#4500

add license file

Add google analytics tracking

Add school-specific IT email address to configuration for display on errors

For non-UCSF schools that are using the Ilios LTI, when users experience an authentication problem, Ilios displays an error telling them to reach out to us at [email protected] and when they do so, we, in-turn, reach out to their respective school's IT people to request that they deal with it.

It has been decided that we need a configurable item in the LTI that requires schools to enter their own respective IT dept email address during setup so, when an authentication error occurs, their users are instructed to contact their own IT department at the appropriate address.

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml
• The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Missing Translations Abound

An in-range update of ember-ajax is breaking the build 🚨

The devDependency ember-ajax was updated from 3.1.2 to 3.1.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ember-ajax is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Commits

The new version differs by 3 commits.

• 430d11c chore(release): 3.1.4
• ba9a87d test: add test case around relative URL conversion
• daf8319 Revert "fix: don't append leading '/' when building url"

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

switch to new i18n library

warnings in build process

$ ember build -e production
 WARNING: Configuring icons in config/environment.js is no longer recommended
       and will be removed in a future version.
 
       Move icon list to config/icons.js for better performance.
       See https://github.com/FortAwesome/ember-fontawesome#subsetting-icons for instructions.
       
 WARNING: [ember-intl] `locales` is obsolete and can be removed from config/ember-intl.js.

resolve these warnings.

Prepare codebase for Ember 3

start by checking for deprecations. file additional tickets for addressing these individual deprecations as you find them:

https://emberjs.com/deprecations/v2.x/

What follows is a list of deprecations introduced to Ember.js during the 2.x cycle which will be removed with Ember 3.0.0:

Deprecations added in 2.1

• INITIALIZER ARITY
• EMBER.APPLICATION#REGISTRY / EMBER.APPLICATIONINSTANCE#REGISTRY
• EMBER.APPLICATIONINSTANCE#CONTAINER
• EMBER DEBUG FUNCTION OPTIONS
• EMBER.COMPONENT#DEFAULTLAYOUT

Deprecations added in 2.3

• INJECTED CONTAINER ACCESS

Deprecations added in 2.6

• EMBER.COMPONENT#DIDINITATTRS
• MODEL PARAM IN {{render HELPER

Deprecations added in 2.7

• EMBER.BINDING

Deprecations added in 2.8

• USE EMBER.STRING.HTMLSAFE OVER EMBER.HANDLEBARS.SAFESTRING
  
• ENUMERABLE#CONTAINS

Deprecations added in 2.11

• {{render HELPER
• RENDERING INTO A {{RENDER}} HELPER THAT RESOLVES TO AN {{OUTLET}}.

Deprecations added in 2.12

• Ember.K