Hi all,
We have imported bibliographic and holdings data of the Evangelical
Theological Seminary library to Evergreen 2.5.3!
Yet, we have encountered the following problem (maybe a bit related to a
recent discussion on Dewey normalization:
Hello Linda,
I don't fully understand how you built your holdings, but it looks like you
found something that worked for you.
Your update is failing on a record which already has both versions of the call
number (correct with '.' and incorrect with 'space'). See here:
Hi Erick,
I'll try to take some time to try an upload with the records you
attached to see if I can get it to work on a 2.5ish system. However, one
small thing jumped out at me from your e-mail.
I would avoid using the (NOT 020a) expression you identified in your
e-mail. I'm not sure how
I echo Dan's thanks to everyone who pitched in on 2.6.
Dan, I'm particularly honored by the HAAS medal ... I'm always happy
to fight a clog, and the plungers are perfect. ;)
--miker
On Fri, Apr 25, 2014 at 4:07 PM, Dan Wells d...@calvin.edu wrote:
Hello all,
With 2.6.0 cut 10 days ago, it is
Hi Erick,
I just tried uploading your MARC file on a 2.5 system (not sure which
point release) with two different match sets:
(item_lang AND (240 ‡a OR 245 ‡a))
(020 ‡a)
In both cases, I had no trouble loading records into the queue. I'm not
sure why you would be seeing something different
Thank you, Dan! Your hint with the bib record with two versions of the
same call number has helped us find the right way to proceed (four
remaining troublesome records will be dealt with manually :-):
evergreen=# UPDATE asset.call_number SET label = replace(label, '.', '-');
UPDATE 10355
Hello everyone,
The Evergreen Documentation Interest Group has its next meeting
scheduled for Thursday, May 1st, 2014 at 2:00 PM EST on the
#EvergreenIRC channel (http://evergreen-ils.org/irc.php).
Anyone interested in documentation is welcome to attend. An agenda has
been posted at
