Bug 12468

Summary: copyright symbol not translating right
Product: Koha Reporter: Nicole C. Engard <nengard>
Component: CatalogingAssignee: Galen Charlton <gmcharlt>
Status: CLOSED FIXED QA Contact: Testopia <testopia>
Severity: normal    
Priority: P5 - low CC: george, hector.hecaxmmx, jonathan.druart, larry, m.de.rooy
Version: Main   
Hardware: All   
OS: All   
See Also: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14734
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Attachments: shown on yale opac
shown in koha

Description Nicole C. Engard 2014-06-23 19:10:55 UTC
Created attachment 29177 [details]
shown on yale opac

The new 264 field can have a copyright symbol in it, but that won't translate in to Koha when you import using Z39.50.  See attached.
Comment 1 Nicole C. Engard 2014-06-23 19:11:09 UTC
Created attachment 29178 [details]
shown in koha
Comment 2 Nicole C. Engard 2014-06-23 19:11:17 UTC
For testing you can use ISBN: 9781451695182
Comment 3 Larry Baerveldt 2014-07-01 21:24:04 UTC
I suspect this bug may affect OCLC Connexion imports as well. We have records of several imports failing with this error in intranet-error.log:

import_bib: "\\x{00a9}" does not map to utf8 at /var/lib/koha/coos/kohaclone/svc/import_bib line 55.
Comment 4 Owen Leonard 2014-07-02 12:51:51 UTC
(In reply to Nicole C. Engard from comment #2)
> For testing you can use ISBN: 9781451695182

That ISBN will return a variety of records depending on the Z39.50 source.

I've run into what looks like the same issue though. I'm seeing stuff like this in some MARC records we get from OCLC:

=264  \4$c&#xFFFD;2001
Comment 5 Héctor Eduardo Castro Avalos 2015-10-07 20:49:45 UTC
This record exist in Library of Congress but don't have copyright date.

I've been searching another example but after an hour I found nothing.
Although a record with phonograph found in LC database with LCCN 2014618376 in Koha searched with Standard ID. The record was successfully copied to the default framework.

Maybe, like comments 3 and 4 only OCLC connexion got that problem. It seems to be an UTF-8 problem.

Regards
Comment 6 Jonathan Druart 2018-01-15 16:02:22 UTC
I guess this is solved, please reopen if not.