Navigation Menu

Click the "+" to see inside a chapter or use the search to the right.

.

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: 2005 updates

...

Coming soon to ExamDeveloper 

...

References: Edition field for Book references

Available from2001 (approximately January 2020)
Rollout pace 
Last updated 

Starting January 1, 2020 we will no longer support any version of Internet Explorer. You can find more information on the future of Internet Explorer here: Lifecycle FAQ—Internet Explorer and Edge

Enhanced Matching items - Single target

Available from2001 (approximately January 2020)
Rollout pace Full rollout - users will have immediate visibility as a result of upgrade
Last updated 

Currently ExamDeveloper requires Enhanced Matching item to contain at least 2 targets when 1 target is supported by Athena. This change allows users to submit Enhanced Matching items with a single token and a single target added to the item.

Removing the 'allow enemies' configuration for sections and exams

Available from2002 (approximately February 2004 - 2006 (approximately April 2020 to June 2020)
Rollout paceFull Gradual rollout - users will have immediate visibility as a result of upgrademay gain visibility over several releases
Last updated 

We've heard that having the allow enemies check box on the build section/exam pages can be a hindrance as, if enemies are not allowed on a section or exam, then two items on the same section or exam cannot easily be made enemies of each other. The user is then forced to change the exam/section rule, to set up the enemy relationship.

Since we always show whether enemies exist or not when saving a section or exam, we will be removing this check box (for new and existing sections/exams). This means ExamDeveloper will:

  • Continue to show if the exam or section has enemies, whenever the exam or section is saved.
  • Always allow writers and reviewers to create enemy relationships, even if the two items to be made enemies are on the same section or form. 

Removal of 'Ignore Item Level Shuffle Response' setting

Available from2003 (approximately March 2020)
Rollout pace Full rollout - users will have immediate visibility as a result of upgrade
Last updated 

For QTI templates and packages, the Ignore Item Level Shuffle Response configuration highlighted in the screenshot below will be removed:

Image Removed

The Shuffle Response property in both the item Advanced Properties menu and the QTI PearsonSectionControl node will not be affected.

Image Removed

In the past, Ignore Item Level Shuffle Response has enabled users to ignore/omit the Shuffle Response property set in the Item Advanced Properties menu, when set to Yes or No. However, the new best practice is to have a value of Not Set when the user wishes to rely on the section attribute instead of the item attribute, per the screenshot below.

Note that this property can be set as the default for new items and/or batch edited for existing items.

Image Removed

Enhanced Matching items Scoring - option to use Add or Set

Available from2003 (approximately March 2020)
Rollout pace Full rollout - users will have immediate visibility as a result of upgrade
Last updated 

The current Advanced Scoring for Enhanced Matching only allows for the correct responses to Add correct combinations and does not have the option to Set. Also, the maxvalue adds up all the values of the possible outcomes and does not have an option to select the value with the highest score.

This change will allow users to decide to use Add or Set in Advanced Scoring for Enhanced Matching items. And, if Add is selected the maxvalue will be a sum of all the correct combinations. If Set is selected then the maxvalue will be the highest value.

Changes to project sharing rules for items and cases

...

For Book references, there is no dedicated field for Edition. With this change, a new Edition field will be added for book references. This field will be configurable in Project settings like other reference fields.

The initial roll out will allow Adding, Batch Editing, and Configuring the Edition field.

Subsequent roll outs will:

  • Display additional data for reference searches
  • Include the Edition field in reports,
  • Improve the user interface to promote Searching before Adding
  • Merge Duplicates

Changes to error notifications for Validators

Available from2005 (approximately May 2020)
Rollout paceFull rollout - users will have immediate visibility as a result of upgrade
Last updated 

When Validators validate an item or case is removed from a project, it is automatically added to the default 'itembank' project, which is not desirable behavior for many managers. We will be changing the rules around item and case sharing so that:

  • Users will not be able to remove an item or case from the current project if it is editable. They will see an error if this is attempted.

  • A user will still be able to make the item or case editable in a new project; doing so will also continue to make the item viewable in the old project.

  • Users will still be able to remove an item or cases from the current project if it is viewable. Furthermore, it will now be possible to remove the item from the default ‘itembank’ project.
  • Making items and cases editable, viewable or removing them from projects will no longer also share them automatically into the default ‘itembank’ project (this will now need to be a manual action.)

Note: this change will have no impact on sharing exams, sections, or collections, etc.

, they do not receive any errors if the item is missing required Metadata or if the Asset attached to the item in in an incomplete state. Moving forward, users will start getting error messages when the item advances to the Validate state if the item is missing required Metadata and/or if the item includes incomplete Assets.

Legacy custom report retirement 

...