Navigation Menu

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

.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 72 Next »

Disclaimer: in order to ensure we make the right decisions for the future of the application, we may change or remove the information that appears here at any time

Coming soon to ExamDeveloper

 

Cases: Separating the split screen exhibit from the case

 

Available from

1810 (approximately October 2018)

Rollout pace

Full rollout - users will have immediate visibility as a result of upgrade

Last updated9-November-2018

 

Case lead-in text is intimately linked with the case, but this makes it difficult to define whether a case is a question type, a grouping of questions, an exam section or a supporting display exhibit, which make cases near-impossible to enhance and maintain without impacting other areas of the application.

We are taking steps to more robustly define and separate the individual components that make up a case, so that we can deliver additional case enhancements in future. This will result in the following initial changes:

  • New and existing case lead-in text and language will be treated as a display-only question type (referred to now as a case exhibit) with its own history and Question ID.

  • Users will have the ability to search for case exhibits and set metadata, enemies, blueprints, advanced properties, etc. against them, but configuring this data will not initially be available on the add/edit case page.

  • The case exhibit blueprint will be ‘Unassigned’ by default.

  • The case exhibit language and lead-in text will remain attached to the case, editable via the same pages, and deliverable to candidates in the same way.

  • Case exhibits will show up in the split screen exhibits menu when modifying a case question alongside stand-alone exhibits, and it will be possible to sequence the tab display order alongside stand-alone exhibits that don’t belong to the case, for that question.

  • When a case is deleted, it will be possible for the case exhibit to remain attached to the case questions in the project (as a stand-alone exhibit), but the ‘grouping’ of questions will no longer exist.

  • New cases will use the default project settings for split screen exhibits. Most existing projects are currently configured to have a default ratio of 0.5 and do not allow candidates to adjust the size of the split screen, whereas existing cases will continue to have a ratio of 0.45 with the ability to adjust the split screen size.

  • A case name must be unique within the itembank - if, after upgrading, you have more than one case with the same name in the itembank, you will receive an error upon saving.

  • When a question is removed from a case, the case exhibit will be removed from that question automatically.

  • It will be possible for writers to submit the case exhibit for review (it will be reviewable independently like any other display-only question type), and they will not be able to edit the case exhibit while it’s not in a Draft or Rejected state.

  • Clicking ‘Submit All’ on the add/edit case page will also submit the case exhibit for review, alongside any case questions.

  • Case enemies and language will become part of the case exhibit. Consequently, exams and sections will check for exhibit enemies when saving.

  • A new case revision will be created whenever a user:

    • Changes the case name.

    • Adds or removes a question on the case.

    • Reorders questions on the case.

    • Changes the lock response configuration for questions on the case.

  • Changes to case exhibits and questions on the case will not create a new case revision, but they will create a new question revision.

  • A user will always see the latest revision of questions and case exhibits that are attached to the revision of the case they’re viewing.

  • When sharing case questions or case exhibits across projects, then the case (and other questions on the case) will be automatically shared in the same way.

  • When performing a question search by Case Name, if no case name is provided then the search will return questions that are on any case in the current project, instead of all questions in the project (regardless as to whether they are on a case or not.)

  • It will no longer be possible to search for assets by the ‘On Case’ criteria.

  • It will no longer be possible to search for questions by the ‘Order on Case’ criteria.

  • When performing a case search:

    • It will be possible to search by Case ID (which will no longer contain the case exhibit language), Case name, Case exhibit language, and Case exhibit text, and On exam form on the view cases, build section, build exam and case project sharing pages.

    • It will no longer be possible to search for cases using the following criteria: Editable On, Viewable On, Written By, Date Written, Date Modified, On Exam Section, Question ID, Blueprint ID, Type, Stem Text, Option Text, Question Metadata, Comments, External Id, Reviewed by, On Collection (Note that this does not affect searches that return questions instead of cases.)

  • The error that prevents cases from being saved if it contains two questions that are enemies of each other will be removed.

  • When importing an enemy relationship for a question or exhibit that is on a case, other questions on the case will no longer automatically be made enemies (e.g., Item A is made an enemy of Item B, which is on a case with Item C; Item A will no longer automatically be made an enemy of Item C, but it will be possible to set this relationship manually or by using the enemy import spreadsheet).

  • It will be possible to see how many questions are on the case on the view cases page.

  • The case ‘type’ column will be removed from the application.

  • The section and exam imports (in XML and XLS format) will allow users to add case questions using the <question> element instead of the <case> element.

  • On the enemy import spreadsheet, if a user sets a question as an enemy of a question belonging to a case, ExamDeveloper will no longer make other questions on the case enemies automatically. Users will still be able to define enemy relationships with other case questions manually via the spreadsheet.

  • Case lead-in text will be removed from the newest custom report.

  • The question import templates will be updated to create cases in a different way:

    • On the spreadsheet import, the cases tab will be removed and replaced with columns to indicate the case name on the questions tab.

    • On the XML import, <case> will be removed and instead case exhibits will be created using <question> (marked as a display type). It will be necessary to reference the case name from both the case exhibit (using a new <case> element), as well as from any questions that should be attached to the case (using the existing <exhibit> element).

  • Existing 'HTML for translation' files containing cases that are not imported prior to upgrade will not be importable, and will have to be re-exported after upgrading.

Cases: adding a subset of case questions to a section or exam

Available from

1810 (approximately October 2018)

Rollout pace

Full rollout - users will have immediate visibility as a result of upgrade

Last updated

13-September-2018

 

Today, if a case is added to an exam or section, then all questions on the case must be added. We intend to enhance the application to the point where it is possible to add individual case questions to an exam, without forcing the user to add all other questions on the case. This will result in the following behavior changes to the add/edit exam and section pages:

  • The ‘Add cases’ tab will be removed.

  • It will be possible to search for case questions on the ‘Add questions’ tabs, and add them individually to the exam (like any standalone question works today.)

  • It will be possible to see which case a question belongs to on the build section / exam pages.

  • If case questions are on a section or exam, and more questions are added to the case, these will not automatically be added to the section/exam.

  • If case questions are on a section or exam, and those questions are removed from the case (or the case is deleted), these will not automatically be removed from the section/exam.

  • The section and exam imports (in XML and XLS format) will allow users to add a subset of case questions.

  • When adding case questions directly to an exam, if the project configuration setting ‘Export cases as sections’ is selected, then a section will automatically be created for each case being added. (If the setting is not selected, then case questions will continue to be added to the ‘Unsectioned’ section that is automatically created.) This rule will always be obeyed, and so if the setting is changed, existing draft exams will be updated.

  • When an exam or section is published, the latest revision of standalone exhibits will now be ‘locked in’, just like case exhibits and questions are. (Note that assets will still not be a part of the locked in content.)

  • When saving a section or exam, there will be a check for exhibits that are enemies of each other, or of other questions, on the same section / exam.

  • The ‘Selected’ tab will be removed.

  • It will be possible to reorder questions and sections on a new tab named ‘Contents’, which will replace the existing ‘Questions’ tab.

  • It will no longer be possible to create more than one ‘Unsectioned’ section (e.g. in the instance where a user had a selected tab contains a question followed by a case or section, followed by another question.)

  • When new questions are added to an exam or section, ExamDeveloper will add them to the end of the existing section, starting with standalone questions (in Question ID order), then case questions (first by Case name, then by Case question order.)

Enhanced matching questions in the custom report

Available from

1810 (approximately October 2018)

Rollout pace

Gradual rollout - users may have visibility over several releases

Last updated

11-October-2018

 

Enhanced matching content in the custom report is limited to just the stem. This enhancement makes it so the custom report (in XLSX and JSON formats) export the following additional information:

  • Template name

  • Canvas background image filename

  • Token, Target and Label data: (1810 release)

    • Ident

    • Text (without formatting)

    • Background image filename

  • Scoring rule data: (1811 release)

    • Compatible token(s)

    • Correct token(s) (key)

    • Rule #

    • Combination

    • Item Score

In the XSLX formats, this additional data appears on a new worksheet labelled ‘Enhanced Matching’ (if you are exporting any). For consistency, the existing worksheet “Sheet1” is also permanently renamed “Questions”.

Branching configurations in a review workflow

Available from1810 (approximately October 2018)
Rollout paceGradual rollout - users will have visibility over several releases
Last updated13-September-2018

 

In ExamDeveloper it is currently possible to set up a review workflow that forces a reviewer to do one of two things:

  • Accept the question, which moves a question to the next state in the workflow
  • Reject the question, which moves a question to any previous state in the workflow.

We will enhance the configurability around this decision making process, to give managers greater control over where their reviewers can send questions in the workflow:

  • ‘Accept’ and ‘Reject’ will be renamed ‘Advance’ and ‘Return’ respectively, in order to indicate the direction that an item is travelling in through the workflow.
  • For each review state, project managers will be able to configure the ‘outcomes’ that are available to the reviewer when they decide to advance or return an item, for example:
    • Allowing reviewers to skip a state when advancing a question (to other review states, validate, complete and obsolete).

    • Restricting the reviewer to a specific state or states when returning a question; or offer no ability to return a question.

    • Requiring a reviewer to add a comment when advancing a question.

    • Configuring whether the reviewer should decide to retain statistics or not (i.e., automatically retain them without offering the choice.)

  • If multiple reviewers are required to advance or return a question, then the last reviewer required to trigger the state change will continue to choose the outcome.
  • A reviewer will be able to modify a question during review and save their changes without that modification automatically counting as advancing the question.
  • Question history  / user tracking will reflect the outcomes and path that a question took through the review workflow at the time, even if the project’s review workflow configuration is modified later.
  • The user tracking tab will continue to reflect the review workflow in the order that it is sequenced, meaning:
    • If an outcome returns a question to a previous state in the workflow, then user tracking is reset back to the new state.
    • If an outcome advances a question through the workflow, and a state is skipped, then the latest question revision will show that skipped state as ‘Not reviewed’.
  • Existing review workflow configurations will continue to behave as they currently do, but can be updated to take advantage of the new functionality.

  


Ability to set numeric range response option for Fill in the Blank items

Available from

1811 (approximately November 2018)

Rollout pace

Gradual rollout - users may have visibility over several releases

Last updated

8-November-2018

 

Today in ExamDeveloper it is not possible to set numeric range as a response option for Fill in the Blank items. With this enhancement, users will have the ability: 

  • To define numeric range response option for Fill in the Blank items. (1811 release)

  • To set attributes - Column width, minimum characters and maximum characters for various options. (1811 release)

  • To import numeric range options through XML and XLS imports (1812 release)

  • To import attributes - Column width, minimum characters and maximum characters through XML import (1812 release)

  • To export numeric range option in Custom reports / MS-Word and XML exports (1812 release)

  • To export attributes - Column width, minimum characters and maximum characters in JSON format Custom reports (1812 release)

Rich Text Editor upgrade

Available from

1812 (approximately December 2018)

Rollout pace

Gradual rollout - users will have visibility over several releases

Last updated 

 

We are enhancing the Rich Text editor in ExamDeveloper to the latest version. We will also be streamlining the editor to allow only the HTML elements that are supported by the Pearson VUE test drivers. The upgrade will not only result in enhanced user experience with content authoring, it will also lead to UI being more consistent with content rendering in Pearson VUE test drivers.

The editor is used to author Metadata (Block Text), Comments, Item contents (Stem and responses), References and Cases. Upgrade will be gradual, starting in 1809, first feature to roll out with the upgraded editor will be Metadata (Block Text).

For more details on the supported HTML elements and changes see the Rich Text Editor Upgrade topic.

Ability to save and export alt attribute for Assets

Available from

1812 (approximately December 2018)

Rollout pace

Full rollout - users will have immediate visibility as a result of upgrade

Today ExamDeveloper does not allow users to save the description (alt attribute of <img> tag) for assets. This change allows content authors to save the description for Assets in ExamDeveloper that will eventually be part of the QTI export. This change will help in creating exams that are accessibility friendly.

Ability to convert single quotes into apostrophe in QTI Builder

Available from

1812 (approximately December 2018)

Rollout pace

Full rollout - users will have immediate visibility as a result of upgrade

Content created in MS-Word with an apostrophe (') is 'smart'-converted to a left or right single quote character ( and ). On pasting this content in ExamDeveloper, these characters are carried forward as lsquo (&#8216;) and rsquo (&#8217;). Athena wraps content containing quote characters mid-word making letters after the quote e.g., ’s move to the next line. This change introduces an ability to convert the single quote characters into an apostrophe character while generating QTI. 

Ability to add Multiple Timer warnings on an Exam

Available from

1812 (approximately December 2018)

Rollout pace

Full rollout - users will have immediate visibility as a result of upgrade

Athena supports Multiple timer warnings for a form or section, but ExamDeveloper can only configure 1 at present. This change allows the Duration element in the QTI Builder to allow for more than 1 Trigger Duration and reduces manual work from Test Publishing. Multiple trigger Duration element can be added to both form and section Durations.

Ability to add MinItemsPresented scoring model for Forms and Sections

Available from

1812 (approximately December 2018)

Rollout pace

Full rollout - users will have immediate visibility as a result of upgrade

Athena supports MinItemsPresented scoring model for CAT Exams, which is currently not an option in ExamDeveloper. This change allows users to add MinItemsPresented scoring model for an exam in the QTI Builder, and reduces manual work. MinItemsPresented scoring model can be added to both form and section Durations.

Ability to Search on Manage Item Bank - Add Content - Sections

Available from

1812 (approximately December 2018)

Rollout pace

Full rollout - users will have immediate visibility as a result of upgrade

Add/Remove content feature, available through Manage Item Bank screen, does not allow users to filter sections fulfilling certain criteria thus restricting its use. As a result, we intend to bring search on Section name functionality for Sections similar to Add Sections tab on Create/Edit Exam page.

  • The change makes it possible to search for Sections on Add/Remove content screen.
  • It will not be possible to save a search with certain criteria.

 "Feedback" feature is being removed

Available from

1812 (approximately December 2018)

Rollout pace

Full rollout - users will have immediate visibility as a result of upgrade

Currently ExamDeveloper has "Feedback" link to provide ability to get feedback. We are retiring this feature as it is not widely used.

 

Ability to move Return modal pop-up

Available from

1812 (approximately December 2018)

Rollout pace

Full rollout - users will have immediate visibility as a result of upgrade


Currently when Reviewers and Approvers are rejecting an item, they can not move the modal pop-up in which rejection Comment is entered. This modal covers the item content making it hard to provide the comments. With this work, they will be able to drag and move Reject / Return modal pop-up around.


QTI Builder - Ability to duplicate Sections

Available from

1812 (approximately December 2018)

Rollout pace

Full rollout - users will have immediate visibility as a result of upgrade

 

Currently ExamDeveloper does not allow users to create a duplicate of a Section while creating Exams. With this enhancement, users will be able to create a copy of an existing Section to save time when they want to build multiple Sections with the exact same configuration.

QTI Builder - DT items set as unscored by default

 

Available from

1812 (approximately December 2018)

Rollout pace

Full rollout - users will have immediate visibility as a result of upgrade

 

Currently when any DT item is added to a Section whilst building Exam, it is added as Scored not set to any value. With this change, the default Scored value for DT items will be set to false which can be changed to desired value through Item Control Configuration.

Item check-out

Available from

To be determined

Rollout pace

Gradual rollout - users may have visibility over several releases

Last updated9-November-2018

 

Whenever a user starts editing an item today in ExamDeveloper, that item is automatically ‘checked out’ (or ‘locked’) so that no other users can make modifications.

We will be enhancing this mechanism so that reviewers and project managers can manually check-out an item for a fixed period of time, preventing it from being edited by others (even while they are logged out.)

  • Only one user can check out an item at any point in time; while checked-out, no other user can edit it (but they can still add comments.)

  • When an existing item is opened for modification, it is automatically checked-out until the system checks it in as a result of the user doing one of the following:

    • Saving their changes and are redirected away from the modify page.

    • Leaving the modify page for more than five minutes.

    • Getting logged out through inactivity.

  • On the Modify page, the user is able to see that they hold the check-out for that item.

  • When another user tries to edit a checked-out item, they get an error telling them who holds the check-out.

  • Users on the Review, Validate or Examine questions page receive notifications in near real-time when the item they are viewing is checked in by the other user.

  • A reviewer is able to check-out / check-in an item manually on the Review questions page:

    • This is performed on an item-by-item basis.

    • A reviewer can only check-in items they have checked-out.

    • Enabling/disabling reviewer check-out is configurable per review state in the project configuration.

    • Manual check-outs persist beyond saving the item, leaving the page, or logging out, and can be configured to last for a day, week or month before the system automatically checks them back in (the reviewer will receive an email notification the day before this occurs).

  • A reviewer is also able to see how many other reviewers are viewing the same item as them on the review questions page - updated in near real-time - even if they don’t have the check-out.

  • A project manager is able to check-out / check-in an item manually on the examine questions page:

    • They are not bound to any time limit.

    • They can check-in other users’ items from this page, and do not have to take this step in order to make the item editable again, since the existing pop-up overrides in other areas of the system will be removed.

  • A new page for the project manager to view and check-in another users’ items in bulk may also become available in the future.



  • No labels