
2024-01-25
Release notes were designed to give an overview of new, enhanced, & fixed items released to our customers.
Release Date: 01/25/2024
New Features
Bricks Create
βOpen responseβ question type
A new, active learning question type is available. The βopen responseβ question type is another interactive way to keep learners engaged and assess their knowledge as they progress through an Rx Brick. Open response style active learning questions are supported on both the Android & iOS mobile applications.
To add an active learning question in a brick, perform the following steps.
When creating a brick, click on the β+β sign to add a new section, or, if youβre using the Brick beta features, type β/questionsβ to display an active learning question vignette.
Select the βOpen Responseβ question type.

When the brick is viewed by a reader, the open response question must have a question response before the βView Suggested Answerβ button is enabled.
[Example of empty response]

[Example that includes a response]

Brick Question metadata
ScholarRx collects the following metadata on all active learning question types, so our institutions have insight into:
Who answered (student name)
How the student answered (answer selection)
When the student answered (date & time)
Intralinking
Brick authors can now create a link to another section within the same brick making it easy for readers to βjump toβ related brick data.
To link a brick section to another section within the same brick, perform the following steps.
Click and drag to select the desired text. The toolbar displays.
Click the drop-down menu and then click the βlink to sectionβ option.

An instruction modal displays at the bottom of the page.

Click the section to link to & then click the βConfirmβ button to complete the link or click βCancelβ to cancel linking.

[Resulting brick view]
When clicked, the selected word or phrase provides a method for the reader to βjump toβ the linked section.

To unlink a previously linked section, perform the following steps.
Select the text to display the toolbar.
Click the drop-down menu, then click the βLink sectionβ option. The text will become unlinked.

Gating
Gating provides a method for a brick author to restrict a readerβs progression to the next section of a brick until they interact with a question or a flash card.
There are several gating rules that authors and readers should be aware of. This logic ensures that readers are always studying from, and interacting with, the most up to date content.
The following table describes these scenarios.
When the selected correct answer of a single or multi-select question answer is edited or changedβ¦
The question is re-gated & any subsequent gates are re-gated.
When any other part of the question is edited (i.e. question, incorrect answers, explanation) β¦
The question is not re-gated.
When edits are made to flash cards or open response style questionsβ¦
The flash card and/or open response question is not re-gated.
When you drag a previously gated item below any other gated itemβ¦
The item that was reordered, and all gated items below it, are re-gated.
When a gated item is reordered, and itβs the last gated item in the brickβ¦
The item is not re-gated.
When an author goes back into a published brick and adds a new gated item above another gated itemβ¦
All items below it are re-gated.
To add a gate, perform the following steps.
In Bricks Create, open the desired brick, or create a new brick.
When a question or flash card is added, a new checkbox is displayed at the bottom of the section. When enabled, the question or flash card is βgatedβ and will require a reader to interact with it before progressing to the next brick section.
[Gating example for a question]

[Gating example for a flash card]

When a reader gets to a gated question or flash card, they must interact before they can progress to the next section of the brick.
[Reader view example β open response style question]

When a question response has been entered, or a flash card has been flipped (clicked), the βContinue to Next Sectionβ button is enabled. When clicked, the next section is displayed, and the reader may continue.

Note: When there are locked gates in a brick, a reader will not be able to use the table of contents to navigate to those sections until they are unlocked.
[Table of Contents example with locked gates]
The orange text represents a section with an unlocked gate. The black text represents a section with a locked gate.

Enhancements
Bricks Create
The following enhancements were made to the Bricks Create application.
Angular update
Angular was updated to version 17 for the Bricks Create application.
Create brick from file β language selection added
When creating a brick from an existing file, a brick language selection drop down has been added. When a language is selected and the file is converted to a brick, it will be converted into the selected language.

Preview button
A βpreviewβ button was added so authors can more easily preview a brick before publishing it.

When clicked, the author is redirected to the Brick Exchange, and the brick displays in a simulated reader view with a red preview banner at the top to aid the author in understanding that the brick is being viewed in preview mode.

Parse nested lists
When a brick author selects the βBegin with Fileβ option to create a brick from an existing file that contains a nested list (bulleted and/or numbered) it can now be parsed properly. This enhancement removes the need for the author to format the list manually after the brick has been created.

Reorder vignettes
Previously, brick vignettes could only be reordered by clicking on up/down arrows. This functionality has been enhanced to make reordering easier. Click the reorder icon next to the desired brick vignette and drag/drop it into the new position.

Brick vignette IDs
Brick vignettes (βsectionsβ) are assigned unique IDs. Previously, when a new version of a brick was published, new vignette IDs were assigned. This prevented brick authors from linking a vignette to another vignette within the same brick. Now, vignette IDs are carried forward during the publishing process; thereby providing a method to successfully utilize the Intralinking feature.
Brick Exchange
The following enhancements were made to the Brick Exchange.
Image & institution name added to profile
To personalize your Brick Exchange experience even more, your profile image will now replace the default profile image, when added.
To add a profile picture through the Brick Exchange, perform the following steps.
Log in to the Brick Exchange at: https://exchange.scholarrx.com. The Brick Exchange dashboard is displayed.

Click on the profile icon, then click the βMy Profileβ option.

The profile page is displayed.

Click the three dots to the right of the βshareβ button, then click the βEdit Profileβ button.

The 'Edit Details' modal is displayed.

Click the camera icon and select an image to upload.

5. Click the βSave Changesβ button to save the profile details.
The profile image now displays in place of the default profile icon when using the following applications.
Bricks Create
Brick Exchange
Faculty Portal (role required)

When the profile icon is clicked, the institutionβs name also displays.

Note: The USMLE-Rx profile will be updated in a future release.
Brick Views β tracking unauthenticated visits
Brick views by unauthenticated users (users who arenβt logged in) in the Brick Exchange are now being tracked.
Brick Views - context collection
When a brick is viewed, context for that view is collected to make the future home page and βwhatβs nextβ experience better. Brick visit context will provide insight on how a brick was visited (i.e. from a brick collection, from a reading list, etc.).
Fixes
Bricks Create
The following fixes were applied to the Bricks Create application.
Edit label on interactive images
When a ScholarRx brick is cloned by an author and it contains an interactive image, the image label can now be modified.
Search - missing brick titles
Previously, when a brick title was added after the brick was initially saved, the title was not picked up during the indexing process. This resulted in brick titles that couldnβt be searched.
Last updated
Was this helpful?