Uploaded image for project: 'mod-inventory'
  1. mod-inventory
  2. MODINV-577

Match logic for VRN matches to Inventory records

    XMLWordPrintable

Details

    • Spitfire Sprint 136, Spitfire Sprint 137, Spitfire Sprint 138
    • 3
    • Spitfire
    • Morning Glory R2 2022

    Description

      Purpose: To describe the matching logic invoked when a user selects Vendor reference number (VRN) as the matchpoint from an incoming MARC Bibliographic record to an existing Inventory Instance, Holdings, or Item

      Full description of the feature: https://wiki.folio.org/pages/viewpage.action?pageId=73535666

      When user selects Vendor reference number (VRN) as the matchpoint for Instance, Holdings, and/or Item

      • Retrieve the VRN from the MARC field and subfield designated in the Incoming MARC Bibliographic record field of the match profile -  024$a, 924$a, 935$a, 980$a
      • Use the VRN to check for a matching POL in the Orders app - query mod-orders by VRN to find related POL - GET request to /orders/order-lines?query=vendorDetail.referenceNumbers="/@refNumber=="{VRN}"
      • NOTE: Only check POLs with status of Open, not Pending or Closed (add additional cql filtering)
        • If a single Open POL is found to be associated with the VRN, then check for a related Instance, Holdings, or Item (as designated in the match profile)
          • If a single match is found for Instance, Holdings, or Item, then consider it a match and proceed with the match action(s) described in the Data import Job profile
          • If no match is found for Instance, Holdings, or Item, then consider it a non-match and proceed with the no-match action(s) described in the Data import Job profile
          • If multiple matches are found for Instance, Holdings, or item, then consider it a non-match and proceed with the no-match action(s) described in the Data import Job profile
        • If multiple Open POLs are found to be associated with the VRN, then consider it a non-match and proceed with the no-match action(s) described in the Data Import job profile
        • If multiple matches are found for Instance, Holdings, or item, then consider it a non-match and discard, with multiple matches error message (being planned as part of UXPROD-3502)

      Additional notes

      • Updates to multiple holdings or items from the same incoming MARC Bib not yet accounted for; see UXPROD-2741
      • Follow same implicit logic when updating Instances (e.g. if updating an Instance with source = FOLIO, then also create an SRS MARC Bib and change the Instance's source to MARC
      • Ensure automated unit test coverage for this new code is 80% plus
      • Right now, if the matchpoint in the incoming record is in a repeatable field, FOLIO will only use the data in the first occurrence of that field. Is that OK for now, or do we need to address it? A-M to confirm with SMEs
      • abreaux to add story for wildcard matching

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                viacheslav_kolesnyk Viacheslav Kolesnyk
                Kateryna Senchenko Kateryna Senchenko
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases