Libsys discussion needed - In Symphony/Eloader land we had a large number of preprocessing perl scripts that would run on MARC records before loading. We have accounted for some of this need in the interface configuration options, but we still have a need to automate some custom MARC modification before loading and would like to enable a small number of users to create and manage the scripts to do so. Currently there are many "packages" that are not fully automated through VMA because the records are first downloaded from VMA by user, edited in e.g. MARCedit, and then loaded to Data Import.
Examples:
856 subfield edits and additions for former eloader packages
Acq European vendor edits
• change 980 $e to $m
• remove 980 $i, $j
• build 035\9 using the value in 980 $c (with "it" added before the value)
• delete fields: 900, 901, 910$aSupplied on.. (keep 910 with vendor name), 981, 990
In addition to the above edits, also do the following for the "g" subaccount only:
• change 980 $b fund to ARTARCH
Libsys discussion needed - In Symphony/Eloader land we had a large number of preprocessing perl scripts that would run on MARC records before loading. We have accounted for some of this need in the interface configuration options, but we still have a need to automate some custom MARC modification before loading and would like to enable a small number of users to create and manage the scripts to do so. Currently there are many "packages" that are not fully automated through VMA because the records are first downloaded from VMA by user, edited in e.g. MARCedit, and then loaded to Data Import.
Examples: