"That Other Andrew" wrote:
'But VuFind is open source ... it is up to the community to make it
better.'
I just want to delurk for a moment to highlight this point. VUFind
looks *fantastic*, even in beta, and with some community development it
will simply rock. I understand that a lot of this criticism is
constructive, but I've often felt that a big impediment to library
innovation is our insistence on perfection right out of the box. I
have, as I'm sure we all have, seen many innovative, and some merely
useful, ideas wither on the vine because a librarian could find a
combination of factors that (*gasp*) might not lead as precisely to one
catalog record as the "old" system.
Personally, I'm interested in hearing more about implementation and
testing experiences. Is there a resource (besides this list) for
libraries who want to kick the tires a bit?
--
Andrew Ashton
Systems Librarian
Scribner Library, Skidmore College
(518)580-5505
>
> "The Peloponnesian War and the Future of Reference, Cataloging, and
> Scholarship in Research Libraries"
> http://guild2910.org/Peloponnesian%20War%20June%2013%202007.pdf
>
> I understand that VuFind relies on the real catalogs it accesses via
> "drivers". So, if a target catalog doesn't have browse lists, VuFind
> cannot provide them? Or does it do its own indexing?
>
VuFind does not rely on catalog and that is one of the core foundations
of the system. It has it's own index. However an implementation of
VuFind would be rather basic with out a catalog for it to connect to.
This is where the drivers come into play. The catalog supplies real
time status information on the records. Also the ability to hold or
recall an item.
Hope this clears things up
Andrew
Received on Tue Jul 24 2007 - 07:06:26 EDT