Looks like it's fixed for us! Thanks for your help, everyone!
On Wed, Mar 22, 2017 at 9:11 AM, Sarah Childs
wrote:
> Hopefully there will be a quick resolution. The problem seems to be
> affecting a lot of libraries.
>
> On Wed, Mar 22, 2017 at 12:04 PM, Jane Sandberg
> wrote:
>>
>> We might en
Hopefully there will be a quick resolution. The problem seems to be
affecting a lot of libraries.
On Wed, Mar 22, 2017 at 12:04 PM, Jane Sandberg
wrote:
> We might end up using Vandelay, but we might also just wait for this
> issue to be resolved. There's no shortage of other things to do
> aro
We might end up using Vandelay, but we might also just wait for this
issue to be resolved. There's no shortage of other things to do
around here. :-)
On Wed, Mar 22, 2017 at 8:58 AM, Elaine Hardy
wrote:
> OH NO!
>
> Can you use Vandeley for the duration of the error? Before I reported the
> prob
OH NO!
Can you use Vandeley for the duration of the error? Before I reported the
problem with OCLC I used it to overlay a record to check if the issue was
more widespread than the Z39.50 interface. Diacritics were fine.
Elaine
J. Elaine Hardy
PINES & Collaborative Projects Manager
Georgia Publ
Thanks, Elaine and Galen! I did submit a launchpad bug
(https://bugs.launchpad.net/evergreen/+bug/1675074), please feel free
to comment on or refine it.
And here's hoping that OCLC fixes this soon! It happened while we
were in the middle of a Spanish-language cataloging project; not a
great time
Hi,
On Tue, Mar 21, 2017 at 5:36 PM, Jane Sandberg wrote:
> Is there an Evergreen setting somewhere that would specify a charset
> and fix this problem?
Not at present. Hopefully OCLC will revert their change soon, but it
would be handy to teach Evergreen Z39.50 client configs about server
chara
Jane,
OCLC does have a system alert posted and is working on a solution.
With the exception of records with the copyright character or those titles
that are timely, our catalogers have been instructed to hold off importing
diacritic laden records (to prevent duplicates, we bring in records one
Hi all,
OCLC made updates to its z39.50 service on Sunday, and since then,
it's been sending badly encoded characters like nobody's business.
I've been able to find out how to get uncorrupted characters in
yaz-client, but I don't know how to get Evergreen to do the extra
utf-8-setting step detaile