Item states (status) (UXPROD-1321)

[UXPROD-2175] Audit status changes and display in app (status history) Created: 02/Dec/19  Updated: 27/Dec/23

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Item states (status)

Type: New Feature Priority: P2
Reporter: Emma Boettcher Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: cap-mvp-split, latam2, q4-2019-spillover
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File uxprod-2175-status-history.png    
Issue links:
Defines
is defined by MODAFILT-9 Spike: familiarization with mod-audit... Open
is defined by CIRC-1133 Some filters not finding recent results Closed
is defined by MODAFILT-7 Capture check out in audit app Closed
is defined by MODAFILT-8 Capture check in in audit app Closed
Relates
relates to UXPROD-2467 Configure whether to anonymize staff ... Open
relates to UXPROD-283 View status history on item record (Q... Closed
relates to UXPROD-2181 View last check in on item record Closed
Epic Link: Item states (status)
Front End Estimate: XXL < 30 days
Front End Estimator: Viktor Soroka
Back End Estimate: XXL < 30 days
Back End Estimator: Dmytro Popov
Estimation Notes and Assumptions: It is needed to create a new UI app and cover the scope.

Backend:
Need to rethink the approach to do it on the backend as the existing similar approach for loan actions history is not considered a best practice and needs improvements
Kiwi Planning Points (DO NOT CHANGE): 16
PO Rank: 93.4
Rank: Chalmers (Impl Aut 2019): R2
Rank: Chicago (MVP Sum 2020): R2
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R2
Rank: GBV (MVP Sum 2020): R4
Rank: hbz (TBD): R2
Rank: Lehigh (MVP Summer 2020): R2
Rank: MO State (MVP June 2020): R2
Rank: U of AL (MVP Oct 2020): R3

 Description   

Current situation or problem:
FOLIO tracks an item's current item status and the date and time it changed to that item status, but there is no information available in the UI about previous item statuses. (Some information about whether an item has circulated is available through the circulation log.)

In scope
Every time status changes, capture:

  • item
  • status it changed from
  • status it changed to
  • when (date and time)
  • app (for context as to how status changed) (differentiate batch changes from individual changes)
  • user
  • user's service point, if applicable (helpful for consortia)

Out of scope

  • Any other changes to item record (may be useful to capture at some point, but not as part of this story)
  • configuring whether the user changing the item status is captured or not ( UXPROD-2467 Open )

Use case(s)

Proposed solution/stories

  • Mod-audit was originally proposed as an implementation of this, but discussion hasn't proceeded since those stories were created.

Links to additional info
https://docs.google.com/spreadsheets/d/19_aA7bhRIxhcC6Gz-rK_LrfOtz8F5VaOmOcsFsdGU8I/edit#gid=1676679098

Questions

  • Capture this along with all other changes to an item?
  • To what extent can this build on/reuse work from the circulation log?

split from: UXPROD-283 Closed .



 Comments   
Comment by Andy Horbal [ 11/Dec/19 ]

We're working on ranking this as per discussion at the 12/9 RA SIG meeting. For this log to be useful, we think it needs to capture ALL loan actions, including most especially renewals. Is this possible?

Comment by Emma Boettcher [ 11/Dec/19 ]

Andy Horbal Thanks for taking a look at it. Based on previous discussions, I'm trying to differentiate between item status (this feature) and all loan activity (https://folio-org.atlassian.net/browse/UXPROD-1407). It sounds like what you're saying is that at least UXPROD-1407 Closed is useful, and I'm not sure if showing an item's status over time is as well.

Comment by Andy Horbal [ 11/Dec/19 ]

Okay, that makes sense! We think both are important, but this is definitely less so for our purposes. We'll rank the issue accordingly!

Comment by Erin Nettifee [ 12/Dec/19 ]

Hi Emma Boettcher - Duke would rank both UXPROD-1407 Closed and this one as go-live for our full deployment in 2021.

Comment by Mark Canney [ 14/Dec/19 ]

Hi Emma Boettcher. Lehigh would rank both item loan history and item status as go-live requirements. Thanks, Mark

Comment by Kristin Martin [ 30/Dec/19 ]

Assuming this info is available via LDP and that check-in is captured and displayed regardless of whether item is loaned ( UXPROD-2181 Closed ) Chicago believes we can wait for this, and have ranked accordingly.

Comment by Mark Canney [ 14/Jan/20 ]

We can go along with that workaround. If the info is available in the LDP then we can wait for this in the UI.

Comment by Cate Boerema (Inactive) [ 06/Jul/20 ]

Hi Stephanie Buck. I am assigning this feature to Firebird since you guys will be working with mod-audit. Per Emma Boettcher, logging this data (even if it isn't displayed) is a must-have for MVP. Not assigning a fix version yet, but wanted you to be aware of this as a potential future project.

Comment by Marie Widigson [ 02/Dec/20 ]

How is this issue related to Circulation log in Honeysuckle? Why is the issue blocked?
As we may not be using LDP, we would like this to be in FOLIO UI.

Comment by Erin Nettifee [ 09/Mar/21 ]

Stephanie Buck - I think this should be unblocked and brought into the circulation log development process. Duke would consider this a must have for our go-live in 2022.

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