Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-2661

Load MARC records to create/update various record types, but do not store MARC

    XMLWordPrintable

    Details

    • Template:
      UXPROD features
    • Potential Workaround:
      Use the Q3 2020 functionality of only updating specific fields in the SRS MARC, instead of updating all fields
    • Front End Estimate:
      Small < 3 days
    • Development Team:
      Folijet
    • Calculated Total Rank:
      36
    • Kiwi Planning Points (DO NOT CHANGE):
      2
    • PO Rank:
      75
    • Rank: Chalmers (Impl Aut 2019):
      R5
    • Rank: Chicago (MVP Sum 2020):
      R1
    • Rank: Cornell (Full Sum 2021):
      R4
    • Rank: Duke (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R3
    • Rank: FLO (MVP Sum 2020):
      R4
    • Rank: GBV (MVP Sum 2020):
      R4
    • Rank: Grand Valley (Full Sum 2021):
      R4
    • Rank: MO State (MVP June 2020):
      R3
    • Rank: TAMU (MVP Jan 2021):
      R3
    • Rank: U of AL (MVP Oct 2020):
      R3

      Description

      Split from UXPROD-2338 to decrease scope; partial workaround: use new option to only update specific MARC fields in SRS

      Purpose: To import data for Inventory or Acquisitions via a MARC record, but then do not save the MARC record in SRS

      Sample use cases:

      • MARC Bib or Holdings creates related inventory record, but library does not want SRS (so Inventory Source = FOLIO, not MARC)
      • Brief MARC Bib supplies order or invoice data, but should not overlay a richer MARC SRS record

      As a staff person working with imported files
      I want to be able to specify whether an incoming MARC record should be saved in SRS or not
      So that I can discard MARC records that are used for transport purposes only

      From 9/23/20 Folijet grooming mtg:

      • In SRS, when try to use update or modify action in job profile; imported records saved in SRS, but no link to instance or original record
        • Job 1: modify, then create instance – all is fine
        • Job 2: Match MARC-MARC (so there is already an SRS), then update MARC – incoming record just has a few fields harvested to update the existing MARC, but does not have any links to an Instance; does it make sense to save to SRS?
        • Should we make explicit that the incoming record is saved or not?
        • Incoming record should not be linked to the instance
        • That’s how it’s working now
        • Revisit when we implement “Do not save MARC”

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                abreaux Ann-Marie Breaux
                Reporter:
                abreaux Ann-Marie Breaux
                Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases