Settings live under Admin > Modules, on the Configure button for ResourceVersioning (/admin/module/configure?id=ResourceVersioning). The Settings button at the top of the Resource Versions page opens the same form.
Settings
| Setting | Default | Description |
|---|---|---|
| Enable version capture | On | When off, no new versions are recorded. Existing history is kept and can still be browsed, compared, and restored. |
| Resource types to version | Items, Media, Item sets | Only the checked types are captured. Unchecking a type stops new snapshots for it; existing versions remain. |
| Maximum versions per resource | 50 | After each capture, the oldest versions beyond this count are deleted for that resource. 0 keeps every version. |
| Retention period (days) | 0 | Versions older than this many days are deleted by the prune job. 0 keeps versions forever and makes the prune job a no-op. |
| Capture versions during batch operations | On | When off, saves flagged as partial updates are not captured. Omeka's admin Bulk Edit and batchUpdate API calls run as partial updates, as do partial (PATCH) updates through the REST API. Turn this off temporarily during very large imports to avoid writing thousands of snapshots. |
| Restore resource owner | Off | When on, restoring a version also restores the owner recorded in the snapshot. When off, the current owner is kept. |
Settings are stored as global settings with the prefix resource_versioning_ (for example resource_versioning_max_versions).
The per-resource cap is enforced immediately after every capture. The retention period is only enforced when the prune job runs; see Retention and Pruning.
Permissions
Access is controlled by the user's Omeka S role. The Version History tab is rendered on the show page for anyone who can view the resource, but following its links requires the roles below.
| Role | View history, diffs, and batch details | Restore a single version | Batch rollback | Prune | Settings |
|---|---|---|---|---|---|
| Researcher | - | - | - | - | - |
| Author | - | - | - | - | - |
| Reviewer | Yes | - | - | - | - |
| Editor | Yes | Yes | - | - | - |
| Site Admin | Yes | Yes | Yes | - | - |
| Global Admin | Yes | Yes | Yes | Yes | Yes |
Restore and rollback buttons are hidden from users who lack the corresponding privilege. Settings follow Omeka's standard rule that only global administrators can configure modules.
Site settings
The module has no per-site settings. Capture and history are global.