Uploaded image for project: 'ui-data-import'
  1. ui-data-import
  2. UIDATIMP-630

Refine identifier matching for Instances

    XMLWordPrintable

    Details

    • Template:
      Folijet UI story template
    • Sprint:
      Folijet Sprint 98
    • Story Points:
      5
    • Development Team:
      Folijet
    • Affected Institution:
      Lehigh, University of Chicago

      Description

      Purpose: Data import users need to be able to match on a wide variety of identifiers in the Instance record. The current matching setup (Identifier and Identifier type as 2 separate matches) is cumbersome and may not work

      As a staff person working with data import
      I want to be able to match an identifying number from any MARC field to a particular identifier type number in an Instance (e.g. only match against OCLC number)
      So that I can narrow down my matches more precisely

      Scenarios

      1. Scenario 1
        • Given the matching profile create/edit screen for Existing Instance record
        • When viewing the dropdown options for the Identifier
        • Then replace the current options of
          • Identifier: Identifier type
          • Identifier: Identifier
        • With options that represent each of the identifier types from Settings/Inventory/Resource identifier type (which will vary per tenant)
        • In the form of Identifier: [resource identifier type name], e.g. Identifier: ASIN
      2. Scenario 2
        • Given the matching profile view screen for Existing Instance record
        • When a user has selected one of the identifiers for the existing instance record field
        • Then display as Identifier: [resource identifier type name], e.g. Identifier: ASIN
      3. Scenario 3 test this scenario after backend is done
        • Given the matching profile for Existing Instance record
        • When a user selects an identifier as the Existing instance record field
        • Then use both the identifier type and the identifier itself to attempt the match to the Instance record
      4. Scenario 4
        • Ensure this story passes Accessibility testing
      5. Scenario 5
        • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

      See attached screenshots

      NOTE: Scenario 3 requires a backend story

      • From Magda: The challenge with the relationship type is that it has to be embedded not appended: see MDEXP-229
      • Per Folijet, needs convo between UI and backend, probably a couple MOD magic stories (create or change existing schema for backend, or some kind of contract between BE and UI for how to notify about composite fields; MODINV story to change data loader to support that kind of query; may be some complexity for UI on building some fields from field names/values)
      • Should be do-able per Oleksii

        TestRail: Results

          Attachments

          1. Instance identifier matching - Current.PNG
            76 kB
            Ann-Marie Breaux
          2. Instance identifier matching - New.PNG
            91 kB
            Ann-Marie Breaux
          3. scratch.json5
            2 kB
            Oleksii Kuzminov

            Issue Links

              Activity

                People

                Assignee:
                Mariia_Aloshyna Mariia Aloshyna
                Reporter:
                abreaux Ann-Marie Breaux
                Votes:
                1 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases