Uploaded image for project: 'mod-inventory-storage'
  1. mod-inventory-storage
  2. MODINVSTOR-713

Enable support for optimistic locking (failOnConflict) in instances/holdings/items (part1)

    XMLWordPrintable

Details

    • CP: sprint 112, CP: sprint 113
    • 1
    • Core: Platform
    • R2 2021

    Description

      This is a follow up issue to MODINVSTOR-656 which was completed in R1. Enabling this functionality will require major API changes and client (UI) support so it needs to be coordinated with UIIN-1245.

      This issue is closed as done because we have a branch with the results: MODINVSTOR-713-optimistic-locking-failOnConflict This is part1.

      The work continues with part2 on MODINVSTOR-726.

      TestRail: Results

        Attachments

          Issue Links

            blocks

            Task - A task that needs to be done. CIRC-1152 Release module

            • TBD - To be determined
            • Closed

            Task - A task that needs to be done. MODCXINV-57 Release module

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-1245 Implement optimistic locking in Inventory

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

            New Feature - New feature requests RMB-727 Implement support for optimistic locking

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

            New Feature - New feature requests UXPROD-1752 Prevent update conflicts (via optimistic locking): platform support for detection

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

            New Feature - New feature requests UXPROD-2796 Prevent update conflicts when doing manual edits (User A and User B)

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

            New Feature - New feature requests UXPROD-2797 Prevent update conflicts (1 user and system trying to act on the same record)

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

            New Feature - New feature requests UXPROD-2798 Prevent update conflicts (two automated processes acting on the same record)

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

            New Feature - New feature requests UXPROD-2994 Optimistic Locking: coordinate rollout of "failOnConflict" to selected modules and APIs

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

            New Feature - New feature requests UXPROD-3089 Inventory. Implementing Optimistic Locking

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

            Bug - A problem which impairs or prevents the functions of the product. RMB-832 For optimistic locking fix upsert, implement updateBatch

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

            New Feature - New feature requests MODINVSTOR-726 Enable support for optimistic locking (failOnConflict) in instances/holdings/items (part2)

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

            Task - A task that needs to be done. MODINVSTOR-708 enable 'failOnConflict' for instances/holdings/items interfaces

            • 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. DEBT-1 No optimistic locking/update conflict resolution

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

            Task - A task that needs to be done. FOLIO-2028 SPIKE: how to handle update conflicts?

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

            Task - A task that needs to be done. FOLIO-2442 Name Changes to Existing Reference Records

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

            New Feature - New feature requests MODINV-398 Optimistic locking (_version field, 409 HTTP status code) in instances/holdings/items

            • 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. MODINVSTOR-431 Settings > Inventory > Mode of issuance. Misc. renaming and source update of existing values

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

            Task - A task that needs to be done. RMB-719 SPIKE: design protocol and implementation for optimistic locking

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

            New Feature - New feature requests MODINVSTOR-656 enable "detection-only" OL for instances, holdings and titles

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

            Activity

              People

                julianladisch Julian Ladisch
                jakub Jakub Skoczen
                Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases