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

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

Jira Ticket created

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

UIIN-3330: Inventory: Filter Holdings Records by Call NumberBlocked

 

 

User Story

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

Description

Currently, the inventory app's search functionality is limited to the effective call number.

This makes it difficult to locate holdings 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 holdings 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 holdings, especially when dealing with large collections or when holdings have undergone changes in location or cataloging.

Acceptance Criteria

  • Search Functionality: The system supports searching for holdings by any call number (primary or additional). The search should be case-insensitive and should match partial call numbers.

  • Performance: Search operations are performant. Results should be returned quickly, even with a large number of holdings 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 holdings 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 154659.png
Anmerkung 2025-03-11 155116.png

 

Scenarios:

Scenario: Search for a holdings record 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 Holding in the Tabbar

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

When I enter "DEF789" (an additional call number for a holdings record) in the search field

And I click the "Search" button

Then the search results should include holdings record "ABC123" (which has "DEF789" as an additional call number)

Scenario: Filter holdings records 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 Holding in the Tabbar

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

When I enter "ABC456" (a primary call number for a holdings record) in the search field

Then the holdings list should only display holdings records 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