Mike Doughney wrote:
I'm happy to let you all know that I was able to install today's release,
and that corrected a great number of strange problems I've been having in
getting Emilda set up over the past few days. I'm now to the point that I
can get most of the system to function, except for a few lingering problems
which seem related to the interface with the Zebra server, as follows:
'Add books to the native database' seems OK, then
'Add Book - Retrieved Book Info' on a successful book lookup has error
message at top in red letters:
"Unsupported Use attribute: 7"
Book can be successfully added. Edit before adding works too.
'Edit Book - Step 2' returns blank fields, and a "Unsupported Use
Attribute: 12" at top of page.
Quick Search by ID on a valid ID returns only the following:
-----
Unsupported Use attribute: 12
No Books found!
-----
Quick or Advanced Search on an author or title works without errors; then
Extended Book Info from any of those results shows "Unsupported Use
attribute:
12" along with the book info.
Clicking on "Show MARC" returns a blank popup with the following in
it:
-----
Unsupported Use attribute: 12
Notice: Undefined offset: 0 in
(path...)/emilda/book_info.php on line 33
(and a "close window" button)
----
I suspect that there is a Zebra configuration problem causing all this. I'm
using the sample USMARC configuration that comes with the Zebra server, and
the USMARC files (with all the files in the 'tab' directory that comes with
yaz) are in a location specified in the zebra.cfg file. Everything looks
normal here. Some web searches on the string 'unsupported use attribute'
refer to this kind of error but don't say much about how to correct it,
other to make sure that all the USMARC files are accessible to the zebra
server.
Hello,
All these errors indeed have to do with the Zebra configuration,
especially with the files in the tab/ sub folder. This is pure
sloppiness that we have not put the sample configuration files on the
web page, and this will be done still today.
What the error tells You is that the PHP/YAZ-client searches using an
attribute that is not defined by default in the Zebra configuration, and
can as such not return anything.
I'm using version 1.3.14 of the Zebra server, along with mysql 4.1 and php
4.3.4. The Perl DBD and php have been recompiled with the mysql 4.1 client
libraries. The PHP configuration can be seen at
http://mtd.com/test/test.php.
As we stated in the release notes, version 1.3.14 of Zebra is _NOT_ to
be used with Emilda, as it contains a bug that will break the MARC
management functions. In version 1.3.15 this anomaly has been fixed, and
as such it is desired that You would upgrade to this particular version
as Your Emilda environment will be messy if using version 1.3.14 of Zebra.
MySQL released in mid-December a bug-patch-version of MySQL 4.1, version
4.1.1 to be more specific, and it is recommended to upgrade to this
version if possible. We have noticed some strange behaviour of version
4.1 and can with good references tell that 4.1.1 seems far more stable.
If there are any particular issues You had installing Emilda that You
think others might want to know, please share them with us so that we in
future can make the Emilda installation process smoother.
Any help fixing these last few problems is much appreciated.
I hope these hints will help You, and I personally will put the sample
configurations online as soon as possible. I will make an announcement
on this list when the samples are online. If You want to attempt to
solve these issues independently, there are hints in older messages in
the "Emilda"-list archives.
And yes, please subscribe to the Emilda lists if You want to stay posted
on future Emilda announcements and developments.
Best regards,
_______________________________________________
Emilda-announce mailing list
Emilda-announce@xxxxxxxxxxxxxxxxxx
http://lists.realnode.com/mailman/listinfo/emilda-announce
--
Christoffer Landtman
Oy Realnode Ab
Partner, Sales
+358 (0)41 510 1073
landtman@xxxxxxxxxxx
www.realnode.fi
|
