Happy New Year!
Niagara College has been using Evergreen and Summon quite successfully since
September 2010. However, we've experienced a bit of a problem with deleted
records. I've been in touch with Andrew Nagy of Serials Solutions and he
provided the following info:
The reason why your
HI Gordana
Yes, there's a Boolean field called deleted in the biblio.record_entry table.
If it's true, the bib record is deleted. There's also a deleted field
in other Evergreen tables as well.Asset.copy, and asset.call number,
Hope that helps.
June
From:
Hello Gordana,
There are 'hooks' to do this - so you can adjust your method of dumping MARC
for Summons to *exclude* records where deleted = 'true' - this flag is set in
the biblio.record_entry table.
How is Summons consuming your MARC records? I assume that Summons is using the
more
The reason why your deleted records are getting indexed is that the MARC
mapping that we have defined for your collection does not delinitate between
a good record and a deleted record. We need some way of knowing whether a
record is real or deleted. Do you know if evergreen can do this?
Hi George,
Right now, we are sending our deletes in nightly updates. The problem
is that the deletes aren't registering in Summon.
For example, search in Summon on Social interest challenge to mankind,
limit to items in the library catalogue:
Hi everyone,
I just saw Jason's suggestion of the d for deleted in the leader. I
will forward this on.
Thanks so much for all your help! Always greatly appreciated.
Gordana
Gordana Vitez gvi...@niagaracollege.ca 1/9/2012 1:28 PM
Hi George,
Right now, we are sending our deletes in nightly
I have a sparkling fresh install of Evergreen 2.1.1 server on Debian
and PG 9.0. Authentication is successful using the web UI, but using
the 2.1.1 client, the software yields the following error...Any help?
Thaks,
Drew
Please open a helpdesk ticket and include the following text:
Mon Jan
