I don't think there are instructions on how to set up Kolibri to use Postgres as an alternative DB. Here's what @lyw07 shared with me on how to do it:

1. Install postgresql (brew install postgresql if you have mac + homebrew)
2. install psycopg2-binary from pip (pip install psycog2-binary)
3. set env var KOLIBRI_DATABASE_ENGINE to postgres
4. set other env vars KOLIBRI_DATABASE_NAME, KOL

It seems like configuration settings are more or less thrown in as people think of them into config-dist.php. Would it possibly be easier to read as well as modify and put into version control if this was abstracted to a yaml or json file that config then loads in? This would also make it easier to write a CLI / YO that could write the config options automatically for people increasing devUX down

"could add the human-friendly labels you just added this week (e.g. SU201819)"

Same method of adding that we do for the two parts of the UI recently but make sure it's on the section list page. With how annoying the drupal view template would be to modify it might be better to just make it a OPA

Update visual style of "last note" to match levels page, counselor meeting page, and school dashboards (eg, blue badge):

before

after

<img width="185" alt="Screen Shot 2019-09-27 at 3 10 35 PM" src="https://user-ima

aLinksToMultiMediaRequireTranscript should include more video file extensions, such as .mp4 or .m4v

https://github.com/ucfopen/UDOIT/blob/214bc8c7ef688f6dc2187d5ba7631385a940b5d2/lib/quail/quail/common/accessibility_tests.php#L230

Make a technical architecture document, and remove outdated docs in https://github.com/sagefy/sagefy/tree/master/docs

outline

• title
• description of the doc (whats in, whats out)
• system diagram & definitions
• postgres
  • model definitions and
  • relations diagram,
  • migrations
  • local test ci prod
• service
• client
• nginx
• experience: page screenshots and flow diagr

If a teacher goes through to give specific grades to a number of different students in a group, the "apply to all" button becomes destructive. The button is useful if a teacher accidentally applies a score incorrectly to everyone, but the destructive nature of the button should be conveyed if it is hit accidentally.

To avoid annoyance when teachers want to use to to apply to everyone, possibly

Expected behavior: It should stay at the end of the video.

Our README, especially the part with setup instructions, is pretty out of date.

We need to add/update a few things:

• Specify that a Redis server is necessary for the project to run
• Document and/or link to documentation how to set up Redis
• Show how to setup the RQ worker
• Ensure that the rest of the existing setup docs are still accurate

The guide links are listed like this in on the page for each widget:

But the tabs are listed like this on the guide pages themselves:
<img width="306" alt="Screen Shot 2019-09-27 at 10 55 27 AM" src="https://user-images.githubu

There should be a test in studygroups/test/test_facilitator_views.py for adding new courses.

When updating the due dates for a lot of quizzes/assignments and a due date is after a availability date an error message comes up. However, the error message referrers to an ID # which does not show by the quizzes/assignments so there is no clear way to determine which one has the issue. See attached for the error message.

![image](https://user-images.githubusercontent.com/46006287/50287695-9

Would require an algebra evaluator to express the solutions has a formula of random numbers. Note that labels should be turned into templates that display random numbers.

See:

• http://algebra.js.org
• http://mathjs.org

Needs to be developped with #248.

Currently the MWDK will check to see if src/_guides exists and, if so, run the creator and player guide files through a plugin to be fully generated.

This is fine most of the time, but if a widget is using the default creator it doesn't really need a creator guide - but if there isn't a creator guide, the build errors.

We're delivering badges through UCF's CredHub. Which itself, proxies badges to Credly.

Credly requires first and last names when sending badges to users that don't exist yet, and we are only sending first names.