Skip to end of banner
Go to start of banner

Circulation Audit logs

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Circulation Audit logs of all actions filtered by a patron and/or an item with additional filters.


Circulation supports interaction with PubSub. So we can use it for logging of actions. The following approach can be applied:

1) Interceptor generates event for some action and send it to PubSub;

2) Listener handles these events and saves it in storage;

3) Client retrieves logs from Logs Storage.


LogRecord

LogRecord is a main entity for saving/retrieving log info:

FieldTypeDefaultRequiredNote
EventIdUUID
Y
UserUUID
N
ItemUUID
N
ObjectEnum<String>
N
Action

N
DateDateTime
N
ServicePointString
N
Source

N
DescriptionString
N
LinkToUUID
N
NotesText
N


Flow Design





Open questions

  • No labels