Details
-
Type:
New Feature
-
Status: Blocked (View Workflow)
-
Priority:
TBD
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:
-
Template:
-
Potential Workaround:No workaround, but unlike other item states, Recently returned items only stay that way for a short time (shelving lag time).
-
Epic Link:
-
Analysis Estimate:Small < 3 days
-
Front End Estimate:Medium < 5 days
-
Back End Estimate:XXL < 30 days
-
Front-End Confidence factor:Low
-
Estimation Notes and Assumptions:
-
Development Team:Vega
-
Calculated Total Rank:
-
Kiwi Planning Points (DO NOT CHANGE):1
-
PO Rank:65
-
PO Ranking Note:Not replaceable by custom item status (since recently returned needs to automatically change to Available, based on shelving lag time), but not necessarily high-priority.
-
Rank: Chalmers (Impl Aut 2019):R5
-
Rank: Chicago (MVP Sum 2020):R4
-
Rank: Cornell (Full Sum 2021):R4
-
Rank: Duke (Full Sum 2021):R1
-
Rank: 5Colleges (Full Jul 2021):R4
-
Rank: FLO (MVP Sum 2020):R4
-
Rank: GBV (MVP Sum 2020):R2
-
Rank: Grand Valley (Full Sum 2021):R1
-
Rank: hbz (TBD):R1
-
Rank: Hungary (MVP End 2020):R1
-
Rank: Lehigh (MVP Summer 2020):R2
-
Rank: Leipzig (Full TBD):R1
-
Rank: Mainz (Full TBD):R3
-
Rank: MO State (MVP June 2020):R4
-
Rank: TAMU (MVP Jan 2021):R2
-
Rank: U of AL (MVP Oct 2020):R4
Description
Current situation or problem:
When an item is checked in at a service point assigned to its effective location, its status changes to Available. This can confuse patrons, who might assume that the item is already on the shelf.
In scope
- Creation and handling of Recently returned item status
- When an item is checked in at a service point assigned to its effective location, its status changes to Recently returned
- if checked in again while its status is Recently returned, this restarts the clock
- When the shelving lag time for the service point has passed, it becomes Available
Out of scope
Use case(s)
Proposed solution/stories
Links to additional info
Questions
- Is the change from Recently returned --> Available done on a live/rolling basis or as a batch job?
TestRail: Results
Attachments
Issue Links
- has to be done after
-
FOLIO-1953 SPIKE: propose an approach for scheduling tasks in Okapi
-
- Closed
-
- is blocked by
-
UXPROD-3652 Item Status: Recently Returned
-
- Open
-
- is defined by
-
UICHKIN-94 Change status to recently returned at check in
-
- Open
-
-
UICHKIN-96 Multiple scans resulting in Recently returned
-
- Blocked
-
-
UICHKOUT-651 Check out items with the item status recently returned
-
- Open
-
-
UIREQ-517 Recently returned: Allow requests
-
- Blocked
-
-
UIREQ-526 Add most recent check in service point/time to requests pick slips
-
- Draft
-
- relates to
-
UICHKIN-39 Status change upon check in: recently returned
-
- Closed
-
-
UXPROD-3652 Item Status: Recently Returned
-
- Open
-