Maintain provenance log

[fpici]

Application will maintain a "provenance log" that records every action performed on a stored document, including initial deposit, editing, approval, deletion, publication, submission to ProQuest, and any embargo events. This log will include the date and time, which user performed the action, whether the action was successful, and which documents were affected.

Logs are in standardized Logger format
Logs are date stamped and automatically rotated
Logs are backed up automatically
Logs should be visible in the UI by superusers
Required fields are present:
Date and time stamp
user
document id
what action was performed
whether the action was successful
Logged actions are also logged to the object in question
Logs must be retained for a minimum of 60 days

[fpici]

Also in Laevigata Tix # 238.

[rotated8]

curationexperts/laevigata#238

[amiles4]

@fipici says: the following are some important information to capture

• status
• when submitted
• approved
• embargos (set, changed, etc.)
• publishing
• confirmation of graduation
• sent to proquest

@rosy1280 wonders: if we expose the Fedora audit trail would some of this information be captured?

[rosy1280]

fedora audit trail may not be on by default. this was taken off the table early on because of the cost.

[fpici]

Here is a screenshot of the current audit trail in Legacy ETDs. It is a Laney dissertation record log:

[rosy1280]

A Mellon grant is being submitted by UCSD that may scope out this work for Hyrax. Emory has been named a partner on the grant.

[fpici]

@rosy1280 This is great news Rosalyn. Thank you!!