...
Field | Type | Default | Required | Note | |||||||
---|---|---|---|---|---|---|---|---|---|---|---|
EventIdeventId | UUID | N | Y | ||||||||
UseruserId | UUID | N | N | ||||||||
ItemitemId | UUID | N | N | ||||||||
Object | Enum<String>String | N | N | enum: Fee/Fine, Item Block, Loan, Manual Block, Notice, Patron Block, Request | |||||||
Action | String | N | N | ||||||||
Date | DateTime | N | N | ||||||||
ServicePointServicePointId | StringUUID | N | N | ||||||||
Source | String | N | N | ||||||||
Description | String | N | N | LinkTo | UUID | N | NNotes | Text | N | N |
DB structure
DB should contain table for each logged object. This will improve performance by reducing the size of the table.
Tables: loans, feesFines, itemBlocks, itemBlockpatronBlocks, patronBlockmanualBlocks, manualBlockrequests, requestnotices
Typical table structure:
id | user | item | action | date | servicePoint | source | description | linkTo | notes |
---|---|---|---|---|---|---|---|---|---|
... | ... | ... | ... | ... | ... | ... | ... | ... | ... |
...