Closed michelleif closed 1 year ago
@rlunnon is there a list of tags this should be performed on?
Or is “all fields in the marc record” safe to do this on? Is $= a valid field in any other marc tag?
Here is a list of the bib tags that may have a subfield =. The 400,410 and 411 tags are authorized but there are only a handful, and none has a subfield = , so I did not include them. The 240 tag is authorized only in the RECORDING and SCORE formats.
Thanks @rlunnon, for the 240 field, is the format for RECORDING and SCORE in the subfield $h or do should I look in a different field/subfield in the record to make this determination?
@jermnelson it wouldn't do any harm to check the 240 in all records, if that is easier than sorting out the RECORDING and SCORE records. There shouldn't be any 240 with subfield = in the other formats.
The record format is determined by position 06 of the leader. RECORDING format values: i j
SCORE format values: c d
update: waiting to see if Khalilah gets back to Vitus on whether or not adding the $0 will mess up authority matching later
Per Vitus, Khalilah has given the go ahead. See thread here.
@jermnelson please change $= to $0 and add (SIRSI) e.g. |0(SIRSI)1863552
Run test on -dev first.
@dlrueda Vitus also asked to Delete all the |?UNAUTHORIZED because we won't need them. They will just clutter up the field.
does that get done here or in your export?
related to #472
deleting the string |?UNAUTHORIZED
should be done on the airflow side. So it can be a part of this ticket.
@ahafele question about the authkey value. In the MARC records I've seen with the subfield $=
, the authkey has a caret character before the value i.e.$=^A262428
, that with the SIRSI prefix ends up in the subfield 0
as $0(SIRSI)^A262428
. Should the caret character be removed?
Hmm I defer to @dlrueda on this one. Darsi, see question about about ^
Jeremy, please also add to this work the deleting of the string|?UNAUTHORIZED
Absolutely remove the caret! In fact, remove “^A” so both the caret and the A.
Sorry it should’ve been in the original spec, doh.
Thanks @ahafele and @dlrueda! Will remove ^A
for the subfield. Also, are there any MARC records examples I can test to remove |?UNAUTHORIZED
? Thanks!
a14465595 a14257390 a4365992
and some from range ckeys_13350000_13399999
.001. |aa13399970 .001. |aa13399971 .001. |aa13399973 .001. |aa13399974 .001. |aa13399976 .001. |aa13399977 .001. |aa13399978 .001. |aa13399980 .001. |aa13399981 .001. |aa13399983 .001. |aa13399984 .001. |aa13399985 .001. |aa13399986
we tested migrating Symphony authkey for headings into $=, FOLIO quickMARC doesn't like this, so instead: put authkey into $0
do test on DEV first