Usage Omeka Classic plugin

Exporting the Log

The log downloads as CSV or JSON, for everyone who may view it.

Exporting

  1. Open Audit Trail in the admin menu.
  2. Optionally set filters (action, actor, resource type, dates). See Viewing the Activity Log.
  3. Click Export CSV or Export JSON at the top of the page.

The file downloads at once and holds every entry matching the filters, newest first, not only the page on screen. Batches are always exported event by event. The file is named after the moment of the export, for example audit-trail-20261027-143005.csv.

There is no row limit: the file is written as it is read, a thousand entries at a time, so even a large log exports without running out of memory. Narrow the export with the date filters if you only need part of it.

Each export is itself logged (audit_trail.export, with the format, the number of entries and the filters).

File contents

Both formats have the same fifteen fields per entry:

id, timestamp, actor_id, actor_display, action, resource_type, resource_id,
resource_label, resource_url, detail, source, batch_id, ip_address, user_agent, extra
  • timestamp is in UTC, as ISO 8601: 2026-10-27T14:30:05Z.
  • resource_url is the full address of the record's admin page, or empty.
  • source is web, api, job or cli.
  • extra holds the entry's data.

The CSV has a header row and starts with a UTF-8 byte order mark, so spreadsheet programs read accents correctly; extra is the JSON text. The JSON file is an array of objects, one per entry, with extra as a nested object.

Export addresses

The buttons open /admin/audit-trail/export with the filters and a format of csv or json:

/admin/audit-trail/export?format=json&resource_type=item&date_from=2026-10-01

You can open these addresses directly while signed in with a role that may view the log. The export does not accept REST API keys.

Log in for Support