/
[Jira Tickets created] Drafts UI - Inventory: Filter Item Records by Call Number

[Jira Tickets created] Drafts UI - Inventory: Filter Item Records by Call Number

Jira Ticket created

This draft is finished. Further work and discussion will happen in the Jira Ticket:

UIIN-3337: Inventory: Filter Item Records by Call NumberBlocked

 

 

User Story

  • Search: A filter option should be implemented in order to enable the limitation of the results to records which match only values of the "effective call number". 

Description

Currently, the inventory app's search functionality is limited to the primary call number of an item.

This makes it difficult to locate items based on previous call numbers or alternative call numbers (e.g., for different editions or locations). This user story addresses this limitation by enabling librarians to search item records by any associated call number, whether it's the primary call number or an additional call number. This will significantly improve the efficiency of locating items, especially when dealing with large collections or when items have undergone changes in location or cataloging.

Acceptance Criteria

  • Search Functionality: The system supports searching for items by any call number (primary or additional). The search operations are performant. Results should be returned quickly, even with a large number of item records. Define specific performance thresholds (e.g., search results returned in under 2 seconds).

  • Performance: Search operations are performant. Results should be returned quickly, even with a large number of items records. Define specific performance thresholds (e.g., search results returned in under 2 seconds).

  • User Interface: The search and filter interface is intuitive and easy to use. It should be clear how to search and filter by call number.

  • Data Integrity: The search functionality returns accurate results. No items are omitted or incorrectly included in the results.

  • Testing: Thorough testing (unit, integration, and user acceptance testing) is conducted to ensure the search and filtering functionality works correctly and meets all requirements.

 

Mock-up

Screenshots:

Anmerkung 2025-03-11 162024.png
Anmerkung 2025-03-11 162004.png

 

Scenarios

Scenario: Search for an item by an additional call number

Given I am logged in as a librarian

And I am in the left sidebar of the Inventory app

And I have selected Item in the Tabbar

And I have selected “All” as a search criteria from the dropdown

When I enter "DEF789" (an additional call number) in the search field

And I click the "Search" button

Then the search results should include item "XYZ123" (which has "DEF789" as an additional call number)

Scenario: Filter items by a primary call number

Given I am logged in as a librarian

And I am in the left sidebar of the Inventory app

And I have selected Items in the Tabbar

And I have selected “Effective call number” as a search criteria from the dropdown

When I select "ABC456" (a primary call number) from the call number filter dropdown

Then the item list should only display items with the primary call number "ABC456"

Questions

/

Comments

We decided to not persue making addtional call numbers available in the “Browse” functionality, because this would mean a significant development effort as mentioned by the PO XXX

Labels

Dependencies

 

Requirement analysis

API-calls

 

Related content