Documents editing, tracking of changes, and workflows.

Information about Editing and Tracking Change

The mapping tool supports a variety of actions to edit map records, add notes, assign advice, etc.  All of the "map objects" (see Domain Model) are audited, meaning all changes to these objects are recorded with each commit.  Thus assignment of a new code, movement through the worfklow, addition of advice, and any other changes are recorded.  All prior states of map records can be searched and retrieved as needed.

Tracking Changes

There is no log of changes, per se, but each prior state of a map object can be viewed and read.  In the "mapped concept view" in the application, the prior history of a map record is shown, with the last state of each map record for a particular concept (within the focus project) being displayed.  Currently, there is no interface for seeing all of the incremental changes to a map record, though something like that would be fairly straightforward (but probably too fine-grained to be useful).

If editing causes any undesirable changes, admin tools can be developed to recover any prior state of a map record. 

Note, prior states of objects not audited cannot be recovered.  This is most important when considering changes in terminology content due to loading new versions, processing deltas (e.g. "drip feed") and tree position recomputation.  This is intentional to improve performance and limit the number of archived states.  Terminology objects include version information so auditing a change in version would cause an entire copy of the terminology to be recorded in the audit trails - this is the main reason they are not audited.

Origin ids

Map records undergo a complex workflow in which individual specialists edit their own copies of the record and submit them for comparison.  When conflicts are detected, new records owned by the corresponding lead are created and at that time, all current states for all the records are available for review by the lead.  A mechanism is used to connect the specialists' records to the lead record, called "origin ids".  When a record is created from another record (or collection of records), the origin ids of that record and that record's id itself are added as origin ids of the later record. What this means is that for any workflow, records retain information about the prior records that were used ultimately to generate them.   Thus the chain of "provenance" is recorded and can be searched.

At the moment, there are no services to query or use origin ids in sophisticated ways, however the tracking of what records lead to what other records is faithfully preserved and can be reported on.  Consider the following chain of events

Workflow Concepts

Following are the standard "workflow paths" that a record can follow while it is being edited. 

Workflow Tracking Record

This domain object represents the complete known state of the workflow, including information about:

Workflow Actions 

The workflow model is built around actions that affect the various workflows in a variety of ways.

Workflow Paths

The mapping tool supports a number of different workflows that have different actions and state transition diagrams.  The currently supported (and planned) workflows include:

Workflow Status

Some workflow status values are reused by different paths and some are specific to certain workflow paths.

Workflow Path Documentation

The supported workflow paths are described in detail at the following links:

The following workflow paths are not yet supported