Overview
Describes the Non-Legacy Workflow Path, by which a concept is mapped independently by two specialists, with conflicts arising resolved by the lead.
Details
For general details on workflow, see Editing, Tracking, Workflow.
Workflow Diagram
(Click to enlarge.)
INITIAL STATE:
- A tracking record for the concept to be mapped has been created by Compute Workflow.
- No map records exist for this concept and project.
FINAL STATE:
- No tracking record exists for this concept and project.
- A single map record marked READY_FOR_PUBLICATION exists.
Workflow Status Combinations and Action Enumeration
The table below describes the stagess that exist and actions that can be taken for each stage of the workflow. The columns are:.
- Workflow Status Combination: The combinations of map records that exist for a given concept and project. Each combination is listed on a new line. Where multiple records exist for a single combination, they are linked with a plus sign (+), e.g. EDITING_DONE + EDITING_IN_PROGRESS. The current user's record (if any) is marked in bold.
- Action: Each row represents a permitted workflow action that can be performed on a particular workflow status combination.
- Result: Describes actions performed on specific map records as a result of the action.
- Trigger: The user's action in the Mapping Tool user interface resulting in a request to perform an action.
Workflow Status Combination | Action | Result | Trigger |
---|---|---|---|
Specialist Level Work: User's record marked in bold | |||
[NO RECORDS – INITIAL STATE ] | ASSIGN_FROM_SCRATCH | Record created with NEW status. | User clicks Assign Concept on Available Work widget |
NEW | SAVE_FOR_LATER | Specialist's record saved without validation and set to EDITING_IN_PROGRESS. | Specialist clicks Save For Later on Map Record editing page. |
FINISH_EDITING | Specialist's record validated. If validation successful, specialist's record saved and marked EDITING_DONE. | Specialist clicks Finish from Map Record editing page. | |
UNASSIGN | Specialist's record deleted. | Specialist clicks Unassign on Assigned Work widget. | |
EDITING_IN_PROGRESS | SAVE_FOR_LATER | Specialist's record saved without validation. No workflow modification. | Specialist clicks Save For Later on Map Record editing page. |
FINISH_EDITING | Specialist's record validated. If validation successful, specialist's record saved and marked EDITING_DONE. | Specialist clicks Finish from either:
| |
UNASSIGN | Specialist's record deleted. | Specialist clicks Unassign on Assigned Work widget. | |
EDITING_DONE | SAVE_FOR_LATER | Specialist's record saved without validation. No workflow modification. | Specialist clicks Save For Later on Map Record editing page. |
FINISH_EDITING | Specialist's record validated. If validation successful, specialist's record saved. No workflow modification. | Specialist clicks Finish from Map Record editing page. | |
UNASSIGN | Specialist's record deleted. | Specialist clicks Unassign on Assigned Work widget. | |
NEW + NEW | SAVE_FOR_LATER | Specialist's record saved without validation and set to EDITING_IN_PROGRESS. | Specialist clicks Save For Later on Map Record editing page. |
FINISH_EDITING | Specialist's record validated. If record valid:
| Specialist clicks Finish from Map Record editing page.
| |
UNASSIGN | Specialist's record deleted. | Specialist clicks Unassign on Assigned Work widget. | |
EDITING_IN_PROGRESS + NEW | SAVE_FOR_LATER | Specialist's record saved without validation. No workflow change. | Specialist clicks Save For Later on Map Record editing page. |
FINISH_EDITING | Specialist's record validated. If record valid:
| Specialist clicks Finish from either:
| |
UNASSIGN | Specialist's record deleted. | Specialist clicks Unassign on Assigned Work widget | |
EDITING_DONE + NEW | SAVE_FOR_LATER | Specialist's record saved without validation. No workflow change. | Specialist clicks Save For Later on Map Record editing page |
FINISH_EDITING | Specialist's record validated. If validation successful, record saved. | Specialist clicks Finish from Map Record editing page. | |
UNASSIGN | Specialist's record deleted. | User clicks Unassign on Assigned Work widget | |
CONFLICT_DETECTED + CONFLICT_DETECTED
| SAVE_FOR_LATER | Specialist's record saved without validation. No workflow change. | User clicks Save for Later on Map Record editing page. |
FINISH_EDITING | Specialist's record validated. If validation successful, compare this
| User clicks Finish on Map Record editing page. | |
UNASSIGN | Specialist's record deleted. | Specialist clicks Unassign on Assigned Work widget | |
ASSIGN_FROM_SCRATCH | Record created with CONFLICT_NEW status | Lead clicks Assign Conflict from Available Work widget. | |
Lead Level Work: User's record is marked in bold | |||
CONFLICT_DETECTED | SAVE_FOR_LATER | Lead's record saved without validation and marked CONFLICT_IN_PROGRESS. | Lead clicks Save for Later on Compare Records editing page. |
FINISH_EDITING | Lead's record validated. If validation successful, lead's record | Lead clicks Finish from Compare Records editing page. | |
UNASSIGN | Lead's record deleted. | Lead clicks Unassign on Assigned Work widget. | |
CONFLICT_DETECTED | SAVE_FOR_LATER | Lead's record saved without validation. No workflow change. | Lead clicks Save for Later on Compare Records editing page. |
FINISH_EDITING | Lead's record validated. If validation successful, lead's record saved and marked CONFLICT_RESOLVED | Lead clicks Finish from either:
| |
UNASSIGN | Lead's record deleted | Lead clicks Unassign on Assigned Work widget. | |
CONFLICT_DETECTED | SAVE_FOR_LATER | Lead's record saved without validation. No workflow change. | Lead clicks Save for Later on Compare Records editing page. |
FINISH_EDITING | Lead's record validated. If validation successful, lead's record saved and marked CONFLICT_RESOLVED | Lead clicks Finish from Compare Records editing page. | |
PUBLISH | Lead's record set to READY_FOR_PUBLICATION. LEADS TO FINAL STATE. | Lead clicks Publish from Assigned Work widget. | |
UNASSIGN | Lead's record deleted. | Lead clicks Unassign on Assigned Work widget. |
Description of workflow combinations
This section describes each possible combination of workflow statuses attached to a tracking record for a concept and project.
Status 1 | Status 2 | Status 3 | Explanation |
---|---|---|---|
NEW | One specialist has claimed the concept, but has not begun editing | ||
EDITING_IN_PROGRESS | One specialist has begun editing, and has saved work. | ||
EDITING_DONE | One specialist has completed editing. | ||
NEW | NEW | Two specialists have claimed the concept, but neither have begun editing. | |
NEW | EDITING_IN_PROGRESS | Two specialists have claimed the concept. The first has not begun editing; the second has saved editing work. | |
NEW | EDITING_DONE | Two specialists have claimed the concept. The first has not begun editing; the second has completed editing. | |
EDITING_IN_PROGRESS | EDITING_IN_PROGRESS | Two specialists are both still editing records. | |
EDITING_IN_PROGRESS | EDITING_DONE | One specialist has finished editing the record and the other is still editing. | |
EDITING_DONE | EDITING_DONE | Exists only temporarily until conflict analysis occurs, at which point either a conflict is detected and the status changes, or a conflict is not detected and these records are removed. | |
CONFLICT_DETECTED | CONFLICT_DETECTED | Two specialists have completed work, and mappings are in conflict. Requires lead review. | |
CONFLICT_DETECTED | CONFLICT_DETECTED | CONFLICT_NEW | A lead has claimed a conflict for review, but has not begun editing. |
CONFLICT_DETECTED | CONFLICT_DETECTED | CONFLICT_IN_PROGRESS | A lead has begun resolving a conflict, and has saved work. |
CONFLICT_DETECTED | CONFLICT_DETECTED | CONFLICT_RESOLVED | A lead has finished reviewing a conflict. |
Links/References