Status change upon check in: recently returned

Description

User story: As a circulation staff member, I need to know when items have been recently checked in, so that I know they're more likely to be still at the circulation desk than on the shelf.

Scenarios:

  1. Scenario

    • Given an item that is Checked out, with no open requests

    • When the item is checked in at a service point assigned to its effective location

    • Then the item’s status changes to Recently returned

  2. Scenario

    • Given an item that is In transit, with no open requests

    • When the item is checked in at a service point assigned to its effective location

    • Then the item’s status changes to Recently returned

  3. Scenario

    • Given an item that is Available, with no open requests

    • When the item is checked in at a service point assigned to its effective location

    • Then the item’s status changes to Recently returned

  4. Scenario

    • Given an item that is Recently returned, with no open requests

    • When the item is checked in at a service point assigned to its effective location

    • Then the item’s status changes to Recently returned

Notes: In conversations with the RA SIG, we have discussed item status and the benefits of separating an item's availability (e.g., Available, Checked out, or In transit) from what it's needed for (e.g., Patron requests) and if it is in staff processes (e.g., Staff search, Digitization). In transit is similar to Available and Checked out (both describe an item's Availability), so the anticipated complexity of an item's status is out of scope for this story.

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Emma Boettcher April 8, 2019 at 2:45 PM

Duplicate with .

Emma Boettcher September 19, 2018 at 1:25 PM

I split this into its own issue from but you're right, it's not fully drafted (and yes, it depends on scheduler using the shelving lag time).

Cate Boerema September 19, 2018 at 9:12 AM

I am linking the scheduling spike as a blocker on this assuming this story will include a scenario that makes use of shelving lag time. If that's not correct, please feel free to remove the blocker.

Cate Boerema September 19, 2018 at 9:07 AM
Edited

Hi . I was just looking for stories that are blocked by scheduler and found this one. Are you still working on it, or can we mark it open for the developers?

Oh, and I think you are aware that we have a "Shelving lag time" setting on the service point. You could specify that we look to that setting to decide when to change the status to Available.

Thanks!

Duplicate

Details

Assignee

Reporter

Priority

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created September 18, 2018 at 3:56 PM
Updated April 8, 2019 at 2:45 PM
Resolved April 8, 2019 at 2:45 PM
TestRail: Cases
TestRail: Runs