Inventory
(UXPROD-785)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | TBD | Parent: | Inventory |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Charlotte Whitt | Assignee: | Ryan Taylor |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | cornell-priority, epam-folijet, inventory, metadatamanagement, mm-review, relink, round_iv | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||
| Issue links: |
|
||||||||||||||||||||
| Release: | Not Scheduled | ||||||||||||||||||||
| Epic Link: | Inventory | ||||||||||||||||||||
| Analysis Estimate: | Very Small (VS) < 1day | ||||||||||||||||||||
| Analysis Estimator: | Charlotte Whitt | ||||||||||||||||||||
| Front End Estimate: | Medium < 5 days | ||||||||||||||||||||
| Front End Estimator: | Niels Erik Nielsen | ||||||||||||||||||||
| Front-End Confidence factor: | Medium | ||||||||||||||||||||
| Back End Estimate: | Medium < 5 days | ||||||||||||||||||||
| Back End Estimator: | Niels Erik Nielsen | ||||||||||||||||||||
| Estimation Notes and Assumptions: | There are multiple potential designs for setting fixed ordering of items:
Alternative 1: * Add ordering field to item record in back-end * When moving item to a new position, potentially all items in the list have to be updated - one by one - in the back-end with their new positions Variation: A new API is created that performs the multiple item updates behind the scenes in mod-inventory Alternative 2: * a new back-end structure is created that holds the ordering of items outside of the items themselves |
||||||||||||||||||||
| Development Team: | Folijet | ||||||||||||||||||||
| Kiwi Planning Points (DO NOT CHANGE): | 27 | ||||||||||||||||||||
| PO Rank: | 58 | ||||||||||||||||||||
| PO Ranking Note: | CW: PO rank aligned with Calculated Total rank. | ||||||||||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R5 | ||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R2 | ||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R1 | ||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R1 | ||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R2 | ||||||||||||||||||||
| Rank: FLO (MVP Sum 2020): | R4 | ||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R4 | ||||||||||||||||||||
| Rank: hbz (TBD): | R4 | ||||||||||||||||||||
| Rank: Hungary (MVP End 2020): | R1 | ||||||||||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R2 | ||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R2 | ||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R2 | ||||||||||||||||||||
| Description |
|
Implement new functionality in Holdings/Item records: the ability to manually reorder Items and the ability to save any specific order of items. Background: Item records currently display in a default order determined by barcode. As a library staff member I want to be able to change and save this default order. For example, we receive a serial publication out of order. The item for volume 10 is created before the item for volume 9, thus the barcode number is smaller and 10 displays before 9. I want to save them displayed in numeric order. This changed/saved order also should be able to be communicated to other systems, e.g., discovery, reporting
Out of scope: automatic re-sorting of item records, changes to current temporary sort options
One possible UI solution would be similar to how we move holdings/items between instances. Slide deck: https://docs.google.com/presentation/d/1rD_5nGoo_jxBX-ACgNTGszl__3LiNUnbWN4FEShTIgU/edit#slide=id.p Notes: |
| Comments |
| Comment by Ann-Marie Breaux (Inactive) [ 25/Apr/19 ] |
|
Charlotte Whitt This seems like a really basic requirement, and I'm surprised it's not ranked as go live by more libraries. For any holdings with lots of item records (say a large run of bound journals with hundreds of item records), it seems critical to have those item records stay in a predictable order (by volume number or copy number ) instead of jumping around or being random-looking. |
| Comment by Charlotte Whitt [ 25/Apr/19 ] |
|
Hi Ann-Marie Breaux - I totally agree! CC: Cate Boerema |
| Comment by Cate Boerema (Inactive) [ 26/Apr/19 ] |
|
Maybe I am misunderstanding this feature. It seems like Ann-Marie Breaux is saying this is just about having items automatically display in some kind of sensible order based on existing data while the description (to me) suggests the addition of a new order field that can be edited by users (directly, via drag and drop or similar) to create a custom order for items. Which is it? Ann-Marie, you mention volume or copy number could be the ordering data but those data elements are not even displaying in the item table? |
| Comment by Kristin Martin [ 02/May/19 ] |
|
The sequencing of items should be by enumeration by default. We should not have to order the items manually. |
| Comment by Erin Nettifee [ 10/May/19 ] |
|
How does this relate to the proposed UX redesign in https://folio-org.atlassian.net/browse/UXPROD-491 slated for Q3? Duke is very interested in overhauling the UX, but would like to know if this is being done in addition to the UX redesign or in replacement? |
| Comment by Charlotte Whitt [ 13/May/19 ] |
|
Hi Erin Nettifee - the
This is about a way to set/define the order of the item records. And not just rely on the order, they are being associated to the holdings record while creating item records. |
| Comment by Cate Boerema (Inactive) [ 19/Mar/20 ] |
|
Charlotte Whitt how can this be analysis complete if there are no user stories? Putting back to Draft for now. |
| Comment by lew235 [ 12/Jul/23 ] |
|
same solution should be implemented for both items and holdings |
| Comment by Raegan Wiechert [ 19/Jul/23 ] |
|
I always liked how this was dealt with in Millennium/Sierra. The records could be re-ordered by column at will without affecting the permanent sort order. If you did want to preserve the order, there was a "Preserve Sort Order" option in one of the menus. This overrode the default system sort order and would not change unless someone picked the Preserve Sort Option again. There was also a move option that let you move one line/record at a time. This was handy for those outlier cases when you just couldn't get the computer to do the sort order you wanted or when you added a new item when there was already a large number of records with a complicated sorting. The default sort order may be something that needs to be set at the tenant level. Somewhere it was mentioned that the default should be the enumeration field, but that is not a field that we use at all, so we would prefer volume. |
| Comment by lew235 [ 19/Jul/23 ] |
|
Raegan Wiechert I like the idea of the default sort order continuing to be whatever it is currently (I thought it was UUID/hrid but Zak thinks it's barcode). Of course, configurable at the tenant level would be nice eventually. |
| Comment by Lynne Fors [ 20/Jul/23 ] |
|
I liked how Alma dealt with item records. They were sorted by volume/enumeration/chronology/year (all separate data elements) first and then by copy numbers (if used) and finally by barcode. Having migrated to Folio from Millennium, I am also fine with the functionality that Raegan described. |
| Comment by Ann-Marie Breaux (Inactive) [ 10/Aug/23 ] |
|
I think that the most recent time an item was edited may also play into the sort order. I was looking at one of the holdings that has thousands of items linked to it. I made a change to one item that was about 850ish in the list, and when I re-displayed the instance, it had moved to be the first item in the list. I just was making a change in Jira to add a value into a dropdown list, and they have an interesting way of handling it - not sure how useable it would be for thousands of items, but it works well for one page worth. You can either move them up and down by arrows, or by specifying the row number that you want. Of course, click and drag is also nice. Seems like click and drag, plus the "Preserve sort order" that Raegan Wiechert described would be pretty good. |
| Comment by Ann-Marie Breaux (Inactive) [ 06/Dec/23 ] |
|
Moved from Prokopovych backlog to Folijet Backlog cc: Ryan Taylor |