Bess Sadler wrote:
Thank you so much for all your help! I can now add books to my system. I
will try to get Emilda running on Solaris and on Mac OSX, too, if you want
some more testing done.
This would be terrific, as we currently do not have access to these
platforms. If You could report on how it went, and feel free to ask more
if You run into problems.
Are you sick of me yet? I have a few more questions about how Emilda
works.
Certainly not; we are glad to have someone asking questions for possibly
all the people out there who have not found the time to do so.
1. I see on the search screen the option to search in all libraries or in
a specific library, but I can't find any way to add more libraries, or to
specify which library a book belongs to. Will this come in the future, or
is it based on how my zebra records are set up, perhaps?
This is a dilemma that we are tackling by the next release of Emilda;
currently it is only possible to add new "library instances" by
performing an SQL query in the Emilda database. This is to prevent the
current users of Emilda to add more instances than they are allowed.
This is of course not durable, and will change by 1.2 of Emilda.
If You however now want to add another library instance, You can consult
the emilda.sql file supplied with Emilda, where it in the last lines
adds an instance. Copying that line and modifying it for Your needs
should suffice, and then of course issuing that command in the MySQL
command shell.
2. Where are the subject headings? Again, is this based on my zebra setup?
I do not know how well You have studied the Emilda source code, but with
the current setup of MARC-data presentation it is actually not possible
to add "subject added entries" (i sincerely hope we are talking about
the same thing =)). The implementation of subject added entires requires
rewriting the entire MARC-data hadling, which is due to either 1.2 or
1.3. We have performed some modifications to the PHP/YAZ library
supplied by Indexdata (http://www.indexdata.dk) and we currently are
discussing how to implement these changes into an official release of
PHP/YAZ. Without these changes we cannot implement the alterations to
the MARC-data hadling system the way we have planned, so we have to wait
a while with this.
3. Currently, as a user, when I search for a book there is no way to
reserve the book after I've found it. Is that a coming feature?
This is currently only partially present; the client we supplied Emilda
1.0 to wanted only to be able to reserve books that have been borrowed,
i.e. if the book You want to reserve has been borrowed by another user
it is possible to reserve it, otherwise not. This we intend to change in
some way by 1.2, so that it would perform as best suitable to other
"clients". One of the ways to approach the problem would be to allow
books to be reserved even though they have not been borrowed.
4. Is there a documentation project in progress to answer questions like
these? If so, do you want help writing it? If not, do you want me to start
one?
We currently are planning to set up some sort of development area for
Emilda, where a documentation project would be available. Due to a
strict schedule I cannot promise any dates when this environment would
be available, but when it is, we would be most thankful if You could
help us write this documentation, especially when it comes to platforms
that we have not the resources to test.
Even though I cannot promise any dates, there should be coming something
up the next follwing weeks, so if You could until then preliminary
gather the information You have and then add into the system when it is
present, this would be terrific.
5. If some of the above features are not on your list of planned
additions, could I help the project by writing them myself? I joined the
developers list, but other than that I'm not sure what to do to get
involved.
Due to the lack of a real development area, there has not been any real
activity on the development section of Emilda, other than internally of
course. But once we have the site/area up and running we hope to get
more active and more precise on what could be done and how. We will of
course post development related issues on both Emilda lists, so stay
posted for evolvement in this area.
As 1.1 is pourly documented, and maybe not entirely ready for involving
external developers on an individual level, we hope to make release 1.2
so well documented that it would be possible to have developers involved
without having to explain the entire functional philosophy to all parts
involved.
Again, thank you for such a beautiful package and I'm quite excited about
using it.
We hope it suits Your needs, and maybe even more, and please, spread the
word if You have contacts who might be interested in the project.
I hope this rather lengthly answer gives You the desired information,
and if I came totally off track, You can always resend old questions or
ask new ones =)
Best Regards,
Bess Sadler
_______________________________________________
Emilda mailing list
Emilda@xxxxxxxxxxxxxxxxxx
http://lists.realnode.com/mailman/listinfo/emilda
--
Christoffer Landtman
Oy Realnode Ab
Partner, Sales
+358 (0)41 510 1073
landtman@xxxxxxxxxxx
www.realnode.fi
|