View coding history
The application keeps an audit history of the coding changes that users make to field values for documents for the following features: Binders, Issues, Productions (unlocked only), Populations and Samples, Annotations, as well as field values that are updated by import jobs for existing document records. For additional information, see Overview of what is audited using the Coding History feature.
For information about how to download a coding history report on the Tools menu, see Download a coding history report. For information about how to download the coding history in the Coding History pane, see Download coding history.
User audit logging for coding decisions is also known as coding history.
Note: Your administrator must enable the Coding History feature, and you must have access to the features for which you want to view audit information. You can then view the coding history for selected documents in a Coding History pane in your workspace. Administrators can see all history records, including records for deleted objects, in the template views in the Coding History pane, regardless of their group membership and the group security settings for objects such as binders, fields, or productions.
The Coding History pane includes the following information for actions to documents:
Field: The feature type, for example, Annotation, Binder, Population, Production (unlocked only), Issue, or Sample.
Value: The name of the item that was added.
Previous value: The previous name of the item that was modified.
Tip: On the Search page, you can use the previous value ever was operator to perform a coding history search for the following fields: Pick list, Date, Number, Yes/no, Text, Binder - Shared, Issue, Production, Population, Sample, Highlight, Redaction, People - correspondence type, Organizations - correspondence type. Memo field types are not supported.
Action: Whether the item was added, updated, deleted, or converted.
Mass coded: The mass coded icon indicates if it was a mass action to multiple documents at once.
Date: The date and time of the action.
User: The user name of the user who performed the action.
The following information appears in the Coding History pane for connection changes to data model entity items:
Field: The entity name.
Value: The ID of the entity item is is connected to.
Previous value: The ID of the entity item that was disconnected.
Action: Linked or unlinked.
Date: The date and time of the action.
User: The user name of the user who performed the action.
Linked: Appears in the Action column when an entity item is connected.
Unlinked: Appears in the Action column when an entity item is disconnected.
For entities, the following icons appear in the Coding History pane:
Linked: Appears in the Action column when an entity item is connected.
Unlinked: Appears in the Action column when an entity item is disconnected.
View coding history for selected documents
To view coding history:
Add a Coding History pane to your workspace. Or, use one of the following methods to open the Coding History pane in a standalone window:
On the Options menu in the List pane, click Open coding history.
In the Conditional Coding pane, click the Coding history button.
Note: If none of the selected documents are coded, you see the message No coding history. If coding history is not enabled for the case, you see the message Audit history is not configured for this case.
In the Coding History pane, you can do the following:
To see a list of all coding changes, click the History ungrouped button. You can sort and filter the columns in this list.
To see a list of coding changes grouped by field name, click the History grouped by coding field button. You can sort and filter the columns in this list.
Code documents with coding history enabled
If the Coding History pane is open in the workspace, and you edit any coding fields, then the coding history updates to reflect the newly saved coding changes.
If the Coding History is open as standalone for a document, and you edit any coding fields for that document, then the coding history updates to reflect the newly saved coding changes.
Overview of what is audited using the Coding History feature
The application audits the following actions:
For documents:
Coding of fields and other items in the Code and Conditional Coding panes, as well as inline edits in the List pane, as follows:
Pick list (field)
Date (field)
Number (field)
Yes/no (field)
Text (field)
Memo (field)
Binder - Shared
Binder - Private
Issue
Production
Creation or deletion of populations and samples, as well as removal of documents from a population or sample.
Application of annotations (highlights or redactions) in the Image viewer in the View pane.
Document downloads in the View pane
For data models:
The application audits entity connections that are linked or unlinked.
To download coding history:
In the Coding History pane, click the Download history button to download the data a spreadsheet (.csv file).