You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For many events, we capture an audit for the two different participants.
So, when an item is loaned to user, we record an event for the item and another for the user. This means we can start with the user and view the history of what they have borrowed, or look at the item for a history of who has borrowed it.
For many of these events, we do store the id of the other participant, to make it clickable from a history page.
But instead, we could take the approach of just the single entry, and in the History page for a object, show events whether it's the subject or the object of the transaction.
Do some analysis to double-check if we can do this for all events. It would be consistent to always have the item first and the other resource second, though this can't always be the case since we store some non-item related events (login, add user, create dispatch, etc, etc).
The text was updated successfully, but these errors were encountered:
For many events, we capture an audit for the two different participants.
So, when an item is loaned to user, we record an event for the item and another for the user. This means we can start with the user and view the history of what they have borrowed, or look at the item for a history of who has borrowed it.
For many of these events, we do store the id of the
other
participant, to make it clickable from a history page.But instead, we could take the approach of just the single entry, and in the
History
page for a object, show events whether it's the subject or the object of the transaction.Do some analysis to double-check if we can do this for all events. It would be consistent to always have the item first and the other resource second, though this can't always be the case since we store some non-item related events (login, add user, create dispatch, etc, etc).
The text was updated successfully, but these errors were encountered: