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


Search label migration and retirement

 

Available from

1801 (approximately Jan 2018)

Rollout pace

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

 

The search label feature is incomplete functionality in ExamDeveloper: it is only possible to create via the batch edit screen, but is not visible on questions. Using collections overcome these drawbacks and so we will be migrating search labels over to collections and retiring search label functionality.
  • If you are using the search labels feature, in future you should use collections instead.

  • Existing search labels will be converted to collections and the default project manager will be the owner of that collection (e.g. if I have a search label named ‘Review Feb 2017’, then after the change there will be a collection with the name “Search label: Review Feb 2017” containing the same questions that had the search label.


“Move Content To” link retirement

 

Available from

1801 (approximately Jan 2018)

Rollout pace

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

 

The ‘Move Content To’ link on the manage blueprint screen is incomplete functionality in ExamDeveloper: this functionality does not create an audit trail in the question revision history when used today. Using the batch edit feature does not have this drawback, and is the recommended alternative for users. We will therefore be removing this link from the manage blueprint screen.

  • If you are using the ‘Move Content To’ link in the Manage -> Blueprints area, use batch edit to search for questions in a blueprint area and move the content to a new blueprint area here instead.


Treating case lead-in text as a question

 

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 question, 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 define and separate the individual components that make up a case, so that we can deliver some additional case enhancements in future. The first of these changes will be to separate the lead-in text from the case, so that it is treated as a display-only question type that is attached to a case (as other question types are today).

  • New and existing case lead-in text will be treated as a display-type question with its own history and Question ID (and ability to set metadata, enemies, blueprints, etc.).

  • It will remain attached to the case, editable via the same windows, and deliverable to candidates in the same way.

  • Case enemies will be removed and migrated to the display-type exhibit question that gets created during the migration. Exams will continue to check for exhibit enemies when saving.


Changes 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 refactoring the way revisions are stored in the database. 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.

  • 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)

  • 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 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:


  • State changes will always cause a new revision of the question to be created, so that a history of state 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.

  • Project Managers viewing a single historical question revision will be able to choose to ‘revert’ some question data to an earlier point in the question’s history.

  • 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 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 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 errors, 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 and rollback changes)

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

 

 

  • No labels