Improve history screens

[baszoetekouw]

General

• Change user 'Unknown' to 'Platform' (if that is correct)
• Change user 'Unknown' to 'API' where applicable
• Use most of available screen width to reduce text wrapping in cells
• Make the action texts available as translation in context (e.g., collaboration, user, service, organisation)
• In general, the conext of history action determines what would be interesting details (second table. righthand side) for the user.

User

• Change 'Updated User username' to 'username authenticated' and change 'last accessed date' to 'last authentication'
• Remove 'Updated User tokens last used date'
• Remove actions that the user didn't perfom, like deleting invitations after expiry that were created by the user

  Organisation

• The action of a service becoming (un)available for my organisation's collaborations should be change to 'Service SURFservice (un)available'
  • Replace info about the organisation in that message with info about the service
  • Fix that the 'Show services' filter works on these actions.

    Service

• Add filter 'Show AUP accepted' for accepted AUPs
• Add filter 'Show access rules' for (dis)allowed organisations
• Add filter 'Show user logins'
• The action 'New Service AUPs' should be renamed 'AUP accepted by user'
  • Replace info about the service in that message with info about the collaboration
• The action 'Deleted Service servicename' should be renamed 'Collaboration disconnected'
  • Replace info about the service in that message with info about the collaboration
• Make clear if an organisation was set to 'always' or 'on request' accept connections. Changing between these to shows 'new' and 'delete' with the same values. Perhaps by displaying the connection conditions.
• The action 'New/Deleted Organisation org' should be renamed 'Allowed/Disallowed Organisation org'
  • Only display the organisation name, description and identifier.
• Add action 'User login' for users authenticating to this service

[oharsta]

@FlorisFokkinga The audit logs functionality is very generic and it's main purpose is traceability of data updates. Now that the history is also shown to other users than the platform admins, we might want to reconsider the generic nature of the audit logs. Also because some the requirements are very difficult to implement with the current setup of audit logs.

Also we need to discuss if all requirements need to be backward compatible or may apply to only new audit records. For example: backward compatibility of the requirement "Replace info about the service in that message with info about the collaboration" is very hard to achieve and I doubt it is worth it.