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

Theme: Ability to maintain relationships between other apps when holdings/items are moved

    XMLWordPrintable

Details

    • Very Small (VS) < 1day
    • Very Small (VS) < 1day
    • Low
    • Hide
      There may not be any work needed to retain the relation to Orders, ref the comment on this issue:

      "Orders relate to the Inventory Item by this property on the Item

      {code}
       "purchaseOrderLineIdentifier": {
            "type": "string",
            "description": "ID referencing a remote purchase order object related to this item"
          },
      {code}

      The Item in turn relates to a holdings record by an holdingsRecordId on the Item.

      Moving the Item to a different holdings record is basically changing the ID - Orders' relation to the Item will be retained in that process and thus move along to the new holdings record with the Item."
      Show
      There may not be any work needed to retain the relation to Orders, ref the comment on this issue: "Orders relate to the Inventory Item by this property on the Item {code}  "purchaseOrderLineIdentifier": {       "type": "string",       "description": "ID referencing a remote purchase order object related to this item"     }, {code} The Item in turn relates to a holdings record by an holdingsRecordId on the Item. Moving the Item to a different holdings record is basically changing the ID - Orders' relation to the Item will be retained in that process and thus move along to the new holdings record with the Item."
    • Prokopovych
    • 144
    • 111
    • CW: Aligned PO rank with Calculated Total rank
    • R2
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1

    Description

      Purpose: When transferring holdings and items any existing relationships should be retained - https://docs.google.com/document/d/16iF5VxRPNVeVE7CVaLi8I9WYpz6RnYzE6iLUPvOCUA4/edit#heading=h.v4stg3pbhaa3

      Usecases:
      1) There is established relationship between a POL in the Order app, and a given holdings record via app interaction Order <>Inventory.
      2) There is established relationship between a POL in the Order app, and a given item record via app interaction Order <>Inventory.
      3) There is established relationship between a patron request and an item record in a holdings record. If the Item record is transferred to another holdings record, the Request link to the given item record must be retained.
      4) Loans on a given item record is to retained, so the loan history is persistent (to be described further - ecboettcher
      5) ....

      • - - - - - - - - - - - - -

      Usecases:
      1) Holding, subscription, and item records move together. In all situations, when an item record is moved, the associated holding and subscription record should automatically follow so that there are no empty record lingering that could be accidentally found by a patron.

      2) UXPROD-2268 addresses - guidance for this question from fhemme: Do you know how a transfer of holdings from one instance to another would work, if the change is triggered outside of Folio? Something to keep in mind with regards to UUID or HRID?

      The jira feature was also mentioned in:
      Gap Analysis 2019 Missing Features - https://docs.google.com/spreadsheets/d/1b3VY1EUOAyoySuEaT0lJfKUBYLMUPZM6PDSBnGiMxYk/edit#gid=739330010

      Original order # 145

      TestRail: Results

        Attachments

          Issue Links

            has to be done after

            New Feature - New feature requests UXPROD-137 Move Holdings and/or Items

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODORDERS-642 Data corruption. When holding/item data are moved in Inventory, then the connected Order lines are not updated accordingly

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UICR-125 Data corruption. When holding/item data are moved in Inventory, then the item in Courses is not updated accordingly

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIREQ-589 [BE] Data corruption. When holding/item data are moved in Inventory, then the connected Request is not updated accordingly

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIU-2082 [BE] Data corruption. When holdings/item data are moved in Inventory, then the connected Fee/Fine is not updated accordingly

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

            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

            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-3342 Implement data consistency approach for Piece<>Item interaction

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

            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

            New Feature - New feature requests UXPROD-3399 When Relevant User Record Attributes are Updated, Synchronize Those Updates with the User's Requests Automatically

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

            New Feature - New feature requests UXPROD-3664 Future Fees/Fines: Add Loan Type and Patron Group to the fee/fine record

            • TBD - To be determined
            • Draft

            New Feature - New feature requests UXPROD-3879 Implement data consistency approach for Item<>Piece interaction

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

            Page Loading...

            Page Loading...

            Page Loading...

            Activity

              People

                charlotte Charlotte Whitt
                charlotte Charlotte Whitt
                Charlotte Whitt Charlotte Whitt
                Votes:
                0 Vote for this issue
                Watchers:
                23 Start watching this issue

                Dates

                  Created:
                  Updated:

                  TestRail: Runs

                    TestRail: Cases