Uploaded image for project: 'ui-inventory'
  1. ui-inventory
  2. UIIN-285

Settings > Inventory > Resource type. Unique resource type code

    XMLWordPrintable

Details

    • Vega

    Description

      Overview: When a cataloger, with permission to add new resource types, creates a local folio term for resource type, then both the resource type term and resource type code has to be unique. When trying to add an existing term or existing code to a new resource type term, then an error message has to pop up. First when the new term and it's code both are unique, then the new term can be saved.

      Steps to Reproduce:

      • Log into http://folio-snapshot-stable.aws.indexdata.com/ as diku_admin
      • Go to Settings > Inventory > Instances > Resource types
      • Click the '+New' button to add a new resource type
        • a) Enter "aaa" as resource type term (new) and "crd" (exist) as resource type code. Please note, that the code already exists in the system.
          OR
        • b) Enter "notated music" as resource type term (exist) and "xxx" (new). Please note, that the term already exists in the system.

      Expected Results:
      a) I get an error message: "The code has to be unique. Please enter a different code."
      b) I get an error message: "The term has to be unique. Please enter a different term."
      The new resource type can not be saved until both the term and the code are unique.

      Actual Results:
      Nothing happens. The new resource type can not be saved.

      Additional Information:

      • When implementing a look-up feature, then a list of codes can be presented. This is to be solved later. See: UX-207, UX-208.
      • This scenario also apply to "contributor type" (UIIN-286) and "formats" - separate jira's will follow up on this

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases