Details
Reporter
Emma BoettcherEmma BoettcherPO Rank
93.4Estimation 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 improvementsFront End Estimate
XXL < 30 daysFront End Estimator
Viktor SorokaViktor SorokaBack End Estimate
XXL < 30 daysBack End Estimator
Dmytro PopovDmytro PopovRank: 5Colleges (Full Jul 2021)
R2Rank: Cornell (Full Sum 2021)
R4Rank: Chalmers (Impl Aut 2019)
R2Rank: GBV (MVP Sum 2020)
R4Rank: hbz (TBD)
R2Rank: Chicago (MVP Sum 2020)
R2Rank: MO State (MVP June 2020)
R2Rank: U of AL (MVP Oct 2020)
R3Rank: Lehigh (MVP Summer 2020)
R2TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Reporter
Emma Boettcher
Emma BoettcherPO Rank
93.4
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
Front End Estimate
XXL < 30 days
Front End Estimator
Viktor Soroka
Viktor SorokaBack End Estimate
XXL < 30 days
Back End Estimator
Dmytro Popov
Dmytro PopovRank: 5Colleges (Full Jul 2021)
R2
Rank: Cornell (Full Sum 2021)
R4
Rank: Chalmers (Impl Aut 2019)
R2
Rank: GBV (MVP Sum 2020)
R4
Rank: hbz (TBD)
R2
Rank: Chicago (MVP Sum 2020)
R2
Rank: MO State (MVP June 2020)
R2
Rank: U of AL (MVP Oct 2020)
R3
Rank: Lehigh (MVP Summer 2020)
R2
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created December 2, 2019 at 6:49 PM
Updated January 21, 2025 at 5:24 PM
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)
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: .