MODDATAIMP-508: Updating Instances and Holdings for Films On Demand

Owned by Ann-Marie Breaux (Deactivated)
Last updated: Aug 16, 2021

Determine best way forward for resolving match/update scenario described in MODDATAIMP-508. Ann-Marie Breaux (Deactivated)to review proposed solution with subgroup before dev changes.

Scenario 1: Updates only

  • MARC records previously loaded to create instances and holdings
  • Updated MARC records received that need to update the instances and holdings

Possible job profile structures

Option 1

  • Match: 001 to Instance System control number
    • For matches
      • Update instance
      • Update holdings

Problem with Option 1: No holdings match, so no way to update it

Option 2

  • Match: 001 to Instance System control number
    • Submatch: Static match Text Online Existing value begins with incoming value Holdings Location: Permanent 
      • For matches
        • Update instance
        • Update holdings

Problem with Option 2: Scenario works, except it is confusing (making a match on the holdings and then updating the corresponding instance); short term, this is the best solution

Option 3a

  • Match: 001 to Instance System control number
    • For matches
      • Update instance
  • Match: 001 to Instance System control number
    • Submatch: Static match Text Online Existing value begins with incoming value Holdings Location: Permanent 
      • For matches
        • Update holdings

Problem with Option 3: Cannot create a job profile with different matches/actions under the same match profile; long term, is this the best solution? Per Folijet, should be able to structure a profile this way. A-M to create a separate story for this (not really a dev bug; but a shift in requirements)

Option 3b

  • Match: 001 to Instance System control number 1
    • For matches
      • Update instance
  • Match: 001 to Instance System control number 2 (exact same profile as the first one, but a different name)
    • Submatch: Static match Text Online Existing value begins with incoming value Holdings Location: Permanent 
      • For matches
        • Update holdings

Problem with Option 3: Cannot create a job profile with different matches/actions under the same match profile; long term, is this the best solution? Per Folijet, should be able to structure a profile this way. A-M to create a separate story for this (not really a dev bug; but a shift in requirements)

Option 3c (being used by Jenn)

  • Match: 001 to Instance System control number 1
    • For matches
      • Update instance
  • Match: Static match Text Online Existing value begins with incoming value Holdings Location: Permanent (to get around having the static match being a submatch, create as a regular match, and then update it to a static match)
    • For matches
      • Update holdings

Problem with Option 3: Cannot create a job profile with different matches/actions under the same match profile; This will work if the submatches can be primary level

Option 4

  • Match: 001 to Instance System control number
    • For matches
      • Update instance
      • Submatch: Static match Text Online Existing value begins with incoming value Holdings Location: Permanent 
        • For matches
          • Update holdings

Problem with Option 4: Within a job profile, the user cannot add a match profile under an action profile; long term, is this the best solution? Per Folijet, would be harder to implement than option 3. Since the outcome of option 4 is the same as option 2, then maybe don't go to the extra effort of 4 (yet)

Additional questions:

  • Adding MARC Modifications into the tree
  • Allowing submatches at the primary level

Scenario 2: Creates and Updates

  • MARC records previously loaded to create instances and holdings
  • New file of MARC records received; some should need to update existing instances and holdings; some should create new instances and holdings

Possible job profile structures

Option 1

  • Match: 001 to Instance System control number
    • For matches
      • Update instance
      • Update holdings
    • For non-matches
      • Create instance
      • Create holdings

Problem with Option 1: No holdings match, so no way to update existing holdings; rest of the profile works

Option 2

  • Match: 001 to Instance System control number
    • For matches: Submatch: Static match Text Online Existing value begins with incoming value Holdings Location: Permanent 
      • For matches
        • Update instance
        • Update holdings
    • For non-matches
      • Create instance
      • Create holdings

Problem with Option 2: Scenario works, except it is confusing (making a match on the holdings and then updating the corresponding instance or creating a new instance); short term, this is the best solution

Option 3

  • Match: 001 to Instance System control number
    • For matches
      • Update instance
    • For non-matches
      • Create instance
      • Create holdings
  • Match: 001 to Instance System control number
    • Submatch: Static match Text Online Existing value begins with incoming value Holdings Location: Permanent 
      • For matches
        • Update holdings

Problem with Option 3: Cannot create a job profile with different matches/actions under the same match profile; long term, is this the best solution?

Option 4

  • Match: 001 to Instance System control number
    • For matches
      • Update instance
      • Submatch: Static match Text Online Existing value begins with incoming value Holdings Location: Permanent 
        • For matches
          • Update holdings
    • For non-matches
      • Create instance
      • Create holdings

Problem with Option 4: Within a job profile, the user cannot add a match profile under an action profile; long term, is this the best solution?