Uploaded image for project: 'ui-inn-reach'
  1. ui-inn-reach
  2. UIINREACH-23

Record Contribution Settings: Configure MARC Transformation Settings (eg. replace Instance HRID in MARC 001 with OCLC number, exclude Fields/Subfields)

    XMLWordPrintable

Details

    • Volaris Sprint 120
    • 13
    • Volaris

    Description

      Purpose:

      Provide an interface to configure MARC transformation for contributed bibliographic records.

      User story statement(s):

      As a local server administrator, I want to configure how the MARC 001 field on contributed records is populated, so that records from the local server will be matched properly against existing records on the central server, and indicate which fields/subfields should also be excluded from the transformed MARC records.

      Scenarios:

      1. Scenario:
        • Given the Record Contribution settings group in INN-Reach settings
        • When the user selects "Bib Transformation"
        • Then a pane with a pull down to select a central server to configure the setting for is presented to the user with an inactive "Save & close" button
      2. Scenario:
        • Given no existing "Bib Transformation" configuration exists for the selected central server
        • When the user selects the central server
        • Then an empty configuration form is presented with the following fields:
          • Customize transformation of contributed MARC records (checkbox, required, if not set, no other fields are active, default: unchecked)
          • An ordered list of identifier options (one option by default with "+" and "delete" options to manage additional options)
            • Instance identifier type to use (required if previous field is checked, single select field populated with configured identifier types from Inventory settings)
            • Strip prefix from identifier (optional, checkbox)
            • Prefixes to ignore (optional, comma-separated list of prefix strings, identifiers with these prefixes will be ignored)
          • A comma-separated list of MARC fields/subfields to exclude from transformed MARC records
      3. Scenario:
        • Given there is an existing "Bib Transformation" configuration for the central server
        • When the user select the central server
        • Then the form described in scenario 2 is populated based on that configuration
      4. Scenario:
        • Given that the user is creating a new configuration
        • When the "Customize transformation of contributed MARC records" is checked and at least one identifier is entered
        • Then the "Save & close" button becomes active
      5. Scenario:
        • Given that the user is modifying an existing configuration
        • If the configured fields are modified
        • Then the "Save & close" button becomes active
      6. Scenario:
        • Given a "dirty" create or edit form
        • When the user attempts to navigate away from the form
        • Then an "are you sure" dialog is presented with options to "keep editing" and "close without saving"
      7. Scenario:
        • Given the "are you sure" modal
        • When the user clicks "keep editing"
        • Then they are returned to the in-progress form
      8. Scenario:
        • Given the "are you sure" modal
        • When the user clicks "close without saving"
        • Then they are navigate to their selected destination and all changes to the form are lost.
      9. Scenario:
        • Given an active "Save & close" button
        • When the user clicks "Save & close"
        • Then an attempt is made to save the form
      10. Scenario:
        • Given the previous scenario
        • When the values entered in the form are valid
        • Then the configuration is created or updated and a success toast is presented
      11. Scenario:
        • Given an attempt to save the form
        • When the data entered in the form is not successfully saved
        • Then an error response is returned by the backend and a failure toast is presented and the user is returned to the form with validation errors

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                Dmytro_Melnyshyn Dmytro Melnyshyn
                brookstravis Brooks Travis
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases