.. include:: /includes.rst.txt

.. comments - headings

   # with overline, for parts
   * with overline, for chapters
   = for sections
   - for subsections
   ^ for subsubsections
   " for paragraphs
   * for H5
   + for H6

.. index:: pair: Asset Collection; Change History

.. _controlling_change_history_target:

Controlling Change History
--------------------------

Record Triple Counts only
^^^^^^^^^^^^^^^^^^^^^^^^^

**Record Triple Counts only** is available under the *Manage* tab.
It disables recording change history at the level of individual triples for production copies.
When activated, EDG only records summary counts of changed triples – added or deleted.
This significantly reduces storage and memory impacts at the cost of losing detailed change information and the ability to undo (revert) the changes.

Working copies and existing change history are not affected by this setting.

Archive Working Copies(Workflows) on Commit
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

**Archive Working Copies on Commit** is available under the *Manage* tab.
When true, working copies are archived automatically when a workflow is committed.

.. note:: The archive always contains the full history, regardless of the *Record Triple Counts only* setting.

Changes made in the archived working copies will not show up in the Change History after commit.
Archived workflows continue to be listed in the Completed Workflows table on the *Workflow* tab.

The archives are stored in a special “archive” folder on the server.
System Administrators can move or permanently delete the archived data so that it isn’t using up storage space when not needed.



Clear Change History
^^^^^^^^^^^^^^^^^^^^

**Clear Change History** is available under the *Manage* tab.
It removes the audit trail from the collection, meaning users can no longer revert a change using the editor form.

Over time, the change history about a collection can become very large adding to the workspace/database causing more memory to be used by EDG.
In order to improve performance, users may want to periodically clear change history if it is not being used.

.. Note:: This operation is not reversible. To recover cleared content, use backups.