ILSR
Vendor Survey
The first
table shows the various database management systems being
used to develop the systems, whether the systems are
relational and/or ODBC compliant. While some vendors
continue to use proprietary development tools, many are
now using tools commonly found in many organizations. For
example, Oracle is being used (or its use is planned) by
many of the vendors. This is good news to many IT shops
within organizations who would prefer that the library
purchase a system that they already know how to support.
It appears
that most vendors are now developing systems that are
both relational and ODBC compliant. A relational database
is simply defined as a database that consists of more
than one table of data where the tables are related by
common fields. This type of structure allows users to
enter data once for many uses. For example, a table of
patron records could be used to circulate materials,
route subscriptions or track purchases of books for
individual researchers. Each patron record would contain
a unique identifier. Every time the patron checked out a
book, that ID would be entered into a circulation record
tying the patron's name, address, etc. to the circulated
item. The ID could also be entered in serial routing
records or acquisition records linking the patron's name,
etc. to routing slips or purchases. The relationship
between the records reduces the time needed to maintain
the database (you don't have to type the patron's full
name, address, etc.) and the disk space needed to store
the data.
ODBC stands for Open Database Connectivity, a
standard used for accessing databases without the
proprietary software that was used to develop the
databases. For example, a system that is ODBC compliant
would be capable of accessing data through other
applications that are ODBC compliant (i.e., Excel for
acquisition spreadsheets) or interfaces developed with
tools like Visual Basic, CGI, etc.
Vendor Name
|
DBMS used in development?
|
Relational?
|
ODBC Compliant?
|
Atlantic Rim Information Systems,
Inc.
|
Proprietary
|
No
|
No
|
Aurora Information Technology
|
MS Access, MS SQLServer, and Oracle.
|
Yes
|
Yes
|
Best-Seller Inc.
|
Proprietary database but have
announced ORACLE support for the year 2000.
|
No
|
Yes
|
BLCMP Library Services Ltd.
|
Sybase
|
Yes
|
Yes
|
Brodart Library Automation
|
Proprietary
|
Yes
|
No
|
CARL Corporation
|
Tandem’s ENSCRIBE
|
Yes
|
Yes
|
CASPR Library Systems, Inc.
|
The MARC Database Engine (MDE)
|
No
|
No
|
Chancery Software Ltd.
|
Proprietary
|
No
|
No
|
Comstow Information Services, Inc.
|
Progress Software
|
Yes
|
Yes
|
Contec Group International Ltd.
|
Faircom C-Tree
|
Yes
|
Yes
|
Cuadra Associates
|
STAR
|
Yes. It is a flat-file system with
relational capabilities.
|
No
|
DIAKON Systems
|
DBisam by ElevateSoft
|
Yes
|
No
|
ELiAS N.V. Extended Library Access
Solutions
|
Oracle
|
Yes
|
Yes
|
EOS International
|
Q Series: Oracle; MS SQL Server
GLAS: Visual Objects
|
Q Series: Yes
GLAS: No
|
Q Series: ODBC calls from other
applications can be made to the Q Series
database.
GLAS: Yes
|
Ex Libris USA, Inc.
|
Oracle
|
Yes
|
Yes
|
Fretwell-Downing Informatics
|
Oracle
|
Yes
|
Yes
|
Gateway Software Corporation
|
DB2/400
|
Yes
|
Yes
|
| Gaylord Information Systems |
GALAXY: Proprietary
Polaris: Microsoft SQL |
GALAXY: No
Polaris: Yes |
GALAXY: No
Graphical GALAXY: Yes
Polaris: Yes |
Geac Computers, Inc.
|
UniVerse from Ardent Software, Inc.
|
Yes
|
Yes
|
Hardcover Software
|
Microsoft Access; converting to
Microsoft Visual Basic within 6 months.
|
Yes
|
Yes
|
Inmagic Inc.
|
DB/TextWorks
|
No. It features
"relational-like" capabilities
(database linking).
|
Yes.
|
Innovative Interfaces Inc.
|
Proprietary. Phase 3 of the INNOPAC
Millennium development project is to migrate to
an Oracle RDBMS engine
|
No
|
No. In development.
|
International Library Systems
|
Faircom, Notes, Oracle
|
Yes
|
Yes
|
Jaywil Software Development Inc.
|
Microsoft Foxpro
|
Yes
|
No
|
Keystone Systems, Inc.
|
Progress
|
Yes
|
Yes
|
MINISIS Systems Group of the
International Development Research Centre
|
MINISIS (Version 8.04)
|
Yes
|
Yes
|
Nichols Advanced Technologies
|
Proprietary
|
Yes
|
No
|
On Point Inc
|
FileMaker Pro
|
Yes
|
Yes. The ODBC feature requires
FileMaker Pro (TLC doesn't require FileMaker Pro)
|
Open Text Corp., BASIS Division
|
BASIS
|
Yes
|
Yes
|
Precision Computer Service, Inc.
|
Delphi
|
Yes
|
No
|
Robert A. Schless & Co Inc
|
Lotus Notes
|
Yes
|
Yes
|
Sirsi Corp.
|
Informix; Oracle
|
Yes
|
Yes
|
The Library Corporation
|
Oracle
|
Yes
|
Yes
|
TKM Software Limited
|
Ctree
|
No
|
Yes
|
URICA Integrated Systems
|
UniVerse
|
Yes
|
Yes
|
Winnebago Software Co.
|
Faircom
|
Yes
|
Yes
|
Reviews || Vendors || About ILSR || Contacts || Home
Copyright © 1998 Mary Dzurinko &
Nina Platt
Last
revised: April 01, 1999.
Contact webmaster@ilsr.com with questions or comments regarding this
site.
|
