Loans (UXPROD-788)

[UXPROD-2920] For In Transit Items Report, add normalized call number field for the item Created: 25/Feb/21  Updated: 06/Jan/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Loans

Type: New Feature Priority: TBD
Reporter: Erin Nettifee Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Gantt End to Start
has to be done after UXPROD-2002 Implement Normalized Call Number for ... Closed
Epic Link: Loans
Development Team: Vega
PO Rank: 0
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R3
Rank: Duke (Full Sum 2021): R2
Rank: 5Colleges (Full Jul 2021): R4
Rank: MO State (MVP June 2020): R2
Rank: U of AL (MVP Oct 2020): R3

 Description   

Current situation or problem:

The Inventory App has an in-app report available that shows all the items at a library that are currently in transit to another location.

Libraries would like this report to include the normalized call number for the item, to make it easier to sort a list for shelf searching and other troubleshooting activities.

In scope

  • Adding the requested call number field to the report

Out of scope

  • Building a UI or any additional features for running the report

Use case(s)

  • A library would like to run a shelf search to see if items that are in transit were accidentally shelved before being returned. They run the report, narrow it down in Excel to items that are at their location, and then sort the report by the call number field to allow staff to quickly walk through the shelves looking for the items.

Proposed solution/stories

Links to additional info

Questions



 Comments   
Comment by Erin Nettifee [ 19/May/21 ]

Cheryl, it looks like the original report was built as part of the Loans epic by Emma, so I've put this there. Sorry. I've also removed the block link since 2002 was done in Iris.

Comment by Erin Nettifee [ 04/Oct/22 ]

Putting this in Vega's queue since they have previously worked on this report, but please move if that is not correct.

Generated at Fri Feb 09 00:27:56 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.