----------------------------Original message----------------------------
I am particularly interested in this problem as we are also about to launch
into automating our map library.  We are going to use LibraryWorks by
CASPR, because that is what we are using for our main (book) library.  We
haven't started yet as we just got the site liscence from CASPR (although
we have been using the system for books for two years now).  The things I
expect to like about the system are these:
 
1.  The files do not require a mainframe.  The whole program lives on one
Mac (now it will live on two Macs), which are also used for a multitude of
other purposes (word processing, telnet, e-mail, etc.).  CASPR also makes a
UNIX version, and if you have a mixed network (as we have) supposedly the
two versions are compatible with each other (we haven't tested that feature
yet).
 
2.  The system comes with integrated modules for cataloging, circulation,
serials control, etc. and is relatively cheap.  Support is also quite
cheap.  The user interface (LibraryBrowser) is purchased separately, but is
also reasonably priced.
 
3.  The system is pretty easy to use.  I have not cataloged maps into it
yet, but it has a nice cataloging template for maps, and, having cataloged
books, serials, audiotapes and videotapes into the system, I know the
templates are clear and easy to use.  Also it imports nicely from OCLC.
 
4.  The system allows you to set up separate files.  We already do that for
interlibrary loan, and it is what we expect to do for maps, so that the
records for our map collection will be separate from the records for our
regular collection.  The interlibrary loan file we set up has allowed us to
test this out, and it works beautifully.  You can set up as many separate
files as you like.
 
However, there are things I don't like about the system.  There are
considerable bugs, and the company is slow to get these straightened out.
For instance, for some reason the system sometimes attaches some of our
serials holdings records to other records.  This makes it very dicey to
trust your serials control.  Also, the system currently allows only one x
subject tag per subject entry.  So you can have "Air--Pollution"  but you
cannot have "Air--Pollution--Measurement".  They expect to change this some
day.  We have not seen it changed in two years so far, and it is a rather
significant limitation.  On the other hand, there is no limitation of size
in the "Notes" field.  I have worked with other systems where there is a
limited notes field, and it is not good (I would particularly see it as a
problem with maps).
 
So there it is, for what it is worth.  As I say, I am familiar with the
system, but I have not, as yet, used it for maps, but I don't expect it
will present any special problems.  I will be interested to note what other
people have to say about their systems.
 
One thing we are toying with is whether to handle our topo maps (the vast
bulk of our collection) as one serial record (which I understand to be the
LC rule) or whether to enter each map as a separate record, or some
combination of the two (for example, topos of each state entered as a
series).  If you have any thoughts about this problem, I would love to hear
them.  Stephanie.
 
Stephanie Bianchi, ERL-C Library, (503)-754-4731.