Inventory (UXPROD-785)

[UXPROD-1925] Holdings: Display of POL number, Order status, Order date and Price in the Acquisition accordion Created: 01/Aug/19  Updated: 29/Sep/22  Resolved: 25/Nov/21

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Kiwi (R3 2021)
Parent: Inventory

Type: New Feature Priority: P2
Reporter: Charlotte Whitt Assignee: Dennis Bridges
Resolution: Done Votes: 0
Labels: acq-dev-grooming, inventory, metadatamanagement, po-mvp, r1-2021-at-risk, round_iv, short_term_solution
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Screenshot 2020-10-22 at 11.22.04.png    
Issue links:
Blocks
blocks UXPROD-2897 Extend RM Order Cluster with Holdings... Open
Defines
is defined by MODORDERS-672 Holdings related to package POLs are ... Closed
is defined by UIIN-1995 Instances linked to package order lin... Closed
is defined by MODORDERS-434 Extra items and holdings are created,... Closed
is defined by MODORDERS-455 Editing location and increase quantit... Closed
is defined by MODORDERS-460 Define and implement business API for... Closed
is defined by MODORDERS-493 Update open order logic with holding ... Closed
is defined by MODORDERS-500 Validate location element which shoul... Closed
is defined by MODORDERS-502 When reopening order system forces us... Closed
is defined by MODORDERS-507 Update UnOpen order logic with holdin... Closed
is defined by MODORDERS-508 Update Close order logic with holding... Closed
is defined by MODORDERS-509 Update ReOpen order logic with holdin... Closed
is defined by MODORDERS-510 Merge branch feature/UXPROD-1925 into... Closed
is defined by MODORDERS-511 Do not allow changing the quantity or... Closed
is defined by MODORDERS-538 Update quantity of the Location in th... Closed
is defined by MODORDSTOR-200 Define "inventory order summary" mode... Closed
is defined by MODORDSTOR-224 Create cross-module migration script ... Closed
is defined by UIIN-574 Holdings record. New elements. POL nu... Closed
is defined by UIIN-1223 Update "Expected" piece locations whe... Closed
is defined by UIOR-609 Can remove but can not edit location ... Closed
is defined by UIOR-724 Allow user to select holding rather t... Closed
is defined by UIOR-726 Restrict editing order location and q... Closed
is defined by UIOR-736 Merge UXPROD-1925 stories Closed
is defined by UIOR-781 Location (holding) field adjustments ... Closed
is defined by UIREC-132 Allow user to adjust order quantity a... Closed
Gantt End to Start
has to be done before UXPROD-2373 Allow for the display of piece inform... Closed
has to be done before UXPROD-185 Import Orders in MARC format Closed
has to be done before UXPROD-3361 Prep for Importing Orders in MARC format Closed
has to be done before UXPROD-1607 Refined Display of Acquisition data i... Analysis Complete
Relates
relates to UIDATIMP-820 Remove Acquisitions accordion from th... Closed
relates to UXPROD-1995 Item: Display of POL number, Order st... Closed
relates to UXPROD-3344 Instance: Display and populate the Ac... Closed
Requires
is required by MODDATAIMP-399 SPIKE: Allow POL or Vendor Ref Number... Closed
Epic Link: Inventory
Analysis Estimator: Charlotte Whitt
Front End Estimate: Small < 3 days
Front End Estimator: Aliaksei Chumakou
Front-End Confidence factor: Medium
Back End Estimate: Large < 10 days
Back End Estimator: Andrei Makaranka
Development Team: Thunderjet
PO Rank: 75.89
PO Ranking Note: CW: Created after ranking exercise. The solution with a minimum data set has been discussed with a MM-SIG working group and AM-Breaux.
DB: Since I have taken responsibility for this feature I have adjusted ranking to fit with my other feature rankings.
Cap Plan Fix Version (DO NOT CHANGE): R2 2021
Rank: Chalmers (Impl Aut 2019): R2
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R2
Rank: GBV (MVP Sum 2020): R4
Rank: Grand Valley (Full Sum 2021): R5
Rank: hbz (TBD): R4
Rank: Lehigh (MVP Summer 2020): R2
Rank: MO State (MVP June 2020): R3
Rank: TAMU (MVP Jan 2021): R4
Rank: U of AL (MVP Oct 2020): R2

 Description   

Overview: For the mvp we implement the POL number in the Acquisition accordion. The POL number is a hotlink directly back to the Order record.

Usecase:
As a circulation staff I want to have easy access to order information relevant for any given search in Inventory.
When I find what I'm looking for - the given patron request - then I want to have easy access coming from the Inventory, holdings record and do not want to repeat my search in another app, e.g. the the Order app.

UX-wireframe for the simple implementation with the POL number as hotlink directly back to the Order record, and two elements more: the Order status, Order status date, and Price.

The long term solution, would be to implement a fuller set or data elements - but that will be beyond mvp - UXPROD-1607 Analysis Complete .

NOTE: This does not affect the Receiving accordion in the Holdings record, only the Acquisitions accordion

Other issues to be confirmed for final stories

  • Will this acquisitions data be referred data from the order, or stored in the Holdings record? If it is view-only data in the Holdings record, then
    • UIIN story needed to remove this acquisitions accordion from the Holdings Create/Edit screen
    • Maybe MODINV story needed to remove the acq data from the Holdings schema
    • Migration script needed if any data has been manually populated into those Holding records fields previously?
    • UIDATIMP story needed to remove the acquisitions accordion from the Holdings field mapping profile create/edit and View screens, or change to Unmappable
    • MODDATAIMP needs review to see if schema changes are needed, and any migration scripts
  • Is additional data needed beyond the original 4? Current UI does not show the POL number. Doublecheck with the Acq Small Group


 Comments   
Comment by Charlotte Whitt [ 03/Jun/20 ]

This is critical for uChicago (round_iv) - https://folio-org.atlassian.net/wiki/display/COHORT2019/Round+IV+-+Post+MVP

Comment by Holly Mistlebauer [ 17/Jun/20 ]

Chicago comment from Round IV Outliers spreadsheet: We felt like there was too much risk for people not to know whether an inventory record was attached to a PO. UXPROD-1925 Closed + UXPROD-1990 Closed together provide a workaround for UXPROD-1607 Analysis Complete , which is the "real" feature that we down-ranked. -Tod Olson

Comment by Cate Boerema (Inactive) [ 09/Oct/20 ]

Dennis Bridges, Charlotte Whitt and I wanted to get your thoughts on which team should do the work on this feature (Thunderjet vs CF vs both). What do you think?

CC: Marc Johnson

Comment by Charlotte Whitt [ 05/Nov/20 ]

Notes from Slack #product-owners:

Charlotte Whitt: Today at 1:33 PM
@cate - in the Iris dashboard I'm missing UXPROD-1925 Closed and UXPROD-1995 Closed which @Dennis Bridges and his team were planning to pick up

Cate Boerema: 7 hours ago
I hadn't heard that those were being prioritized for R1. Maybe I missed a conversation?

Charlotte Whitt: 4 hours ago
Has been discussed at several RM-SIG meetings. See also: https://folio-org.atlassian.net/wiki/display/COHORT2019/Round+IV+-+Post+MVP (uChicago's list).

Dennis Bridges: 3 hours ago
@cate is correct, this was NOT actually scheduled for R1. We determined these had a lot of crossover with UXPROD-2373 Closed and that they should be implemented together. Unfortunately Thunderjet dose not have capacity in R1.

Comment by Marie Widigson [ 11/Nov/20 ]

Is there a reason why this is not planned for instance level? It would be even more convenient not to have to open each holdings record.

Comment by Sharon Beltaine [ 12/Nov/20 ]

Reporting SIG: For reporting, we would like the POL to link to holdings and items in particular (this is not important to us for display, we just need the data element link). Having this link enables us to have reports that link the PO with a specific holding or item. Having holdings and items links is important for summarizing costs at the order level. The thin thread implementation of this data element is fine for reporting.

Comment by Cate Boerema (Inactive) [ 16/Nov/20 ]

Dennis Bridges, could you please have Thunderjet revisit the estimates on this feature? The estimates showing here were done by Niels Erik eons ago.

Comment by Andrei Makaranka [ 18/Nov/20 ]

Dennis Bridges, Cate Boerema
Back-end work is needed here :
1. Define model, which will be retrieved on UI (1SP)
2. Define and implement API (3SP)

Thanks

Comment by Charlotte Whitt [ 19/Jan/21 ]

Hi Holly Mistlebauer Dennis Bridges - getting this work done is often mentioned by the SMEs. Are their any change that this work can be picket up either by Dennis' team or Core Functional team for R1 2021 with the extended deadline?

CC: Kristin Martin lew235 Mike Gorrell

Comment by Ann-Marie Breaux (Inactive) [ 27/Jan/21 ]

Hi Charlotte Whitt and Dennis Bridges Just trying to understand the Data Import field mapping implications. As far as I can tell, all of this will be drawn from the associated POLs automatically. Is that right? Will it only work if the holdings is created as part of the Order process? If the holdings is created as part of the Data Import process, would there be an opportunity to associate with the relevant POL manually somehow? (or via the Data Import process)

Right now, this is just a blank accordion in the Data Import field mapping screen for the Holdings record.

Let me know if we should have a quick meeting to discuss. Thank you!

Comment by Dennis Bridges [ 27/Jan/21 ]

Ann-Marie Breaux Regardless of how the Holding is created the orders app should be doing a FINDorCreate and establishing a reference. how the reference is established and where is still not set in stone, but likely this will mean storing the Holding UUID in the order. Fro that point on when a Holding is displayed in the inventory UI it would retrieve information from orders by requesting information related to its UUID. The orders app would control what is given and inventory would display everything it can.

IF we implement this way the import app could potentially create Holdings and add the UUID when creating the order, this way it would be certain that the correct holding was used. I don't know that this would be necessary. However, it should be consistent with how you facilitate the Instance<>POL linking and Piece<>Item linking.

Comment by Ann-Marie Breaux (Inactive) [ 18/Feb/21 ]

Thanks for the additional info Dennis Bridges. This is definitely going to be required for UXPROD-185 Closed (which is Juniper for Folijet) and UXPROD-191

Comment by Charlotte Whitt [ 18/Feb/21 ]

Holly Mistlebauer - Input for our R2 2021 conversation and prioritization of work.

As you can see in the comments above, then UXPROD-185 Closed (scheduled for Juniper for Folijet) requires the work planned for UXPROD-1925 Closed to be done. We would therefor need to look at this work ( UXPROD-1925 Closed , UXPROD-185 Closed , and UXPROD-191) as a theme, and make sure that we have the necessary work in Inventory ready, before the depending features can get started. 

Comment by Holly Mistlebauer [ 19/Feb/21 ]

Dennis Bridges:  Hi!  This feature needs to be completed early in the Juniper development cycle because it is required for UXPROD-185 Closed , also scheduled for Juniper.   Will Thunderjet be able to complete this as needed?   Thanks...

Comment by Dennis Bridges [ 19/Feb/21 ]

Thanks Holly Mistlebauer I have adjusted the PO rank accordingly.

Comment by Lisa McColl [ 22/Apr/21 ]

Is there any provision here or elsewhere that if someone tries to delete a holding with a related POL there is a warning message alerting the user of the relationship that is about to be broken? 

 

Comment by Dennis Bridges [ 22/Apr/21 ]

Lisa McColl There is nothing in scope of this feature for making a check on delete of holding from the inventory app. This type of interaction is a hotly debated topic at the moment. However, the order app will need some way of handling situations where our link no longer resolves. Ie. give a user the ability to choose a new holding.

Ultimately the community needs to settle on an approach for managing these types of situation at a system level such that individual apps can conform to that approach and possibly leverage the global tools provided to do so. I've been away for a few weeks but I believe that even recently more progress has been made on this topic.

Comment by Dennis Bridges [ 10/Jun/21 ]

After confirming with Ann-Marie that the defendant features have been delayed we have decided to push this feature to R3 to allow for completion of the remaining stories and proper testing. There was no logical place to split this work.

Comment by Ann-Marie Breaux (Inactive) [ 04/Aug/21 ]

Hi Dennis Bridges Once this is done, and in general - does the Instance, Holdings, and Item store the related POL number (or its UUID perhaps) in Inventory-Storage, or does it just request that info from the Order app when it creates the view of the Instance/Holdings/Item?

Comment by Dennis Bridges [ 04/Aug/21 ]

Ann-Marie Breaux it just requests the info from the orders app. Basically says give me POLs that have my UUID and then displays the information that is returned. As we currently store the instance and item IDs on the order side the decision was made to keep this consistent for now with Holdings.

Comment by Dennis Bridges [ 25/Nov/21 ]

All issue resolved and verified in bugfest-kiwi

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