The 264 fields are the most likely field to be locally added if the library
is editing hybrid AACR2/RDA records to full RDA in their catalogs. And 264s
are also likely to be the only field in a MARC record for an English
language title to have a special character since we indicate copyright and
pho
Jason and Mike,
Thanks so much for the help! Glad to know that it’s a remote issue and not
something set up incorrectly on our side.
-Brent
-
Brent Mills
Systems Librarian | Sage Library System
email: br...@hoodriverlibrary.org
tickets: https://sagelib.org/support
p
Jason hit on (almost certainly) the answer: bad records from sources that
don't restrict cataloging to valid character sets. I'll add a couple
comments below for general clarification, as well...
On Fri, Dec 2, 2016 at 4:52 PM, Brent Mills
wrote:
> Hello,
>
> I’ve recently noticed some issues w
Brent,
The records are mostly likely not MARC-8 or UTF-8. The example you
shared looks like a Windows-1252 "smart" quote. I would not be surprised
if the records have characters from multiple character sets in them.
I've seen that before.
I don't have any useful suggestions for you, other than su
Hello,
I’ve recently noticed some issues with imported MARC records from a specific
set of Z39.50 servers.
A noticeable amount of records that are imported through Prospector/MaineCat
targets have mangled characters when diacritics, symbols,etc.. are present in
the record.
Does anyone have so
