Resource Audit Fields - MVP

[JodiNA]

For the February, 2024 virtual sprint, one of our volunteer roles will be conducting an audit of our existing resources to make sure that the URLs still work. In order to do this, we need to have a mechanism to track who audited the resource and when. This will allow us to ensure that all resources are getting audited on a regular basis. Additional needs include tracking what, if any, issues were found or changes made, or changes that need to be made in the future (ex: auditor could note that the URL was updated and also note to SCR team that the resource description needs updating too).

Requirements:

• Resource field: Audited By (user lookup)
• Resource field: Audited Date (date field)
• Track changes to the above fields
• Interface (likely a screen flow) for auditors to record their check and write notes

Questions:

• Should auditors use the "curator notes" field for recording notes about what they found during the audit or should this be a separate field (or separate object?!)
• How granular do we want to get with tracking what was changed/updated in audit? Is it important to know what was changed or just that it was reviewed?
• What happens if a url no longer works? Do we change the status to denied? New status? Does the submitter need to get notified, and, if so do we give them an option to send an updated link? Needs an MVP approach to this for now.

[janawalke]

Resource field: Audited By added Resource field: Audited Date added Tracking for these fields added.