Inventory
(UXPROD-785)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Sunflower (R3 2024) | Parent: | Inventory |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Charlotte Whitt | Assignee: | Christine Schultz-Richert |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | GBV, LC-priority2, browse, cataloging, loc, metadatamanagement | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||
| Epic Link: | Inventory | ||||||||||||||||||||||||||||
| 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 | ||||||||||||||||||||||||||||
| Development Team: | Spitfire | ||||||||||||||||||||||||||||
| Report Functional Area(s): |
Metadata Management
|
||||||||||||||||||||||||||||
| PO Rank: | 0 | ||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R1 | ||||||||||||||||||||||||||||
| Description |
|
Current situation or problem: Enhancement request building upon the recent work done implementing Call number sort for item-level call number sorting,
In scope:
Out of scope: Bibliographic-level call number browse (covered in
Use case: As a staff user I want to sort query results by item level call number, many queries don't use item tables, and holdings records don't always have item records attached (most commonly for special collections) Proposed solution/stories
Links to additional info Questions
|
| Comments |
| Comment by Joanne Leary [ 01/Dec/21 ] |
|
In the use case description above, it should say "I want to sort query results by holdings level call number" (not item level call number). |
| Comment by Holly Mistlebauer [ 07/Dec/21 ] |
|
Charlotte Whitt: This is a bug, not a feature. Please move it to the appropriate project. Thanks... |
| Comment by Anya [ 10/Jan/22 ] |
|
Support : Charlotte Whitt states we currently do not have this functionality so it is a feature and not a bug. |
| Comment by Joanne Leary [ 10/Jan/22 ] |
|
We at Cornell recently discovered that the item-level sort does not sort correctly in the LDP when using Postgres to create queries. When applying the "effective shelving order" as a sort criteria in a Postgres query, the results are not in correct LC call number order. This may be some kind of issue with Postgres rather than the actual sorting code, but the end result for us is that it doesn't work. The workaround (also not perfect) is to export the results of the query to Excel, re-sort the results by the effective shelving order column, delete that column, and then delete duplicate rows. Ugh. |
| Comment by Holly Mistlebauer [ 10/Jan/22 ] |
|
Oops! I moved this to MODINV as a bug before seeing that this is a feature. So, I moved this issue back to UXPROD and changed the Issue Type to "New feature'. Sorry for the confusion... |
| Comment by Debra Howell [ 03/Aug/22 ] |
|
Hi Charlotte Whitt I see this is listed for Nolana but there is no dev team assigned. Do you have any updates? |
| Comment by Khalilah Gambrell [ 10/Oct/22 ] |
|
Hey Charlotte Whitt - will this work be done in Nolana? If not, can we most this to Not Scheduled or another release? |
| Comment by Debra Howell [ 08/Jun/23 ] |
|
Khalilah Gambrell Is there anything we can do to elevate this? I'm also not sure who the PO should be - the list still says Charlotte Whitt . If this could make it's way into the November Poppy release, it would really help us. This issue is blocking a number of reports that we still need. |
| Comment by Khalilah Gambrell [ 08/Jun/23 ] |
|
Hey Debra Howell and Thomas Trutt I think this work will need to be reviewed by Spitfire. cc: Christine Schultz-Richert |
| Comment by Christine Schultz-Richert [ 09/Jun/23 ] |
|
Hi Debra Howell & Thomas Trutt There is another feature for browsing both bibliographic and holdings call numbers - https://folio-org.atlassian.net/browse/UXPROD-4120 . It sounds like the scope for this feature (
I can split
|
| Comment by lew235 [ 09/Jun/23 ] |
|
Christine Schultz-Richert yes, this sounds correct. Cornell's most critical need is for the holdings-level call numbers to be available for reporting (LDP) when items are lacking. So "Generate shelving order for holdings call numbers according to the normalization rules of the call number type (using the same rules as are currently applied to item shelving order)" would be the most important piece. The Inventory browse, of course, is also desirable. |