Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-1925

Holdings: Display of POL number, Order status, Order date and Price in the Acquisition accordion

    XMLWordPrintable

Details

    • Small < 3 days
    • Medium
    • Large < 10 days
    • Thunderjet
    • 75.89
    • Hide
      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.
      Show
      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.
    • R2 2021
    • R2
    • R1
    • R4
    • R4
    • R2
    • R4
    • R5
    • R4
    • R2
    • R3
    • R4
    • 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.

      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

      TestRail: Results

        Attachments

          Issue Links

            blocks

            New Feature - New feature requests UXPROD-2897 Extend RM Order Cluster with Holdings and Items

            • TBD - To be determined
            • Open
            has to be done before

            New Feature - New feature requests UXPROD-185 Import Orders in MARC format

            • P2 - normal priority level, must be included in the current development cycle
            • In Review

            New Feature - New feature requests UXPROD-1607 Refined Display of Acquisition data in Holdings and Item records (long term solution)

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Analysis Complete

            New Feature - New feature requests UXPROD-2373 Allow for the display of piece information on Holding records in inventory

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed

            New Feature - New feature requests UXPROD-3361 Prep for Importing Orders in MARC format

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            is defined by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODORDERS-434 Extra items and holdings are created, when location is changed in Open order

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. MODORDERS-455 Editing location and increase quantity at the same time for Open order (Common open flow)

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODORDERS-460 Define and implement business API for retrieving holding summary

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODORDERS-493 Update open order logic with holding ids storing

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODORDERS-500 Validate location element which should contain locationId or holdingId

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. MODORDERS-502 When reopening order system forces user to delete pieces and items

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODORDERS-507 Update UnOpen order logic with holding ids storing

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODORDERS-508 Update Close order logic with holding ids storing

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODORDERS-509 Update ReOpen order logic with holding ids storing

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Task - A task that needs to be done. MODORDERS-510 Merge branch feature/UXPROD-1925 into master

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODORDERS-511 Do not allow changing the quantity or location of the POL, if the order already opened

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODORDERS-538 Update quantity of the Location in the POL if pieces updated/removed

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. MODORDERS-672 Holdings related to package POLs are not displaying Order information in acquisition accordion

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODORDSTOR-200 Define "inventory order summary" model for the acquisition accordion in inventory

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODORDSTOR-224 Create cross-module migration script for Open orders for populating holding ids into order

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-574 Holdings record. New elements. POL number, Order status, Order status date, Price in the Acquisition accordion

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-1223 Update "Expected" piece locations when permanent location is changed in holding

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. UIIN-1995 Instances linked to package order lines are not displaying Order information

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIOR-609 Can remove but can not edit location on Open POL

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIOR-724 Allow user to select holding rather than location at point of order

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIOR-726 Restrict editing order location and quantity on POL

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIOR-736 Merge UXPROD-1925 stories

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIOR-781 Location (holding) field adjustments for None or Instance Create inventory setting

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIREC-132 Allow user to adjust order quantity and location/holdings connection from receiving ui

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            is required by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODDATAIMP-399 SPIKE: Allow POL or Vendor Ref Number match to trigger updates for related Instance, Holdings, Item(s), and SRS MARC

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            relates to

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIDATIMP-820 Remove Acquisitions accordion from the holdings field mapping screen

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests UXPROD-1995 Item: Display of POL number, Order status, Order date and Price in the Acquisition accordion

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests UXPROD-3344 Instance: Display and populate the Acquisitions information accordion with data from the Orders module

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            mentioned in

            Page Loading...

            Page Loading...

            Page Loading...

            Activity

              People

                dennisbridges Dennis Bridges
                charlotte Charlotte Whitt
                Charlotte Whitt Charlotte Whitt
                Aliaksei Chumakou Aliaksei Chumakou
                Andrei Makaranka Andrei Makaranka
                Votes:
                0 Vote for this issue
                Watchers:
                14 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases