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

Disallow holdings types with same name

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • P2
    • Resolution: Done
    • None
    • 17.0.0
    • EPAM-Veg Sprint 22, EPAM-Veg Sprint 23
    • 5
    • Vega

    Description

      Overview:
      When a duplicate term is entered in controlled vocab CRUD component in Settings, the addition fails with a weird server error. This applies in e.g. Settings > Inventory > Holdings, Holdings type, and Settings > Inventory > Instance, Holdings, Item > Call number type and more (basically everywhere this component is used in both Inventory and User settings.

      This story will address fields outlined in the below bug. Additional stories will be created to address other fields.
      Steps to Reproduce:

      • Log into http://folio-snapshot.aws.indexdata.com as diku_admin
      • Go to Settings > Inventory > Holdings, Holdings type, and Settings > Inventory > Instance, Holdings, Item > Call number type
      • Create a new term with the same Name as an existing term

      Expected Results:
      The server will respond with the error code which will be handled on the UI

      Actual Results:
      The server responds with:
      duplicate key value violates unique constraint "loan_type_name_idx_unique": Key (lower(f_unaccent(jsonb ->> 'name'::text)))=(can circulate) already exists.

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                opoch Oleh Pochernin
                Oleksandr_Antonenko Oleksandr
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases