Hi all,
We've had difficulty finding records in our catalog due to the automatic
stemming that occurs when records are indexed in Evergreen. As an
example, a title on one of our summer readings lists was The Assist by
Neil Swidey. However, when users were searching for the assist as a
title
On Tue, Aug 14, 2012 at 06:22:15AM -0400, Kathy Lussier wrote:
Hi all,
We've had difficulty finding records in our catalog due to the
automatic stemming that occurs when records are indexed in
Evergreen. As an example, a title on one of our summer readings
lists was The Assist by Neil
On Tue, Aug 14, 2012 at 9:16 AM, Dan Scott d...@coffeecode.net wrote:
On Tue, Aug 14, 2012 at 06:22:15AM -0400, Kathy Lussier wrote:
Hi all,
We've had difficulty finding records in our catalog due to the
automatic stemming that occurs when records are indexed in
Evergreen. As an example, a
While looking into ways to integrate our SMS service provider to
Evergreen, I came upon the idea to follow SMSes' sent, and whether or
not they reach their destination. An email is sent to a special account
for any undeliverable SMSes. Currently in Evergreen we don't have a clue
what happens
As a librarian who frequently uses Evergreen at the reference desk, I would
prefer to have stemming used to retrieve results, but have exact matches
ranked highest, then close matches, and finally distant matches. The search
results for assist would then include the word assist, assists, and
Thank you for your help and feedback Dan!
This particular example is quite a concern! I haven't noticed anything
similar yet, since we moved to Evergreen 2.3ish last week, and nobody
has brought a similar problem to my attention, but it might just be
early days for us.
Echoing what Mike said,
Thanks Mike!
Relating particularly to this example, though, is the (now generally
unused) relevance adjustment code that targets exactly this problem by
boosting the score of (without restricting to) exact word matches.
One of the hopes with the convert some stored procedures from perl or
On Aug 14, 2012 11:58 AM, Benjamin Kalish bkal...@forbeslibrary.org
wrote:
As a librarian who frequently uses Evergreen at the reference desk, I
would prefer to have stemming used to retrieve results, but have exact
matches ranked highest, then close matches, and finally distant matches.
The
I'm trying to upgrade a training server from 2.2-rc1 to 2.2.1. The last
script registered in config.upgrade_log is 0709 so I ran 0710 but got an
error:
Here is what I typed:
psql -U evergreen -h localhost -v eg_version=null -f 0710*
Here is what I got:
ERROR: cannot ALTER TABLE issuance
Hello Martha,
Yes, you will want to add that line between the UPDATE and the first ALTER
TABLE. Since 0706 and 0710 are two versions of the same idea, the upgrade file
probably combines the two (so that is where the line came from). To help
explain what is happening, some of the constraints
10 matches
Mail list logo
