All Versions
DSpace Documentation
| Table of Contents | ||||
|---|---|---|---|---|
|
The Audit feature in DSpace offers a structured way to capture and review significant events across DSpace objects. It tracks changes to content, metadata, and other key operations, allowing administrators to:
...
returns the full details of a specific event.
...
Export example:
./dspace solr-core-management --mode export --core audit --directory /tmp/export --format csv --threads 4 --increment WEEK |
|---|
Import example:
./dspace solr-core-management --mode import --core audit --directory /tmp/export --format csv --threads 2 |
|---|
...
| please check the dedicated Solr Data Management page./dspace solr-core-management -m <mode:{export|import}> -c <core:{audit|statistics|...}> -d <directory> [-f <format:{csv|json}>] [-t <threads:integer>=1] [-s <start-date:yyyy-MM-dd>] [-e <end-date:yyyy-MM-dd>] [-i <increment:{WEEK|MONTH|YEAR}>] [-h] |
|---|
By default, when auditing is enabled, audit event logs are also written to configurable log files. This is managed through the log4j2.xml configuration file. The logging level for audit events can be set using the following property:
<Property name='loglevel.audit.events'>ALL</Property> |
|---|
ALL can be used to track all the Audit details
OFF can be used to turn off the Audit Log trace
...