The big stuff you'll wanna know

We have two cool new features for you in this release - Score importing and question copying! Along with the usual cocktail of enhancements and bug fixes.

For authors & instructors:

When creating a new Obojobo Next LTI assignment you can choose to enable score importing. When a student is taking an LTI assignment with score importing enabled they will have the option to import a previous score instead of taking the assessment. If the student imports a score their number of attempts is reduced to zero and they're unable to start any attempts.
You can now copy and move questions into any question bank! To do it, click the details menu (...) of a Question Bank and click on the new Import Questions button. Any questions you import will be duplicated and appended to the bottom of your Question Bank.
The "Lock Navigation During Attempts" toggle has been changed to better align with the description. It now will lock navigation when an attempt is started and unlock navigation once the attempt is completed. Previously this was more confusing - it used to lock the navigation when entering the assessment section and unlock it when an attempt is over, requiring you to provide a button to allow students to leave the assessment section. If you want to replicate this behavior you'll just need to add an onNavEnter trigger to lock navigation and an onNavExit trigger to unlock the navigation. Note that this change doesn't impact or change any previous modules you've authored.

For students

If your instructor has enabled it on an Obojobo Next module assignment you can now import a previous score. When starting a module with importing enabled you'll see a dialog letting you know the option is available. Then, when you being an assessment attempt you'll be prompted with the choice to either import your previous score or to ignore your imported score and continue the assessment.
We've done some improvements with questions so that they won't jump around when interacting with them, making them way less annoying!

For developers:

This release includes updates for several packages and a database migration.

For administrators:

This release includes updates for several packages and a database migration.

For data nerds:

The following events have been updated with non-breaking changes:

assessment:attemptEnd: 1.2.0 → 1.3.0
assessment:attemptScored: 2.1.0 → 2.2.0

These events now include the following new fields in their payloads:

Property	Description
`imported`	Boolean indicating if this attempt was imported from a previous attempt
`originalScoreId`	If this attempt was imported then this is the internal `assessmentScoreId` of the assessment score that was imported. Otherwise `null`.
`originalAttemptId`	If this attempt was imported then this is the internal `attemptId` of the attempt that was imported. Otherwise `null`.

REST API Changes:

No changes in this release

New Feature Screenshots

Score Importing

Score importing is a new option you can enable that allows students to submit a previous score if they've taken the assessment for a module previously. When embedding an Obojobo module as an assessment item in your LMS there's a new option to enable score importing - you can see it here:

When a student first comes to a module which has score importing enabled (and they've previously submitted an assessment for this same module in the past) they'll see this dialog:

When starting the assessment they'll see this additional dialog giving them two choices - they can either import their previous score or ignore the old score and take the assessment as usual. If they opt to take the assessment they can no longer import their old score. Likewise, if they import their old score they can no longer take the assessment.

Editor Locking

We've added more safeguards when it comes to multiple authors working on an Obojobo module. Now if someone else is currently editing a module you'll see this screen:

This will help prevent you and the other author from overwriting one another.

As long as you're actively working on editing a module others won't be able to edit at the same time. If you stay idle for long enough you will see this warning message:

Once you return to the module you can continue editing. If you continue to stay idle for longer you'll see this message:

Most likely you'll be able to return to the module and continue editing. However if another user is attempting to edit this module at the same time they will be able to start editing once you are shown this message.

Copy & Move questions

A common request from faculty has been an easier way to move questions around. With this release you can now copy questions in your module into any Question Bank inside that same module. This allows you, for example, to copy practice questions from your module's content pages into your assessment Question Bank in order to have a starting point for creating your assessment. Or if you accidentally create questions in the wrong place you can easily import them into the Question Bank you intended them to land in.

To do this, make sure your cursor is somewhere in a question inside a QuestionBank, then click the details menu (...) button for the Question Bank. This shows advanced settings for the Question Bank, along with the new Import Questions button:

Clicking on this will bring up a window allowing you to select any question that has been found inside your module:

Note that imported questions are duplicated from their originals. The original question you've imported will be left untouched.

Here's what the complete process looks like:

Complete Issues List

The list of completed pull requests can be seen on our GitHub milestone page.

#1123 - 🛠️ Sometimes when answering a question the page could unexpectedly and annoyingly jump around. This enhancement includes updates to the focusing system to prevent the page from scrolling when interacting with a question.
#1384 - 🛠️ Small tweak to prevent the text cursor from showing up in non-editable areas of the Visual Editor UI.
#1385 - 🛠️ Restricts the width of the details menu in the Visual Editor. Long inputs such as very long page titles could cause this dialog to render in unexpected ways.
#1410 - ✨ New feature which lets you quickly import questions into any question bank
#1451 - 🛠️ Slight tweak to help make scrolling detection in the viewer more efficient
#1461, #1555, #1558, #1564, #1579 - ✨ Module launches can now enable the new score importing feature. This allows students to import a previous score if they're taking the same module they've taken previously. This also adds a new editor locking mechanism. This prevents multiple authors from accidentally overwriting work by editing a module at the same time.
#1486 - 🐛 Fixes the display of the edit-link menu in the Visual Editor in paragraphs with hanging indent enabled. Before this fix the menu would not be positioned in the expected place.
#1520 - 🛠️ Simplifies the "Lock Navigation During Attempts" toggle in the Assessment section detail menu. This option previously set a confusing mix of triggers that didn't align perfectly to the description of the feature (triggering the nav:lock action for onNavEnter, onEndAttempt, and onNavExit triggers). This now simply fires the nav:lock action for the onStartAttempt and onEndAttempt triggers, which aligns better with the expectation of the feature.
#1525 - 🐛 Fixes a bug that prevented you from editing the link address in the Visual Editor
#1530 - 🐛 Fixes an issue where deleting the Assessment would crash the Visual Editor
#1531 - 🐛 Fixes weird behavior when entering new lines in a Code chunk.
#1534 - 🛠️ Adds documentation in the Visual Editor Tutorial for the auto-width table cells that were added in the previous release (v10.1.0)
#1542 - 🛠️ Adds Github actions for automated tests
#1544 - 🐛 Fixes the heading menu in the Visual Editor for Safari
#1554, #1563, #1569 - 🐛 Fixes bugs when editing various details in the Assessment section details menu.
#1565 - 🐛 Fixed a bug where the warning that you can't have an empty module title wouldn't disappear once it was triggered

Issue legend:

✨: New features

🛠️: Improvements & enhancements

🐛: Bug fixes

Release Stats

Commits: 330
Developers: 6
Files Changed: 485
Lines Changed: 36,774 (+27,581 / −9,193)
Commit Dates: March 3, 2020 - October 5, 2020

Lines of Code (expand to view)

cloc ./ --hide-rate --by-percent cmb --read-lang-def=cloc-type-definitions.txt
    1986 text files.
    1756 unique files.
     279 files ignored.

github.com/AlDanial/cloc v 1.84
---------------------------------------------------------------------------------
Language                       files        blank %      comment %           code
---------------------------------------------------------------------------------
Jest Tests                       469          13.95           2.16          72750
Jest Test Snapshots              246           2.07           0.42          56668
JavaScript                       662          12.45           5.92          41214
JSON                              82           0.01           0.00          27628
Sass                             137          15.23           1.09           9751
XML                               31           2.36           5.25           1372
JSX                               29          10.90           0.90           1367
Markdown                           3          17.92           0.00            577
EJS                               12           8.79           0.93            483
SVG                               37           0.61           0.00            164
YAML                               3          19.42           7.77             75
---------------------------------------------------------------------------------
SUM:                            1711           9.10           2.23         212049
---------------------------------------------------------------------------------

Thanks!

A big thanks to our contributors for this release (listed in alphabetical order):

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

v11.0.0 - "Garnet"