Loans (UXPROD-788)

[UXPROD-2133] Create an Action Log to capture Accurate Loan Edits -- for reporting purposes Created: 17/Oct/19  Updated: 07/Dec/21

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Loans

Type: New Feature Priority: TBD
Reporter: Cheryl Malmborg Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: reporting, round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to REP-103 Collections use - physical (internal)... Closed
Epic Link: Loans
Development Team: None
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R4
Rank: Grand Valley (Full Sum 2021): R3
Rank: Lehigh (MVP Summer 2020): R2
Rank: U of AL (MVP Oct 2020): R4

 Description   

Record significant actions against loans by loan id – checkout,renewal,request,alter due date,checkin for use in statistical reports.

Resource Access collection Use reports require tracking action taken on loans over specified date ranges.

The reports provide counts of loans and renewals grouped variously by patron group, item owning location, loan type and service point of the loan.

Currently the data available is:

mod-circulation-storage/loan-storage:

id - unique to a loan links to mod-circulation-storage/audit_log
userID - of the patron (may be null for closed loans)
patronGroupIDAtCheckout (patron group may change over the course of a loan)
itemID - link to mod-inventory-storage/item(permanentloantypeid,temporaryloantypeid,materialtypeid,permanentlocationid)
loanPolicyID - effectively the type of loan although it may apply to multiple loan types
itemEffectiveLocationAtCheckout
loanDate

mod-circulation-storage/audit_log contains a snapshot of the loan record taken every time the loan is touched
The snapshot is recorded whether or not the state of the loan changes. This makes it difficult to extract actions against such as
renewals from the log. Recording only actions that change the state of a loan would greatly simplify reporting.

Developers need to know:
-which loan actions are relevant
-when the loan actions occur
-what information is needed for each action

Related reports
REP-103 Closed
Rep-107
REP-145 Closed
REP-194 Closed
REP-195 Closed



 Comments   
Comment by Sharon Beltaine [ 21/Oct/19 ]

Most problematic part of this need is renewal counts at this time.

It would be most helpful to have an Action Log instead of an Audit Log to capture various changes to the loan, such as renewal.

(From Marc Johnson) For those who have already implemented FOLIO, we need to migrate existing loans before converting audit log to action log. We need to look at the impact of migration for these institutions.

Developers need to know:
-which loan actions are relevant
-when the loan actions occur
-what information is needed for each action

Emma suggests looking at the Loan Epic and review the list of Loan Actions in that list, such as check in, check out, etc.

Generated at Fri Feb 09 00:21:24 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.