We tried that and it looked fine, then we saved the record. But when we re-opened it, the field had reverted back to right-to-left reading order. Puzzling.
I imagine your display issue is caused because the field is reading right-to-left. You can make the 670 display “properly” in OCLC by changing the directionality of that particular field. One way to do this is to right-click in the field, then choose Right-to-Left Reading Order to remove the check mark. The field will switch so that the title appears first.
…and I’m tickled pink that your example is one of our first script records!
Cataloging & Metadata Services Director
Princeton University Library
From: Program for
Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Sarcia,
Sent: Thursday, July 17, 2008 3:55 PM
To: [log in to unmask]
Subject: Non-Latin references - 670 display with Arabic characters
One of our Arabic language catalogers has noticed an idiosyncrasy in the display of the 670 field in OCLC when he inputs Arabic characters. The portion of the $b in parenthesis that contains the Arabic script jumps to the far left of the field in front of what would be the start of $a (i.e., the field switches to right-to-left reading order when he inputs Arabic characters).
If the record is printed, it looks fine, as does the public display. It seems that only the display in OCLC looks a bit funny. For example, see the record for: Khatir, Jurj Anis (no2008101559). The 670 looks a bit odd in OCLC, but displays fine if you view it in the LC online authorities, or if you print the record. Is it something specific to OCLC, or is there something on our end that we need to do to correct the display?
Thanks for any insight,
Catalog Librarian/NACO Coordinator
Catalog & Metadata Services
Sterling Memorial Library
tel: 203.432.6406 fax: 203.432.7231
[log in to unmask]