Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

MARC records updated with Single Record Overlay thereafter uneditable

Description

When using Single Record Overlay to update an existing record, that record becomes uneditable thereafter.  This is not the case for records brought in using Data Import or for records CREATED by Single Record Import, only those that had a MARC record already.   Checking the underlying data, it seems that after overlay, there are multiple "active" SRS records for that Instance, which seems to be the root of the issue (marking the older as 'OLD' makes the MARC editable again).

I think the way the "generation" value works changed.... I have an instance with 6 SRS records.  The first three (chronologically) are generations 1, 2 and 3, with the third being "ACTUAL".... but then there are three more versions after, starting with generation 0, with the gen2 record also being 'ACTUAL' (and the most recent)

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Checklist

hide

Activity

Show:

Ryan Taylor July 23, 2024 at 2:50 PM

Confirmed as same underlying issue as https://folio-org.atlassian.net/browse/MODDATAIMP-1058. Moving ticket to Done.

Ian Walls July 8, 2024 at 4:41 PM

I took a look at the data in the DB, and can confirm the following case:

  • 7 generations of a MARC record, numbered 1-7, with 7 being listed as ACTUAL, all had the matchedId = ‘9ee57d90-a0d8-4c46-9ce5-8fa309712c10’

  • 1 additional record, with generation 0 and the most recent created date, also with state ACTUAL and matchedID = ‘d0a18981-c768-48ed-b312-1fc90e6f4022’

  • ID ‘d0a18981-c768-48ed-b312-1fc90e6f4022’ is a valid record ID in raw_records_lb, while the other is not.

Based on the explanation of MODDATA-IMP-1058, it seems to me that this is the same underlying issue.

Ruslan Lavrov July 4, 2024 at 10:38 PM

Hello , could you please provide the multiple ACTUAL records for some particular instance? So that I could check if the root cause is the same as for bug.

Ian Walls June 26, 2024 at 5:54 PM

Yes, this is applicable to Poppy. We’re currently running CSP #5

Charlotte Whitt June 26, 2024 at 8:31 AM
Edited

- I added the label support to this issue. It will probably help the developers when troubleshooting this issue, if they also get information about what version of FOLIO this issue has been seen in; e.g. Poppy (and maybe a given CSP) etc.

CC:

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Folijet

Parent

Release

Ramsons (R2 2024)

RCA Group

Data related (ex. Can be detected with large dataset only)

Affected releases

Poppy (R2 2023)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created June 25, 2024 at 5:39 PM
Updated February 7, 2025 at 4:39 PM
Resolved July 23, 2024 at 2:50 PM
TestRail: Cases
TestRail: Runs