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

Create Holding Record in inventory for items ordered that are not currently represented in inventory by a Holding

    XMLWordPrintable

Details

    • Small < 3 days
    • Low
    • Medium < 5 days
    • Will need to collaborate with inventory team
    • Thunderjet
    • R5
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1

    Description

      "Purpose: Need a record in inventory in order to understand what we own, do not own, have on order, need to order more of...

      High-Level Requirements:
      One Holding needs to be created in inventory per Location identified in the order record.
      This is a link to the document that maps order data fileds to holding data fields. https://docs.google.com/spreadsheets/d/1kdYx63J0KoqR3-LUHuPAzERgj8WE0OQ08rzuCaJaHWs/edit#gid=952741439"

      TestRail: Results

        Attachments

          Issue Links

            relates to

            Umbrella - FOLIO-1273 Define and describe the architecture for seamless push and pull of data between apps (interaction)

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

            Umbrella - FOLIO-1331 Define and describe the architecture for how to keep data in sync across multiple apps

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINVSTOR-279 Add an electronic location & service point to the sample data in folio-testing, -snapshot, and -snapshot-stable

            • 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. MODORDERS-66 Create Holding Record in inventory for titles ordered that are not currently represented in inventory by a Holding

            • 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-121 PO Line: add "Locations" accordion and associated fields

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

            New Feature - New feature requests UXPROD-1105 Create Container record in inventory from PO Line

            • P4 - lowest priority level, nice-to have things that require future discussion and design
            • Blocked

            Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. UXPROD-1151 Creating and Updating Records in inventory when creating NEW Orders

            • 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. MODGOBI-48 make location repeatable

            • 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-237 Holdings Record. Accordion Acquisition. Implement new elements and reorder data (long term)

            • P4 - lowest priority level, nice-to have things that require future discussion and design
            • Draft

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-268 Create Brief Instance records when items are acquired (can be deprecated?)

            • 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-379 Holdings record. Receipt status values are received from the Acquisition module.

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-451 Holdings Record. Accordion Acquisition. Data to be received from the Acquisition module

            • P4 - lowest priority level, nice-to have things that require future discussion and design
            • Open

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-455 Holdings record. Receipt status. Value received from the Acquisition module

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

            New Feature - New feature requests UXPROD-143 Creation of metadata records when items are acquired

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

            Activity

              People

                dennisbridges Dennis Bridges
                dennisbridges Dennis Bridges
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases