Allow a NR to run with the PTC job
TL;DR:
We would like to have the ability to run a normalization rule whenever the PTC modifies a record.
Background:
In November 2024 Ex-Libris added a new functionality to the PTC job:
MARC 21 Preferred Term Correction Can Flip Headings with Cross-Reference in Different Field
https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2024/Alma_2024_Release_Notes?mon=202411
Problem:
The PTC job only changes the first indicator correctly when the PTC job changes a field into 630.
in all other cases, the existing indicators remain.
We opened a case and spoke directly with Ex-Libris, but were told that the PTC job runs as intended, and that not handling the indicators is not a bug.
I understand that other institutions have different reasons for having a NR run whenever the PTC changes a record.
Request:
We would like to have the option to add a normalization task to the PTC in the configuration menu, that way we will be able to fix problems that arise from this job.
-
Hanoch Roniger
commented
Having the on-save NR is defintately a valid approach -- the needed corrections appear in ours. It also runs automatically whenever a job is run manually.
The main thing is to have some kind of normalization running alongside the PTC job.
If EL are concerned with an overload of system resources, we can put the specific changes in a lighter NR. -
Lisa Hatt
commented
Ariel's comment was my thought, that the on-save normalization should run when PTC edits the record so that fields are reordered, and if desired then one could put indicator corrections in there (I believe).
-
Ariel Lock
commented
Possible variation: Automatically run on-save normalization process after PTC job runs
Example use case: we have an on-save NR that reorganizes the subfields that are not part of the heading in a specific order; this is important for us for processes that are external to Alma. Since the PTC job doesn't always retain this order, it would be very helpful if the on-save NR runs after the PTC job finishes running