Representation of CJK MARC tags
- Product: Aleph
- Product Version: 20, 21, 22, 23
- Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care
Description:
We would like to represent CJK records with the original vernacular script (eg. Chinese script) BEFORE its corresponding romanized form (eg. Hanyu Pinyin) in the display.
The romanized form comes before the CJK form. Any idea if we can swap it?
These records are loaded from OCLC. Our investigation shows that OCLC is not sending in the correct 880 when the OCLC client is set to have "include all data, with Latin script in 880 field" (this is the correct setting to allow the Chinese script to appear before the Latin script). However, when we set the OCLC client to have "include all data, with other scripts in 880 fields", the parallel fields appear correctly. Unfortunately, this results in the Latin form appearing before the Chinese form.
Resolution:
This is the concept. It creates a fix (invoked by fix_doc_do_file_08) called "fliptag"; to implement this example....
! 2 3 4 5 6 7 8 9
!-!!!!!-!!-!-!!!-!!!-!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
1 880## COND-LOAD-VAL-MATCH N,$$6246
1 880## CHANGE-FIELD TMP##,L
1 TMP## REPLACE-STRING 246-,880-
1 246## COND-LOAD-VAL-MATCH N,$$6880
1 246## REPLACE-STRING 880-,246-
1 246## CHANGE-FIELD 880##,L
1 TMP## CHANGE-FIELD 246##,L
This type of change needs to be added for each field that you want changed.
The stability of this fix depends on a lot of variables. It should work if there is only one instance and it is built correctly.
Nevertheless, I would recommend using it sparingly. Is it critical that all paired fields be flipped (Chinese first)?
Until this is well-tested, I would recommend that catalogers double-check the results.
- Article last edited: 12-Mar-2016