Details

    • Epic Link:
    • Analysis Estimate:
      Small < 3 days
    • Front End Estimate:
      Medium < 5 days
    • Back End Estimate:
      XL < 15 days
    • Confidence factor:
      Low
    • Estimation Notes and Assumptions:
      Hide
      Scheduler feature is in place to trigger updates from "Recently returned" to "Available"
      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" 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:
      Core: Functional
    • Rank: Chalmers:
      NOT NEEDED
    • Rank: Chicago:
      go-live
    • Rank: Cornell:
      go-live
    • Rank: 5Colleges:
      go-live
    • Rank: Lehigh:
      go-live
    • Rank: TAMU:
      go-live
    • Rank: U of AL:
      go-live
    • Rank: Bremen:
      go-live

      Description

      When an item is checked in at a service point at its home location, its status should change to Recently Returned (informing staff and patrons that while it's not checked out, it may not be on the shelf yet). After the shelving lag time for the service point has passed, then the item's status, if still Recently Returned, should become Available.

      The transition from Recently Returned --> Available might be done on a rolling, "live" basis but may also be acceptable as a batch job, if that functionality (including the ability to see, edit & cancel/pause) exists elsewhere.

        Attachments

          Issue Links

            Expenses

              Activity

              Hide
              Klute Uschi added a comment - - edited

              The Shelving Lag Time can be set per Service Point. In my experience it should be configurable per location. Some of our libraries have 0 or 30 or 60 minutes in their settings, others have 1 or 2 days, as they have closed stacks, sometimes far away with daily car transport.
              There are two Service Points which handle items from this closed stack and also items from within the central library.

              Show
              Klute Uschi added a comment - - edited The Shelving Lag Time can be set per Service Point. In my experience it should be configurable per location. Some of our libraries have 0 or 30 or 60 minutes in their settings, others have 1 or 2 days, as they have closed stacks, sometimes far away with daily car transport. There are two Service Points which handle items from this closed stack and also items from within the central library.
              Hide
              ecboettcher Emma Boettcher added a comment -

              The RA SIG discussed this again yesterday, and they decided to prioritize easier setup (shelving lag time on service point) over granularity (shelving lag time on location), even with the remote storage example in mind.

              One comment from the group supporting this decision was that they could also set up a service point for the remote storage/closed stacks, sending items in that location in transit to that service point, and checking in items at the remote location/closed stacks when they arrived there.

              Show
              ecboettcher Emma Boettcher added a comment - The RA SIG discussed this again yesterday, and they decided to prioritize easier setup (shelving lag time on service point) over granularity (shelving lag time on location), even with the remote storage example in mind. One comment from the group supporting this decision was that they could also set up a service point for the remote storage/closed stacks, sending items in that location in transit to that service point, and checking in items at the remote location/closed stacks when they arrived there.

                People

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

                  Dates

                  • Created:
                    Updated: