Cannot add multiple uncontrolled subfields to a linked "MARC bib" field

Description

Overview: Cannot add multiple uncontrolled subfields to a linked "MARC bib" field upon data import

Preconditions:

  • Job profile created to update "MARC bib" record by matching "999 f f s" subfield

  • The system must have at least 1 "MARC Bibliographic" record which has fields linked to at least 1 "MARC Authority" record.
    You can use files from the attachements:
    1) "MARC Authority" record (Import it via "Data import" app using "Default - Create SRS MARC Authority" job profile):
    Chin, Staceyann(original_record).mrc
    2) "MARC Bibliographic" records (Import it via "Data import" app using "Default - Create instance and SRS MARC Bib" job profile):
    The other side of paradise a memoir Staceyann Chin (with letter and digit subfields in 100).mrc

  • The "100" MARC field with "$a" value "Chin, Staceyann," of imported "Instance" record ("The other side of paradise : a memoir / Staceyann Chin.") must be linked to the "100" field of imported "MARC Authority" record ("Chin, Staceyann, 1972-").

  • Authorized user with the following permissions:
    Data import: Can upload files, import, and view logs
    Inventory: All permissions
    MARC Authority: View MARC authority record
    quickMARC: Can Link/unlink authority records to bib records
    quickMARC: View, edit MARC bibliographic record
    UI: Data export module is enabled

  • User is on "Inventory" pane with search results for "Instance" record which was linked with "MARC Authority" (see Precondition, e.g.: "The other side of paradise : a memoir / Staceyann Chin.").

Steps to Reproduce:

  1. Check the checkbox that is displayed next to the "Instance" record which is linked to "MARC Authority" records on the search result pane (For example: "The other side of paradise : a memoir / Staceyann Chin.").

  2. Click on the "Actions" button on the second pane and select "Export Instances (MARC)" option.

  3. Go to "Data export" app.

  4. Download exported ".mrc" file by clicking on the "File name" column value.

  5. Open downloaded ".mrc" file via "MarcEdit" (or any similar app).

  6. Add second "$e" subfield BEFORE existing "$e" subfield in a controlled field (for example, add "$eNarrator" before "$eAuthor" in "100" field)

  7. Save the edited ".mrc" file.

  8. Go to the "Data import" app >> Click on the "or select files" button >> Select the updated ".mrc" file (see previous step) >> click the "Open" button

  9. Click on the job profile created in precondition >> Click on the "Actions" in the appeared third pane >> Select "Run" option >> Click on the "Run" button in appeared modal.

  10. Click on the new row with "Completed" status after job cpmpletes

  11. Click on the "Updated" link in "Instance" column in completed job details window

  12. Click on the "Actions" button and select "Edit MARC bibliographic record" option from the expanded menu.

Expected Results:  Two "$e" subfields are shown in the fifth box of linked field (e.g. "100" field) - for example "$e Author $e Narrator"

Actual Results: Only newly added "$e" subfield is shown in the fifth box of linked field (e.g. "100" field) - for example "$e Narrator"

Additional Information:

  • Please see attached screencast:

  • Second uncontrolled field of the same type not added at all if you add it AFTER existing subfield (e.g. "$eAuthor$eNarrator")

  • No issues when adding multiple uncontrollable fields to a not linked linkable field

  • The same happens when updating record by matching "999 f f i" subfield

  • Issue is now reproducible on Snapshot too

Interested parties:  

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

14
  • 31 Mar 2023, 04:58 PM
  • 31 Mar 2023, 04:57 PM
  • 29 Mar 2023, 08:14 AM
  • 29 Mar 2023, 08:11 AM
  • 29 Mar 2023, 08:11 AM
  • 28 Mar 2023, 07:41 AM
  • 28 Mar 2023, 07:41 AM
  • 28 Mar 2023, 07:41 AM
  • 28 Mar 2023, 07:41 AM
  • 28 Mar 2023, 07:41 AM
  • 24 Mar 2023, 05:24 PM
  • 22 Mar 2023, 02:21 PM

Checklist

hide

TestRail: Results

Activity

Show:

Yauhen Viazau March 31, 2023 at 4:59 PM

Verified on Orchid BF - works as expected Check Mark

Please see attached screencasts:

  •  

Yauhen Viazau March 29, 2023 at 8:15 AM

Verified on Snapshot-1 - works as expected Check Mark

Non-controllable subfields can be added to a linked field having existing subfield(s) of the same letter/type.

Please see attached screencasts:

  •  

No issues with adding letter or digit subfields. Non-controllable subfields still can be added to linkable (not linked) field.

Yauhen Viazau March 28, 2023 at 7:48 AM
Edited

I have tested this issue with different scenarios on both Orchid BF and Snapshot-1.

Info Issue is now reproducible on Snapshot too.

Info It is not exclusive to $e subfield or 100 field.

The following behavior is observed:

  • When adding second non-contollable subfield before existing one (same letter) → Existing value is replaced by new one

    •  

  • When adding second non-contollable subfield before existing ones (same letter) for several existing subfields of several types/letters in one field → Existing values are replaced by new ones for each subfield type/letter

    •  

  • When adding two non-contollable subfields before existing one (same letter) → Existing value is replaced by first of the new ones

    •  

  • When adding second non-contollable subfield before two existing ones (same letter) → First existing value is replaced by new one

    •  

  • Issue might not be reproduced (subfields successfully added) if updates were made to other subfields

To summarize, the first existing non-contollable subfield always gets replaced by the first added subfield of the same letter (different letters are replaced separately).

- please review

Khalilah Gambrell March 27, 2023 at 5:42 PM

Hey   - so odd that is only when adding another $e?

Yauhen Viazau March 24, 2023 at 5:24 PM

Still reproducible on Orchid BF - see attached screencast:

NOTE: update works as expected if other subfields also edited. The issue reproduced only when adding another $e is the only update made.

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Spitfire

Fix versions

Release

Orchid (R1 2023) Bug Fix

RCA Group

Missing integration/unit test

Affected releases

Orchid (R1 2023)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created March 22, 2023 at 1:05 PM
Updated May 3, 2023 at 11:47 AM
Resolved March 29, 2023 at 2:45 PM
TestRail: Cases
TestRail: Runs

Flag notifications