Page History
Status denotes the state of the mapping of a source code (not specifically to the targets).
| Status | Definition | Description |
|---|---|---|
| UNMAPPED | Source code has neither a target or "No map" flag assigned | This is the default status when a map has been created and a target is yet to be assigned. It will also occur when a "No map" flag has been removed. |
| DRAFT | Source code has one or more target codes or a "No map" flag assigned and is in a draft state | The status will automatically change to draft when a map row has been edited. Examples:
|
| MAPPED | Source code has one or more target codes or a "No map" flag assigned and is in a completed map state. | This is a manual status change by an author to denote when the authoring of a mapping of a source code is complete and ready for review (if a review process is being used). When a source code has this status, it can be reviewed if required |
| IN REVIEW | Source code and its mapping(s) is currently being reviewed | This is a manual status change by a reviewer to lock the source code from any changes by an author. |
| ACCEPTED | Source code and its mapping(s) have been accepted by the reviewer and mapping is complete | This is a manual status change by a reviewer to accept the mapping and is now locked for any changes by an author |
| REJECTED | Source code and its mapping(s) have been rejected by the reviewer and needs remapping by an author | This is a manual status change by a reviewer to reject the mapping and should be remapped by an author. |
The statuses used in this tool are split between the two task types, mapping and reviewing.
- Mapping statuses are UNMAPPED, DRAFT and MAPPED.
- Reviewing statuses are IN REVIEW, ACCEPTED and REJECTED.
In a mapping task, a user is able to transition a source code's status between UNMAPPED, DRAFT and MAPPED and where a source code has been rejected by a reviewer, the user can also change REJECTED to DRAFT or MAPPED. If a review process is being used, a status of MAPPED can also be considered the same as "ready for review".
In a review task, a user is able to transition a MAPPED source code to IN REVIEW, ACCEPTED and REJECTED. The IN REVIEW status is designed to be like a lock for the source code so no further changes can be made by the author. A reviewer can choose to bulk change all the status of the valid rows in their task to IN REVIEW if they wish to lock them while they are working.
Overview
Content Tools
Apps