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 47 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


Enhancements to references

Available from

1804  (approximately April 2018)

Rollout pace

Gradual rollout - users will have visibility over approximately 2 - 3 releases

In order to introduce clearer, more granular control over references, we are enhancing the way they are controlled through the project configuration and allowing managers to determine whether the reference belongs to the item, key or distracter. This will result in the following changes:

  • The existing project configuration settings that control if a writer or reviewer can add new references to the project will be improved and moved from the Questions tab to the References tab.

  • A manager will be able to further configure their project to allow users to optionally set references against a specific key or distracter on a question.


Removal of old reports from ExamDeveloper

Available from

1804 (approximately April 2018)

Rollout pace

Gradual rollout - users will have visibility over several releases

In order to ensure reporting is more useful in ExamDeveloper in future, we are looking to streamline the ‘additional reports’ available to Managers. A number of these were created to serve a specific purpose many years ago and either perform poorly or are not believed to be used by anyone anymore. The following reports are planned for removal from the Manage -> Reports -> Additional Reports tab in the application:

  • Blueprint Distribution Exam

  • Exam Answer Key*

  • Exam Default Statistics*

  • Exam Item Statistics

  • Form level Item Statistics*

  • Item Counts By Blueprint

  • Item Statistics Report

  • No of Graphics*

  • Outline Items

  • Pearson Exam Question Details

  • User Activity*

  • Validation Data Report

* Data will be included in the Custom Report

Please note that if you are using these reports, please reach out to examdeveloper@pearson.com in the first instance, so that we can set up some time to understand your needs and explore how we might best serve them.


Case publish retirement

Available from

1804 (approximately April 2018)

Rollout pace

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

Publishing in ExamDeveloper today to ‘lock-in’ revisions of question content takes several steps. In order to publish an exam, a user must ensure that:

  • Questions and assets are in a Completed state.

  • Cases are published.

  • Sections are published.

This is difficult and time consuming to manage for those who have a mixture of different objects on their exam, and so we intend to begin streamlining the publishing process in ExamDeveloper, by removing the ability to publish a case:

  • The ability to see the case status (draft or published) will be removed.

  • It will no longer be possible to publish or unpublish a case, and the publish case permission will be retired.

  • It will no longer be necessary to publish a case in order to publish a section or exam.

  • All existing published cases will be automatically unpublished when ExamDeveloper is upgraded:

    • This will make those cases, and questions on those cases, editable by Writers.

    • Existing sections and exams that are published will continue to have the case content ‘locked-in’.

    • Existing sections and exams that are not published will use the latest case content.


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

Available from

1804 (approximately April 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 to filter questions fulfilling certain criteria, restricting its use. As a result, we intend to bring search functionality for Questions like it exists for Cases.

  • The change will make it possible to search for Questions on Add/Remove content screen.

  • It will not be possible to save a search with certain criteria


Ability to view users with active Work assignments during delete operation

Available from

1804 (approximately April 2018)

Rollout pace

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

Delete work assignments feature available through Assign Questions → Load Search screen, does not allow to delete a saved search with multiple work assignments, which is correct. It also does not display the users with multiple work assignments, leading to more time expense in finding users having that assignment.

  • The change will make it possible to view users with multiple work for the search which user is trying to delete on the Load Search screen.


Display Saved search name instead of query string for Work assignments

Available from

1804 (approximately April 2018)

Rollout pace

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

For work assignments current method displays a query string as Criteria instead of the saved search name, which can be confusing for the users. To make the information on screen more meaningful:

  • The change will display Saved search name instead of the query string.

  • This change will be applicable to all places where assignment criteria is displayed in the application.

  • For 'auto-assigned', write assignments and write/review/validate assignments, saved search name will follow the format - "Blueprint: <ID> <Name>; <MetadataName>: <Comma separated list of values>"


Get All Assets report will get queued like Custom reports

Available from

1804 (approximately April 2018)

Rollout pace

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

Current Get All Assets report for project managers starts downloading directly without queuing up. In order to bring consistency and enhanced user experience, Get All Assets report will get queued like Custom Report.

  • The change will not impact the way Get All Assets report is generated or delivered.

  • Apart from getting queued all other elements of Get All Assets report will remain as is.


Removal of ability to edit statistics on the statistics tab, when viewing a question

Available from

1805 or 1806 (approximately May or June 2018)

Rollout pace

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

From feedback we have received from statisticians/psychometricians, the current ability to import and export statistics in ExamDeveloper is the preferred process for statistics management, and they’d like to ensure that other users do not have the ability to alter statistics when viewing a question.

As a result of this feedback, whenever a user views a question in ExamDeveloper (such as on the Examine, Observe and Review Question pages, etc.) and they navigate to the statistics tab, they will continue to be able to select an analysis group / set to be able to view statistics, however, it will no longer be possible to edit the statistics / default flag on these pages.


Calculator on an individual item

Available from

1808 (approximately August 2018)

Rollout pace

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

The current functionality to add a calculator today is to add the calculator to a Section or Sections in the QTI Builder. Authors will now have the ability to set the calculator on an individual item in the Advanced Properties. Visibility, Editability, and Calculator defaults can be set in the project configuration page. In the QTI Builder, users will have the ability to set a Calculator at the Assessment level that can be referenced from each of the items along with any of the Sections. Current calculator features will remain functional.


Changes to cases

Available from

To be determined

Rollout pace

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

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, and it will be possible to sequence the tab display order alongside split screen exhibits that don’t belong to the case, for that question.

  • When a case is deleted, the case exhibit will remain attached to the case questions in the project (as a split screen exhibit), but the ‘grouping’ of questions will no longer exist.

  • 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 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, On Exam, 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.

  • 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; users should be aware that this will only work if all questions on the case are included in the import.


Improvements to the way revision numbers are incremented

Available from

To be determined

Rollout pace

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

In order to ensure we can support larger item bank in the application, we are changing the way revisions are stored behind-the-scenes. As part of this change, we have an opportunity to change the way that question revision numbers are incremented, as they are currently randomly set by the application whenever a new question revision is created.

We will be moving to a more user-friendly system, which increments the question revision number by one each time a new revision is created, rather than assigning a random number.

  • New questions will have a logical revision number that indicates the iteration of the question, starting at one and increasing by one each time a new revision is created.

  • Existing questions will no longer get a random revision number, but will start to increment by one each time a new revision is created (e.g., if the latest revision number of a question is 133905, the next revision number will be 133906, then 133907, etc. after this change.)

  • Existing revision numbers will not be altered.


Improvements to question history and user tracking

Available from

To be determined

Rollout pace

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

In order to ensure we can support larger item bank in the application, we are changing the way revisions are stored behind-the-scenes. As part of this change, we have an opportunity to improve the way that we display question user tracking and history tabs to end users.

Changes to the question history tab:

  • When nothing is changed about a question and a user submits, a new revision will not be created (i.e. the system will no longer create duplicate revisions.)

  • State changes will always cause a new revision of the question to be created, so that a history of state/workflow history changes can be tracked.

  • A new grid will be implemented, which displays:

    • the revision number.

    • the state of the question for the revision displayed.

    • the user who created the revision (i.e., the user who wrote/modified the question.)

    • the time the revision was created (i.e., the time the user wrote/modified the question.)

  • It will be possible to select a single question revision and view it without comparing changes against the previous revision.

  • Users will be able to compare changes between any two revisions (e.g. revision 2 vs. 5.)

Changes to the user tracking tab:

  • Written by and Modified by will be removed, as they are now available on the history tab for every revision that is created.

  • The Reviewed by/Accepted by/Rejected by labels will be merged into a single layout that more clearly outlines the workflow history of the question.


Improvements to question batch edit processing

Available from

To be determined

Rollout pace

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

The batch edit page is a powerful page for applying updates to many questions en-masse, but when one of those question fails to update, all questions fail and all changes are rolled back unnecessarily. We have taken steps to ensure that a batch edit processes changes where it can and gives users greater feedback about what and why certain questions couldn’t be updated, so they can focus on correcting the remainder left over, rather than having to sort through the entire batch.

Changes to the question batch edit screen in ExamDeveloper:

  • Only one change can be made for each batch edit that is run (i.e., I can change blueprint or stem text in separate batch edits, but not in the same batch edit), with the option of adding a comment that describes the change being made.

The following changes impact the way question batch edits are processed:

  • If changing a question does not cause an error, it will be processed and updated.

  • If changing a question does cause an error, it will be skipped and the process will continue with the next question in the batch (instead of causing the entire process to fail.)

  • At the end of the batch edit, if any questions failed, an Excel report will be automatically downloaded that details the questions that failed to update, giving reasons why the update failed.



 

  • No labels