Universal Search App (UXPROD-858)

[UXPROD-2243] Pre-order searching to identify what is owned and what must be purchased Created: 27/Jan/20  Updated: 09/Dec/21

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Universal Search App

Type: New Feature Priority: P4
Reporter: Dennis Bridges Assignee: Dennis Bridges
Resolution: Unresolved Votes: 0
Labels: acquisitions, crossrmapps, needs-ranking, orders
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Potential Workaround: Search in applications individually to identified what material the library already owns or has access to. Eg. Orders, agreements, eHoldings, inventory
Epic Link: Universal Search App
Development Team: Thunderjet
Kiwi Planning Points (DO NOT CHANGE): 5
PO Rank: 30
PO Ranking Note: Matching the current calculated total rank.
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R3
Rank: Cornell (Full Sum 2021): R2
Rank: Duke (Full Sum 2021): R2
Rank: 5Colleges (Full Jul 2021): R4
Rank: 5Colleges (ERM Jun 2020): R4
Rank: GBV (MVP Sum 2020): R2
Rank: hbz (TBD): R4
Rank: MO State (MVP June 2020): R2
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R1

 Description   

Problem: The first step for an acquisitions librarian in making the decision to purchase material is identifying what of it, if anything, the institution currently owns. This can be difficult and time consuming as information is stored in separate systems or applications depending on it how it was acquired. Being able to do this from one place inside FOLIO would improve both the accuracy and efficiency of acquisitions.

Use cases:

  • See document below

Requirements:

  • User is able to search through all material currently owned, accessible and on order. Such that they can confirm the library will need to acquire this material or more of this material.
  • Search can be executed with a Title, package name or Product ID (such as ISSN).
  • Filtering can be done by...TBD
  • Search will identify the source of information returned (Eg. order, agreement, instance)

Approach:
App interaction group discussions at WOLFcon2020 have identified that Codex may be the most viable solution for delivering a single search experience solution for this problem.

Specific use cases for pre-order searching:
https://docs.google.com/document/d/1rIpsXkXg6CBoejXXYid377NF_j7CQncqyA0XcNcZTUk/edit

Use Cases from WOLFcon that resulted in the creation of this feature:
https://docs.google.com/document/d/1TwxLXAsxog-MPpV4oyLKv_uKJN3uGyzSDeDk3CNO110/edit


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