Representation of Titles with Chinese Characters

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Article Type: General
Product: Aleph
Product Version: 20

Description:
In our current setup, Chinese character titles are in 245 fields and the Han Yu Pin Yin, latin, characters are in 880 fields. Our cataloger wishes to know if it is possible to display the fields as consecutive 245s.

Resolution:
Yes, this can be done on an ongoing basis. In addition, we can run a job that will move ALL existing 880 fields to their parallel field names (fix_doc_880). To limit this to specific records, such as 245 would require additional steps, but should be possible.

The current situation is that fix_doc_880 is being run at certain defined times:
ABC01/tab/tab_fix
LOCAT fix_doc_880
OCLC fix_doc_880
EXPRT fix_doc_redo_880

LOCAT is run automatically when the Locate record function is used in the Catalog GUI.
OCLC is run when the oclc_server is used. It is also used by p_file_93.
EXPRT is used during record exports (e.g., p_print_03).

If you prefer the parallel fields instead of the paired 880 setup, we should be able to turn off:
NPL01/tab/check_doc
CATALOG-INSERT check_doc_paired_fields
Z39-INSERT check_doc_paired_fields
Z39-REPLACE check_doc_paired_fields

SysLib Guide, Cataloging

p39
fix_doc_880
This routine replaces the tag number of the alternate graphic representation field (880) by the associated tag registered in subfield $6 of the field. In addition, the tag number of the associated field is removed from subfield $6 but the occurrence number is retained. For non-880 fields, the tag number of the associated field (for example, 880) is removed from subfield $6 and the occurrence number is retained. This program creates parallel fields, both containing the same tag number. For example:
1001 L $$6880-01$$a[Name in Chinese script].
8801 L $$6100-01/(B$$aShen, Wei-pin.
Is changed to:
1001 L $$601$$a[Name in Chinese script].
1001 L $$601$$aShen, Wei-pin.
Note that for this fix to work, subfield $6 must be the first subfield in both linked fields.

p55
fix_doc_redo_880
This routine reverses the effects of the fix_doc_880 program. This program restores the tag number of the alternate graphic representation field (880). For example:
1001 L $$601$$a[Name in Chinese script].
1001 L $$601$$aShen, Wei-pin.
Is changed to:
1001 L $$6880-01$$a[Name in Chinese script].
8801 L $$6100-01/(B$$aShen, Wei-pin.
Note that the order of the paired fields is important, because the tag of the first of a pair is left as is, and the second of a pair is transferred to 880.
In addition, note that the input for this program must be in MARC8 (not in UTF) encoding. The reason for this is that this fix routine sets the escape sequence and
orientation for the language code, and in order to do so, the record must be in MARC8 encoding. The fix_doc_redo_880 program will work correctly on UTF records, but will not set the escape sequence and orientation for the language code.

p85-85
check_doc_paired_fields
This program checks the following two aspects related to fields that are linked by subfield $6 (subfield $6 contains data that links fields that are different script representations of each other), such as:
1001 L $$601$$a[Name in Chinese script].
1001 L $$601$$aShen, Wei-pin.
If the record contains a field with subfield $$6 <value numeric - other than '00'>, there must be an additional field with the same tag and indicators and the same $$6 value. If the record contains a field with subfield $$6 <value numeric - other than '00'>, there must be no more than two fields that have the same $$6 value.

Article last edited: 10/8/2013