On Fri, Jan 27, 2006 at 08:42:43PM +1000, Paul Gear wrote:
> Hi folks,
>
> I've just created a new installation of Emilda using the Debian package
> repository (great job, David!), and i have a few questions.
Thanks for using it. :)
> 1. http://www.emilda.org/node/36 seems to imply that quite a bit of
> setup is required in order to use zebra. How much of this is done for
> me by using the Debian package? (Obviously the choosing a file location
> part is done, but what else?)
If you decided to configure emilda during installation (or via
'dpkg-reconfigure -plow emilda'), everthing should be done except for
running http://localhost/emilda/setup.php and creating
/etc/emilda/config as instructed at the bottom of that web page.
/usr/share/doc/emilda/README.Debian has a few more details on this for
the case that you wanted to do a manual setup.
> I guessed just the init, update records, and commit commands at the end,
> so i tried them and they worked, but i still get the following error
> when i try to add a book:
>
> YAZ error: 109 (Database unavailable) (Host: localhost:9999/Default)
> (Query: @attr 5=100 @attr 1=7 0840720300 )
>
> The corresponding error in the /var/log/idzebra/emilda.log is:
>
> 20:18:19-27/01 zebrasrv [request] Search 1 RPN: @attrset Bib-1 @attr 1=7
> @attr 5=100 0840720300 ERROR [109] Database unavailable--Default
>
> On my only previous Emilda installation, i can't remember having to
> touch any of these settings - maybe they didn't work?
I think all emilda users receive this exact error with a new (empty)
emilda data store. Do you still get this after adding at least one
book?
> 2. I'd really like to add a some more appropriate Z39.50 servers to my
> installation, but i know almost nothing about MARC, and the YAZ
> attribute replacement tables in /etc/emilda/z3950-servers.ini are
> gibberish to me. :-)
>
> I've searched in vain for documentation on this file's format. Can
> anyone point me to something to work from? Even better would be sample
> entries for popular Z39.50 servers. ;-)
To conform to File System Hierarchy standards (required by Debian
policy), I converted some of the php code into this format so that
configuration and code were separate.
The format is standard ini file format. Hopefully, it is clear to
compare this file with what is provided by the emilda developers:
http://cvs.sourceforge.net/viewcvs.py/emilda/src/lib/MARC.inc?rev=1.51.2.8&only_with_tag=EMILDA_1_2_BRANCH&view=auto
The more complicated part is to figure out which servers support which
kind of searches on which attributes and mapping those to what is used
by the emilda installation.
I am not an expert in this. But hopefully some documentation can be
seen at:
http://www.indexdata.dk/yaz/doc/tools.tkl
--
Encrypted Mail Preferred:
Key ID: 8527B9AF
Key Fingerprint: E1B6 40B6 B73F 695E 0D3B 644E 6427 DD74 8527 B9AF
Information: http://www.gnupg.org/
ASCII ribbon campaign:
() against HTML email
/\ against Microsoft attachments
Information: http://www.expita.com/nomime.html
|
