Alert staff to special location at checkin

Description

Current situation or problem:
When an item is checked in at a service point that is not assigned to its effective location, the item status changes to in transit, and a modal appears on the screen with the option to print a routing slip.

In contrast, when an item is checked in at a service point that is assigned to its effective location, there is no modal to the user informing them of the item's location. (Though the location displays on the check in screen.) Some locations may be unusual to see at particular service points, though, so displaying a modal in those instances, similar to when an item goes in transit, could be helpful.

In scope

  • Within the service point-location relationship, allow tenant to flag which locations need emphasis at their home service point (while still having those service points assigned to those)

  • When a user checks in an item with that effective location at that service point, present an alert as they check the item in

Out of scope

Use case(s)

  • Locations that are often temporary locations (e.g., Reserves) may also benefit from an extra alert to staff, since the location will differ from the item's spine label.

  • Main Library has one service point for its entire building, but if a reference item is checked in, it needs to be sent to a particular shelf for reshelving. The message would prompt staff to remember to put the reference item on a special cart for reshelving.

Proposed solution/stories

Links to additional info

Questions

Priority

Fix versions

None

Development Team

Vega

Assignee

Solution Architect

Parent Field Value

None

Parent Status

None

Checklist

hide

TestRail: Results

Activity

Show:

Susan Kimball February 16, 2025 at 12:38 AM

RA Review: Still desired functionality for non-stack locations like New Book Shelves, Displays, reserves, reference, etc.

David Bottorff April 13, 2022 at 3:46 PM

This is in particular an issue because we've noticed some unpredictable lag times with the screen refreshing in the Check-in App in production. Not significant, we don't think (occasionally a book takes a second or so before it appears on the screen, which is much slower than usual), so staff who are "in the zone" checking in large quantities of books are more likely to miss something.

David Bottorff April 13, 2022 at 3:34 PM

This continues to be a problem for Chicago, as we have a small number of reference collections that pass through our main processing error that continue to be mis-routed and mis-shelved. Now that we've implemented FOLIO, I would hope that this would be a relatively simple feature to add.

Holly Mistlebauer June 17, 2020 at 9:15 PM

Chicago comment from Round IV Outliers spreadsheet: This keeps us from mis-routing things. Without this in our previous system, we found a lot of mis-shelving. -Tod Olson

Emma Boettcher September 10, 2019 at 2:47 PM

The biggest use case is for items with a temporary location, where the book is labeled according to its permanent location, but is temporarily shelved in the Reserves section (or some other temporary location). Usually, the book will also have a sticker (or some labeling) that says Reserves, but in case it does not, the system should draw the user's attention to the fact that this book is not shelved according to what it says on the physical item. Besides temporary locations, there may be other use cases - a location that circulates very rarely or a location whose items are usually returned to primary service point A but it's acceptable for them to be returned to service point B.

Because effective location displays on the check in screen, and because some libraries do physically label some of their items with temporary locations, I didn't feel that this was as high priority as some of the other loans features. I'll also note that I'm differentiating this from in transit (already implemented), where the service point used at check in is not assigned to the item's effective location and the user is alerted to that.

Details

Reporter

PO Rank

97

PO Ranking Note

CM: Based on R1 and R2 rankings.

Estimation Notes and Assumptions

CB: Per agreement with Jakub and the cap planning team, some of us non-developers are going to estimate the remaining unestimated features. I will label this "swag" so we know to revisit when we have more info.

Front End Estimate

Medium < 5 days

Front End Estimator

Front-End Confidence factor

Low

Back End Estimate

XL < 15 days

Back End Estimator

Rank: FLO (MVP Sum 2020)

R1

Rank: 5Colleges (Full Jul 2021)

R4

Rank: Cornell (Full Sum 2021)

R2

Rank: Chalmers (Impl Aut 2019)

R4

Rank: GBV (MVP Sum 2020)

R2

Rank: hbz (TBD)

R1

Rank: Hungary (MVP End 2020)

R1

Rank: Grand Valley (Full Sum 2021)

R1

Rank: TAMU (MVP Jan 2021)

R1

Rank: Chicago (MVP Sum 2020)

R1

Rank: MO State (MVP June 2020)

R4

Rank: U of AL (MVP Oct 2020)

R4

Rank: MTSU

R3

Rank: Lehigh (MVP Summer 2020)

R2

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created November 19, 2018 at 7:12 PM
Updated 7 hours ago
TestRail: Cases
TestRail: Runs