Adding MARC modifications to single record overlay doesn't respect field protections

MARC Modification action should not take into account field protection settings - such were original requirements and we have test rails that explicitly test that
https://foliotest.testrail.io//index.php?/cases/view/350678
https://foliotest.testrail.io//index.php?/cases/view/359188

Supported scenarios for using MARC Modify are described here - https://folio-org.atlassian.net/wiki/spaces/DD/pages/1778826/3.+Modify+MARC+BIB

@Ryan Taylor, please review the user documentation contains details about Modify action and and fields protections. I believe this issue could be closed as not a bug. Thank you!

FROM SUPPORT: Thank you @Jennifer Eustis for providing more information. @Ryan Taylor can you respond and explain why the ticket remains blocked? Thanks

Hi @Ryan Taylor , when I put the marc modification for a marc srs update at the beginning of the job and before the match, the field protections (in my one test) were respected. I would say this is a good sign. It seemed from our discussions that no one could think of needing to have a marc modification at the end or after an update marc action. Perhaps the flow is that on update the marc modification has to come first?? If we stick to that and a few more tests to make sure that this flow respects field protections, would it be possible to close this out? And this would apply to Quesnelia as this is when the new flow of where to put marc modifications starts.

Support SIG: @Jennifer Eustis @Ryan Taylor please update the ticket with the outcome of the conversation in the DI working group, as mentioned above. I assume this ticket is blocked on that conversation, while we don’t see any tickets listed as blocking work.

If this conversation states that all is good, then please close the ticket.

@Ryan Taylor , I just tested this in bugfest quesnelia and it is working. I’ll do a couple of more tests. The first test that I did was a job profile that was part of the SRI update instance. This worked.

However, when I use this same marc modification profile to update an instance, the protected fields are stripped from the existing record. See job https://bugfest-quesnelia.int.aws.folio.org/data-import/job-summary/bb20e0ff-826c-4a1d-9740-7141581ded8f and https://bugfest-quesnelia.int.aws.folio.org/data-import/job-summary/7584a479-3049-4927-af99-3980edebb6e5

I ran another version where instead of putting the marc modification at the end of the profile or after the update instance action, I put it in front of the match as the first action in the job for the solo job profile to update the instance. This preserved the field protections. https://bugfest-quesnelia.int.aws.folio.org/data-import/job-summary/6d15e02c-03d0-4c4f-aa3d-77f8ab804c53

@Debra Howell We’ll be talking about MARC modifications this week in DI working group. I would prefer to hold off until we have that discussion where I’ll bring this up.