Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-527

Recently returned

    XMLWordPrintable

    Details

    • Template:
      UXPROD features
    • 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
    • Confidence factor:
      Low
    • Estimation Notes and Assumptions:
      Hide
      Scheduler feature is in place to trigger updates from "Recently returned" to "Available" (increased estimate due to scheduling feature not being in place)
      Item status updating mechanism is in place (if this is derived, then need to determine what information this is based up - is it a loan closed recently)
      When a loan was closed is already stored
      When an item status changed is already stored (and can be queried)
      Dedicated Check In API is in place (rather than just updating a loan, as currently is now)
      Show
      Scheduler feature is in place to trigger updates from "Recently returned" to "Available" (increased estimate due to scheduling feature not being in place) Item status updating mechanism is in place (if this is derived, then need to determine what information this is based up - is it a loan closed recently) When a loan was closed is already stored When an item status changed is already stored (and can be queried) Dedicated Check In API is in place (rather than just updating a loan, as currently is now)
    • Development Team:
      Prokopovych
    • Calculated Total Rank:
      74
    • 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

            blocks

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINV-337 Field mappings: Item - Item status handling logic for Recently returned

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Blocked
            clones

            New Feature - New feature requests UXPROD-92 Check-in: Implications to item status

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            has to be done after

            Task - A task that needs to be done. FOLIO-1953 SPIKE: propose an approach for scheduling tasks in Okapi

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            is blocked by

            New Feature - New feature requests UXPROD-594 Scheduler

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed
            is defined by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UICHKIN-94 Change status to recently returned at check in

            • P4 - lowest priority level, nice-to have things that require future discussion and design
            • Open

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UICHKIN-96 Multiple scans resulting in Recently returned

            • P4 - lowest priority level, nice-to have things that require future discussion and design
            • Blocked

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UICHKOUT-651 Check out items with the item status recently returned

            • TBD - To be determined
            • Open

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-539 Change Recently returned to Available

            • P4 - lowest priority level, nice-to have things that require future discussion and design
            • Blocked

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-1248 Search and filter recently returned items

            • TBD - To be determined
            • Open

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-1249 Recently returned: mark as missing, mark as withdrawn

            • TBD - To be determined
            • Open

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIREQ-517 Recently returned: Allow requests

            • P4 - lowest priority level, nice-to have things that require future discussion and design
            • Blocked

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIREQ-526 Add most recent check in service point/time to requests pick slips

            • TBD - To be determined
            • Draft
            relates to

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UICHKIN-39 Status change upon check in: recently returned

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

              Activity

                People

                Assignee:
                cmalmbor Cheryl Malmborg
                Reporter:
                ecboettcher Emma Boettcher
                Analysis Estimator:
                Emma Boettcher Emma Boettcher
                Front End Estimator:
                Aditya matukumalli Aditya matukumalli
                Back End Estimator:
                Marc Johnson Marc Johnson
                Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases