Uploaded image for project: 'mod-data-import'
  1. mod-data-import
  2. MODDATAIMP-744

SPIKE: Design approach for differentiating incoming MARC Bibs that should/shouldn't be saved in SRS

    XMLWordPrintable

Details

    • Folijet Sprint 165, Folijet Sprint 166, Folijet Sprint 167, Folijet Sprint 169, Folijet Sprint 170
    • 8
    • Folijet
    • Poppy (R2 2023)

    Description

      Problem definition:

      We don’t have an explicit action to save the SRS MARC record, it is implicit and happens (almost… we already have a couple of exceptional cases, which were added later as “bug fixes”) for each incoming file. When it was designed we thought of an incoming file as a new and valid record that should be saved prior to any other actions and serve as a single source of truth. In fact, what we have now - there are indeed records that are coming and should be saved in SRS and referenced by other entities that are derived from it. However, there are also multiple use cases (usually some kind of updates or creates on Holdings and/or Item), where incoming MARC record is considered to be disposable, it might contain only partial data, and if we save it we end up either with lost data (when original record is overridden) or with messed up links to corresponding inventory entities (when we save the record as new one)

       

      Notes:

      • Consider making Create/Update SRS MARC Bib explicit - a separate step in the profile
      • Alternatively some kind of a check box should be added when profile is constructed specifying whether MARC Bib is supposed to be saved or not
      • Maybe initial saving of incoming MARC Bibs is not necessary, it should be a part of Create Instance (or maybe other scenarios). Might help in eliminating (at least partially) post-processing logic for Instance creation - all ids will be generated and assigned, 001, 003 and 035 handling will have to move to mod-inventory
      • Need to clarify the situation with DI logs - if we do not save the incoming MARC Bib, we won't be able to display the MARC json

       

      TestRail: Results

        Attachments

          Issue Links

            defines

            New Feature - New feature requests UXPROD-3932 NFR: Folijet - Poppy - RCA I&A

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            improves

            Bug - A problem which impairs or prevents the functions of the product. MODSOURMAN-819 The status of Instance is Multiple in the Import log after uploading MARC file for update

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. MODSOURMAN-891 SRS MARC Created when No Create Instance Action in Job Profile

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. MODSOURMAN-907 The '2' number of Instance is displayed in cell in the row with the 'Updated' row header at the individual import job's log

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            is duplicated by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODDATAIMP-746 SPIKE: Design approach to remove post-processing step when Instance is created

            • TBD - To be determined
            • Closed
            relates to

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODSOURMAN-1021 Provide endpoint for getting parsed content for DI log

            • P2 - normal priority level, must be included in the current development cycle
            • Draft

            Bug - A problem which impairs or prevents the functions of the product. MODDATAIMP-710 Adding MARC modifications to imports with update actions creates broken records

            • P2 - normal priority level, must be included in the current development cycle
            • Blocked

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINV-849 Move 001+003->035 logic to inventory

            • P2 - normal priority level, must be included in the current development cycle
            • Draft

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINV-850 Save SRS MARC by an HTTP request from Inventory

            • P2 - normal priority level, must be included in the current development cycle
            • Draft

            Task - A task that needs to be done. MODSOURCE-299 Change record version mechanism if match discarded.

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Open

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODSOURCE-672 Remove step of initial saving of incoming records to SRS

            • P2 - normal priority level, must be included in the current development cycle
            • Draft

            Bug - A problem which impairs or prevents the functions of the product. MODSOURMAN-819 The status of Instance is Multiple in the Import log after uploading MARC file for update

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. MODSOURMAN-891 SRS MARC Created when No Create Instance Action in Job Profile

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. MODSOURMAN-907 The '2' number of Instance is displayed in cell in the row with the 'Updated' row header at the individual import job's log

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODSOURMAN-1020 Add table to save incoming records for DI logs

            • P2 - normal priority level, must be included in the current development cycle
            • Open

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODSOURMAN-1022 Remove step of initial saving of incoming records to SRS

            • P2 - normal priority level, must be included in the current development cycle
            • Open

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODSOURMAN-1023 Rename event DI_SRS_MARC_BIB_RECORD_CREATED

            • P2 - normal priority level, must be included in the current development cycle
            • Draft

            New Feature - New feature requests UXPROD-4471 Remove step of initial saving of incoming records to SRS

            • P2 - normal priority level, must be included in the current development cycle
            • Open
            mentioned in

            Page Loading...

            Page Loading...

            Page Loading...

            Activity

              People

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

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases