[OPEN-ILS-GENERAL] Bib records not indexed - Evergreen 1.6.0.3

[Linda Jansova]

  Hi Dan,

Thank you very much for testing those records in 2.0 :-)! Since we are 
currently using Evergreen for a small private library (presumably first 
in the Czech Republic to use Evergreen), we should be able to upgrade to 
2.0 when it becomes available. Supposing the bib records get reindexed 
after the upgrade, it will hopefully work fine :-).

At the same time we are working with a bigger library (part of JABOK, a 
school focusing on social pedagogy and theology) and planning to do the 
migration in the fall, so we will probably wait for 2.0 version. So it 
will be our pleasure to help with some testing :-).

Linda Jansova and Vaclav Jansa

Dne 11.9.2010 04:23, Dan Scott napsal(a):
> On 10 September 2010 02:42, Linda Jansova<skolkova at chello.cz>  wrote:
>>   Dan, thanks for the explanation and also for the positive news that
>> Evergreen 2.0 should be able to handle these characters without problems
>> :-)!
>>
>> Deanna, I believe that USMARC or SUTRS syntax should not be the problem as
>> other bib records in USMARC format have been processed correctly.
>>
>> BTW, we encountered problems with these characters also in the older
>> versions of Evergreen we experimented with earlier - an example (which is
>> still "valid")  would be a record from the Library of Congress (TCN 3760924
>> - or it can be found using Author Čapek, Karel and Title RUR :-). Maybe this
>> could also be an example worth trying in Evergreen 2.0...
>>
> Hi Linda:
>
> I had a few minutes this evening and tried the NKC examples and the
> Library of Congress example that you gave (thanks for such a clear
> description of the problem and such great sample data!); all of the
> examples imported perfectly and get indexed properly; keyword searches
> and title searches retrieve the records. So, good news on that front!
>
> If you're wondering about the timing of Evergreen 2.0, we'll be
> putting out a second alpha release of Evergreen 2.0 soon, with a beta
> release expected in October, and then more betas until we stamp out
> all of the bugs our determined testers find, hopefully resulting in a
> final release in December or January. It would be great if you could
> help us with some early testing of 2.0!
>
> Dan
>