Circulation log/report (UXPROD-1704)

[UXPROD-1703] Circulation log of all actions filtered by a patron and/or a item with additional filters Created: 17/May/19  Updated: 01/Dec/20  Resolved: 30/Nov/20

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q3 2020
Parent: Circulation log/report

Type: New Feature Priority: TBD
Reporter: Darcy Branchini Assignee: Stephanie Buck
Resolution: Done Votes: 0
Labels: appreport, circ-log, resourceaccess, round_iv, split
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Circ history (Circ log 7_23).png     PNG File Circ history (Circ log 7_23, empty state).png    
Issue links:
Defines
is defined by CIRC-986 User details are absent in aged to lo... Closed
is defined by CIRC-1015 Not loaned checked in item was not re... Closed
is defined by MODAUD-35 Double http responses caused "Respons... Closed
is defined by MODAUD-44 Update mod-audit requests to handle R... Closed
is defined by CIRC-859 Spike: Technical design for Circulati... Closed
is defined by CIRC-929 Log Event Publisher for Notices Closed
is defined by CIRC-930 Log Event Publisher for Requests flow Closed
is defined by CIRC-933 Log Event Publisher for Loans Closed
is defined by CIRC-957 Declared lost, Anonymized, Renewed th... Closed
is defined by CIRCSTORE-247 Request log actions: Pickup expired, ... Closed
is defined by MODAUD-9 Create LogRecord schema Closed
is defined by MODAUD-10 GET /audit-data/logs for Circulation ... Closed
is defined by MODAUD-12 Prepare DB tables for Circulation Aud... Closed
is defined by MODAUD-14 LogEventSender library Closed
is defined by MODAUD-15 LogEventListener for mod-audit Closed
is defined by MODAUD-16 Loans: log actions Closed
is defined by MODAUD-17 Fees/fines: log actions Closed
is defined by MODAUD-18 Blocks: log actions Closed
is defined by MODAUD-19 Requests: log actions Closed
is defined by MODAUD-20 Check In/Check Out: log actions Closed
is defined by MODAUD-21 Notices: log actions Closed
is defined by MODAUD-28 User barcode isn't present in log rec... Closed
is defined by MODAUD-29 Template name in Notices log descript... Closed
is defined by MODAUD-30 Source field in Loan log record is empty Closed
is defined by MODAUD-31 Requests log actions - improvements Closed
is defined by MODAUD-32 A sent notice is not appearing in Cir... Closed
is defined by MODAUD-41 Fees/fines records in Circulation log... Closed
is defined by MODFEE-124 Log Event Publisher for Fees/Fines flow Closed
is defined by MODFEE-125 Log Event Publisher for Blocks flow Closed
is defined by MODFEE-131 Fee/fine actions do not appear in cir... Closed
is defined by UICIRCLOG-1 Select and open the Circulation Log app Closed
is defined by UICIRCLOG-2 Open Circulation Log search & filter ... Closed
is defined by UICIRCLOG-3 View circulation log table Closed
is defined by UICIRCLOG-4 Filtering & Searching the circulation... Closed
is defined by UICIRCLOG-5 Circulation Log filters Closed
is defined by UICIRCLOG-7 Circulation log select Action dropdown Closed
is defined by UICIRCLOG-11 Project Setup: ui-circulation-log Closed
is defined by UICIRCLOG-12 Circulation log ellipses pop up box Closed
is defined by UICIRCLOG-13 Circulation log permissions Closed
is defined by UICIRCLOG-16 Ellipses pop up for Manual Blocks Closed
is defined by UICIRCLOG-18 Ellipses menu option permissions Closed
is defined by UICIRCLOG-19 Update circulation log table headings Closed
is defined by UICIRCLOG-20 Switch service point filter from chec... Closed
is defined by UICIRCLOG-21 Show items for multiple-item notice i... Closed
is defined by UICIRCLOG-24 Newly added log should be at the top ... Closed
is defined by UX-382 Mockups for circulation log app Closed
is defined by UICIRCLOG-9 Circulation log Notices filter Closed
is defined by UICIRCLOG-10 Circulation log Loan filters Closed
is defined by UICIRCLOG-15 Circulation Audit log architecture Closed
is defined by UX-381 Icon for Circulation Log app Closed
is defined by UX-387 Show/hide items for multiple-item not... Closed
Duplicate
duplicates UXPROD-932 Bounced email report for patron notices Draft
Relates
relates to UXPROD-2467 Configure whether to anonymize staff ... Open
relates to MODAUD-8 Spike: Circulation log of all actions... Closed
relates to UXPROD-283 View status history on item record (Q... Closed
relates to UXPROD-2181 View last check in on item record Closed
relates to UXPROD-933 Loans in-app report: Determine item u... Closed
relates to UXPROD-2832 Circulation log updates Closed
relates to UXPROD-1056 Requests: track and display all chang... Draft
relates to UXPROD-1327 Circulation statistics for item on it... Analysis Complete
relates to UXPROD-2691 Circulation log export to CSV Closed
relates to FOLIO-2361 enable mod-audit-filter in platform-c... Closed
relates to UXPROD-283 View status history on item record (Q... Closed
relates to UXPROD-2181 View last check in on item record Closed
relates to UXPROD-933 Loans in-app report: Determine item u... Closed
relates to UXPROD-1407 Loans in-app report: Item loan history Closed
relates to UXPROD-1327 Circulation statistics for item on it... Analysis Complete
Requires
is required by UICIRCLOG-17 Cover ui-circulation-log by unit test... Closed
Epic Link: Circulation log/report
Front End Estimate: Large < 10 days
Front End Estimator: Hkaplanian
Front-End Confidence factor: Low
Back End Estimate: Large < 10 days
Back End Estimator: Hkaplanian
Development Team: Firebird
Report ID (pre-May 2019): ID449 (is a small part of this)
Report Contact(s):
Cheryl Malmborg, David Bottorff, Joanne Leary
Report Functional Area(s):
Resource Access
PO Rank: 79
PO Ranking Note: ranked high by round IV implementers
Rank: BNCF (MVP Feb 2020): R1
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: FLO (MVP Sum 2020): R2
Rank: GBV (MVP Sum 2020): R5
Rank: Lehigh (MVP Summer 2020): R2
Rank: MO State (MVP June 2020): R1
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R2

 Description   

In-app report with real-time data. Filters include date range, type of action/event, type of notice, material type, item, patron, patron group, etc. Actions/events included would be check-in, check-out, renewal, requests, notices, and more. For some institutions, patron data would be anonymized.

Circulation Log Ideas Spreadsheet: https://docs.google.com/spreadsheets/d/1appTFVPMZJSfO_WThrFkFurg7lSBe4eCtMC9hF1vacw/edit?usp=sharing

Log Examples: https://docs.google.com/spreadsheets/d/1JTWdAP54Fki_sXHmHbqCGWnxVRkcOum0I_SbWW66fuI/edit#gid=189640390

Requirements:
https://docs.google.com/spreadsheets/d/1D7bhNTH341yq9A7fo6AFNNnHYu4a5Stk3SoFCz71aXE/edit#gid=0

Tech Design:
https://folio-org.atlassian.net/wiki/pages/viewpage.action?pageId=1776581

NFR:
https://docs.google.com/spreadsheets/d/1sMu8FM_w1SpOosGQMJyBhFDKz-dIWPn1t7sqzpNYC2U/edit#gid=2108767638

Grooming

Export to CSV

Work on Exporting to CSV was not completed in Q3 2020. That work has moved to UXPROD-2691 Closed .



 Comments   
Comment by Lisa Sjögren [ 24/May/19 ]

Hi Darcy Branchini!

We will rank this feature when there is a more precise definition. We do _not _want a log which includes patron information, but would be interested in action history for items.

Comment by David Bottorff [ 01/Jul/19 ]

If this is available and sufficiently robust go-live, Chicago could wait on UXPROD-1627 Closed for up to 1 year.

Comment by Anya [ 02/Jul/19 ]

FCs are changing the rank of this to go-live and will wait for 1627.

Comment by Darcy Branchini [ 22/Aug/19 ]

Posting a use case from an email conversation with Andy Horbal and Joanne Leary with Cornell:
In general, we need to answer both kinds of questions – patron-initiated issues (claims returned, fine appeals, claims never checked out, etc.), and issues that relate to locating a book that is missing, in transit, etc. – might be needed by a patron, or for reserves, or internal processing, or something else. In all cases, it helps to have everything connected to circ history to piece together what might have happened to the book. When a book has NO circ history, we need to see details about internal processing (date record created, locations associated with processing or storage, item status history) along with physical descriptors such as the info in the 300 field of the BIB record.

I just didn't want to lose this information.

Comment by David Bottorff [ 23/Aug/19 ]

In relation to trying to rank this, I'm trying and failing to find where FOLIO will be keeping the return history of items, regardless of whether they are loaned. In relationship to Darcy's comment above, we need not just item status history but when and were it was scanned in the return app. In other words, it's not enough to know that an item was updated to available or recently returned, we need to know the service point, operator ID, etc. Is there somewhere that this data is being captured? Is there somewhere that this data can be viewed?

Comment by Emma Boettcher [ 23/Aug/19 ]

David Bottorff Requirements for UXPROD-283 Closed (planned for MVP) state that the item record show last time touched - date, operator, place (service point) - and link to a full history of status changes.

Comment by Erin Nettifee [ 26/Aug/19 ]

Thanks Emma Boettcher - that is helpful.

I think a concern with that as MVP is that it requires staff going into the Inventory module to get to the info, right? I know UXPROD-1742 Closed did not make it into the plan (the RA view).

I can't tell from the cap-mvp label what made it in with regards to Inventory UI.

Comment by Emma Boettcher [ 26/Aug/19 ]

Erin Nettifee Right, that's a consequence of JIRA features are organized more around functions than FOLIO apps. There is an Inventory epic (everything that was tagged with cap-mvp and linked Inventory epic: https://folio-org.atlassian.net/issues/?jql=labels%20%3D%20cap-mvp%20AND%20%22Epic%20Link%22%20%3D%20UXPROD-785%20ORDER%20BY%20cf%5B10002%5D%20ASC) but that doesn't get at all Inventory changes if they're supporting other product areas (Loans, Item states, Requests, etc. all have separate epics, so those features won't show up there). If there's something in particular you were looking for, let me know if I can help.

Comment by Erin Nettifee [ 26/Aug/19 ]

Hi Emma Boettcher - yah, I've reviewed the Inventory features labeled cap-mvp. Specifically, what we would like to know is what is being planned for the Inventory app in the absence of an RA-specific view, which did not make the cap plan. I realize that's broad, but also it's possible that changes to accommodate other functions will change things that RA is expecting to happen, and I'm betting that many SIGs would like this info, not just us...

Andrea Loigman

Comment by Mikita Siadykh [ 08/Jul/20 ]

hi Stephanie Buck Emma Boettcher

we need small clarification: what does in-app report with real-time data mean for you?

Comment by Stephanie Buck [ 09/Jul/20 ]

Mikita Siadykh, we'd like to be able to see the report with current (as close to to-the minute and second) data in the app. We don't want to have to go to another app to see it. Emma Boettcher feel free to add or correct!

Comment by Vasily Gancharov [ 09/Jul/20 ]

Stephanie Buck, by the "app" do you mean Circulation app or overall Folio? Also, would you like to see the reports on some existing page or a new page should be created for it?

Comment by Emma Boettcher [ 09/Jul/20 ]

Vasily Gancharov Stephanie Buck I attached some wireframes. This should be a search and filter app called the circulation log. Filtering or searching the entries in the circulation log should show the results on the same page (compare to the Inventory app).

Comment by Vasily Gancharov [ 09/Jul/20 ]

Thank you Emma Boettcher

Comment by Mikita Siadykh [ 09/Jul/20 ]

Stephanie Buck Emma Boettcher
in my understanding report with real-time data is data auto refresh when smth is change, e.g. I'm on this report page and, when someone made an action that produces log record, record is automatically appeared in the table without any refreshes from my side. If you mean this it will be an additional complexity (mb x2) and possible UX issues

or do you mean our standard flow when user should refresh page/make some searches etc to see new records?

Comment by Darcy Branchini [ 28/Sep/20 ]

Stephanie Buck, is there any talk of us being able to reuse parts of the circ log on the user record? One of my features is UXPROD-1627 Closed (Audit/history section of notices sent on user record) and I'm just wondering if we'll be able to re-use what you're working on. One thought I had is that it pulls the first 5 records from the notices section for a given user to display on the user record.

Comment by Stephanie Buck [ 28/Sep/20 ]

Hi Darcy Branchini. The Circulation log was designed so that it can be reused in other parts of FOLIO. I haven't been part of conversations about specific apps though.

Comment by Darcy Branchini [ 29/Sep/20 ]

Great news Stephanie Buck! Thank you!

Comment by Erin Nettifee [ 11/Nov/20 ]

Is there any information at this point about how the circulation log information will be structured? (e.g., a JSON object - anything in github we could look at?) We're having discussions at Duke about loan history and it would help to have some info if it's available.

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