Inventory search. Support browse searches, e.g. call numbers
(UXPROD-2988)
|
|
| Status: | Open |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Sunflower (R3 2024) | Parent: | Inventory search. Support browse searches, e.g. call numbers |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Khalilah Gambrell | Assignee: | Khalilah Gambrell |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | LC-priority2, SolutionArchitecture, browse, cataloging, loc, metadatamanagement | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||
| Epic Link: | Inventory search. Support browse searches, e.g. call numbers | ||||||||||||||||||||||||||||
| Front End Estimate: | XL < 15 days | ||||||||||||||||||||||||||||
| Front End Estimator: | Khalilah Gambrell | ||||||||||||||||||||||||||||
| Front-End Confidence factor: | 20% | ||||||||||||||||||||||||||||
| Back End Estimate: | XXL < 30 days | ||||||||||||||||||||||||||||
| Back End Estimator: | Khalilah Gambrell | ||||||||||||||||||||||||||||
| Back-End Confidence factor: | 20% | ||||||||||||||||||||||||||||
| Development Team: | Spitfire | ||||||||||||||||||||||||||||
| PO Rank: | 0 | ||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R1 | ||||||||||||||||||||||||||||
| Rank: MI State-Lib of MI (Sum 2021): | R1 | ||||||||||||||||||||||||||||
| Description |
|
Librarians want the ability to browse instance records via Inventory app by and mod-search must be updated to support. In scope:
Out of scope:
Use cases: https://folio-org.atlassian.net/wiki/display/MM/Browse+Use+Cases Mockups of call number/subject browse work: https://drive.google.com/drive/folders/1duaMQ4jjzQ6I_Ei7c_rSbsGrWdgZZ7wl' Requirements consideration
Proposed solution/stories:
Examples > Browse by titles
|
| Comments |
| Comment by Mikhail Fokanov [ 27/Jun/22 ] |
|
Khalilah Gambrell, Should it be filters for titles browse? |
| Comment by Mikhail Fokanov [ 27/Jun/22 ] |
|
I see the following requirement from Janet Baldwin:
According to this requirement, the business case is that there could be a "typo in the record". Let's imagine, that the title length is 30 characters and the typo is at 5th letter. For such case it is not so convenient to browse through at least 10+ pages to find appropriate title. The best practice to help users to find the appropriate information is using "did you mean" and "fuzzy search". Both features will provide users with instances' titles that he is searching for. |
| Comment by Khalilah Gambrell [ 27/Jun/22 ] |
|
Mikhail Fokanov - I have not written requirements yet. Once I do, I will schedule a meeting to discuss. |
| Comment by Janet Baldwin [ 27/Jun/22 ] |
|
Thanks, Mikhail Fokanov and Khalilah Gambrell. I'll call this to the attention of others on the Cataloging and Metadata Task Force (Michigan State University/Library of Michigan) so we can start coming up with other use cases. |
| Comment by Charlotte Whitt [ 14/Jul/23 ] |
|
Hi Khalilah Gambrell Christine Schultz-Richert - In a talk with Stanford, they asked about when browse by instance titles would be available. I see this feature is scoped for Orchid, but still Open. Are you planning to have this new work in for Poppy, and the feature just need to be updated? |
| Comment by Khalilah Gambrell [ 14/Jul/23 ] |
|
Hello Charlotte Whitt and Laszlo Jakusovszky Unfortunately we are not able to implement this feature for the Poppy release. It is a candidate for "Q" but we need more time defining requirements.
|
| Comment by Michelle Futornick [ 05/Oct/23 ] |
|
could someone remove "Orchid" from the Release field so that this issue won't show up in Orchid-filtered lists? Thanks! |