-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Audit feature #35
Comments
The audit log would be stored in the database. As the audit's fields are likely to evolve, the logs should take the form of a JSON. It would be an array of 3-fields objects:
The audit scan would be runnable as a task (from /tasks/run-audit) The audit log should be accessible from a dedicated controller. The most recent audit should be accessible with /audit. It would be the raw JSON. Each section would be accessible with /audit/key-of-section. The audit's history should also be accessible, through /audit/history |
As libraries get bigger over time, many files are added,
But we might forget to set some metadata to them.
In order to keep a library as clean as possible, an audit feature would be nice.
It would parse the database, and raise any missing data and/or empty fields like a genre, a release date, an unspecified disc index, etc.
The text was updated successfully, but these errors were encountered: