Topic | Open Questions and User Story Suggestions - need to determine priority, preferred behavior, and in/out for v1 | Consensus |
---|
Roles and Permissions | - User with appropriate permissions can provide None or Read access to the Audit Trail
or - User with Delete access to any Procedure or Authority term may view the Audit Trail for that record type
or - User with Delete access to any Procedure or Authority and Read access to Audit Trail may view the Audit Trail for that record type
or - User with Write access to any Procedure or Authority term may view the Audit Trail for that record
or - User with Write access to any Procedure or Authority and Read access to Audit Trail may view the Audit Trail for that record type
or |
|
Performance | User will not experience a decline in system performance due to the implementation of Audit Trail functionality |
|
Relationships | - User may view or create a report of all changes to the Relationships for a given Object
- User may view or create a report of all changes to Relationship-specific data for a given Object
- Future need - i.e. if a user notes on an Exhibition record that a specific Object needs a mount, that change is noted on both the Exhibition and Object record Audit Trails
|
|
Authority Terms | How will a user view Audit Trail for Authority term records, which have no tabs |
|
Repeatable Fields | How will changes to repeatable/multi-valued fields be logged? - Value added
- Value changes
- Value deleted
- Order changed (e.g. value changed to primary) - how to log re-arranging the order beyond primary/not primary? Necessary?
|
|
Media Handling | - User can view the Audit Trail for a blob within a Media Handling record, including:
- Blob added to MH record
- Blob removed from MH record
- Blob removed and replaced with new in MH record
|
|