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

Check-in: Implications to item status

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed (View Workflow)
    • Priority: P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Template:
    • Epic Link:
    • Analysis Estimate:
      Medium < 5 days
    • Front End Estimate:
      Small < 3 days
    • Back End Estimate:
      XL < 15 days
    • Confidence factor:
      Low
    • Estimation Notes and Assumptions:
      Hide
      * Item status updating mechanism is in place (and this does not involve creating any new type of record for state derivation, if that is the approach we choose)
      * Excludes recently returned and in transit as these have become separate issues
      Show
      * Item status updating mechanism is in place (and this does not involve creating any new type of record for state derivation, if that is the approach we choose) * Excludes recently returned and in transit as these have become separate issues
    • Development Team:
      Prokopovych
    • Calculated Total Rank:
      80
    • Rank: Chalmers (Impl Aut 2019):
      R1
    • Rank: Chicago (MVP Sum 2020):
      R1
    • Rank: Cornell (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R1
    • Rank: GBV (MVP Sum 2020):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      R1
    • Rank: TAMU (MVP Jan 2021):
      R1
    • Rank: U of AL (MVP Oct 2020):
      R1

      Description

      Checking an item in will change item status. Tania is handling status expectations where requests are concerned, but there will be other, non-request scenarios to consider at check in. For example, once we implement service points (UXPROD-169 appears to have been deleted, or I don't have access) and the relationship between service points and locations, some checked in items will be home while others will need to go "in transit". I am sure there are more.

      Discussed 2/28/18 with Loans subgroup. Checkin can trigger the following statuses.

      • Recently returned - when checked in, no pending requests, and checked in at the item's location. (After a set time, status changes to available)
      • Available - when checked in, no pending requests, and checked in at the item's location. (Triggered by check in when institution is not using recently returned)
      • In transit - when checked in, no pending requests, and checked in at a location other than the item's location
      • On hold - when checked in, pending request, and checked in at the request's pick-up location (May need to be delayed, similar to how an item with no requests is "recently returned" before it is "available")
      • in transit/requested - when checked in, pending request, and checked in at a location other than the request's pick-up location

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                ecboettcher Emma Boettcher
                Reporter:
                cboerema Cate Boerema
                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:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases