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

Connect SRS and quickMARC for MARC Bibs (Folijet work)

    XMLWordPrintable

    Details

    • Template:
    • Epic Link:
    • Front End Estimate:
      Very Small (VS) < 1day
    • Back End Estimate:
      XL < 15 days
    • Estimation Notes and Assumptions:
      Hide
      Should be all backend work; some work in SRS and some work in quickMARC
      Front end: quick check to make sure all is OK when record is created/edited in quickMARC, and will update SRS properly
      Show
      Should be all backend work; some work in SRS and some work in quickMARC Front end: quick check to make sure all is OK when record is created/edited in quickMARC, and will update SRS properly
    • Development Team:
      Folijet
    • Calculated Total Rank:
    • PO Rank:
      120
    • Rank: Cornell (Full Sum 2021):
      R1
    • Rank: Duke (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R1
    • Rank: GBV (MVP Sum 2020):
      R5
    • Rank: hbz (TBD):
      R1
    • Rank: MO State (MVP June 2020):
      R1
    • Rank: TAMU (MVP Jan 2021):
      R1
    • Rank: U of AL (MVP Oct 2020):
      R2

      Description

      This epic is for the Folijet/SRS dev team work; Firebird/quickMARC dev team work is on UXPROD-2272

      Goal is that the the CRUD work done in SMRE will make the appropriate CRUD happen in SRS
      Figure out what work needs to be done by SRS/Folijet and what work needs to be done by Firebird/quickMARC. SRS/Folijet stories go on this feature.

      Requirements:

      1. quickMARC must be able to access an existing SRS MARC Bib via a button in the Instance (e.g. Edit MARC) and edit the MARC Bib.. Once the edits have been made via quickMARC, then
        • The edits are saved to the SRS MARC Bib (including updates to the size of the MARC record in MARC Leader bytes 00-04)
        • and the corresponding updates are made to the MARCcat MARC bib automatically (not at the beginning, only once MARCcat and SRS are integrated)
        • and the corresponding updates are made to the Inventory Instance automatically

      Notes:

      • Current scope for quickMARC would be editing existing SRS Bib records only. Not creating new MARC records from Instances or creating new MARC records from scratch.
      • quickMARC will use a simple UI, rather than a text editor
      • The only expected validation is the general structural validation that SRS currently does. Any more rigorous MARC validation would happen in MARCcat or external to FOLIO.
      • If displayed in the quickMARC, data in MARC 001 and 999 ff fields would be visible, but not editable
      • Once SRS is expanded to include MARC holdings records, quickMARC may be expanded to allow for editing of MARC holdings also, but not in current scope

      Future note:
      If quickMARC is expanded in the future to allow for creation of a MARC bib from an Inventory instance that does not already have an underlying source MARC; then when it is saved, it

      1. will need to be saved as a new MARC Bib in SRS
      2. with the instance HRID in 001 field
      3. linked to the corresponding instance via the 999 ff field
      4. and the editing of the instance in Inventory blocked (Instance Source changed to MARC)

        TestRail: Results

          Attachments

            Issue Links

            defines

            Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. UXPROD-47 Batch Importer (Bib/Acq)

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Analysis Complete
            is defined by

            Bug - A problem which impairs or prevents the functions of the product. MODINV-311 Adding or changing notes in quickMARC creates error in Instance record notes

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

            Bug - A problem which impairs or prevents the functions of the product. MODINV-321 Cannot delete a field in quickMARC

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

            Task - A task that needs to be done. MODINV-324 Add source-record states storing mechanism for QM edit workflow

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

            Task - A task that needs to be done. MODSOURCE-114 Add State "field" to records table.

            • 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. MODSOURCE-115 Create endpoint for retrieving "sourceRecords" using "matchedId" and generationId-mechanism.

            • 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. MODSOURCE-116 Add filtering of sourceRecords to return only latest generation

            • 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. MODSOURCE-168 Bugfest. Changes to MARC record in quickMARC do not save to the Instance

            • 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-268 Implement endpoint for updating MARC records

            • 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-271 SPIKE: Define API contract between SRM\SRS and quickMARC

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

            Task - A task that needs to be done. MODSOURMAN-272 SPIKE: Design updating of marc records and related instances

            • 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-276 Create endpoint for retrieving MARC record by instance id

            • 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-317 View source, Instance, and edit in quickMARC get out of sync after several edits

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

            Task - A task that needs to be done. MODSOURMAN-321 Change response status to 202 on parsed record update

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

            Bug - A problem which impairs or prevents the functions of the product. UIIN-1119 Instance 'Action" dropdown menu is slow after a quickMARC edit is saved

            • TBD - To be determined
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. UIIN-1125 View source does not always show the most recent version of the SRS record

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINV-207 Implement Update action handler for Inventory Instances

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

            Umbrella - MODSOURMAN-262 Automatically update Instance when SRS MARC Bib is updated

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

            New Feature - New feature requests UXPROD-2272 Connect SRS and quickMARC for MARC Bibs (Firebird/quickMARC work)

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

              Activity

                People

                Assignee:
                abreaux Ann-Marie Breaux
                Reporter:
                abreaux Ann-Marie Breaux
                Analysis Estimator:
                Ann-Marie Breaux Ann-Marie Breaux
                Front End Estimator:
                Viktor Soroka Viktor Soroka
                Back End Estimator:
                Oleksii Kuzminov Oleksii Kuzminov
                Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases