There's a largish library that is thinking about using Koha. They've come up with a long list of questions that they'd like answered, and I'd like to get some other peoples feedback before I start answering. Please have a look at these, and reply to those that you feel comfortable talking about. thanks, -pate ----------------------Questions---------------------------- 1 -- Which operating system, or choice of systems, does the proposed library automation system run on? 2 -- Is system administration done with command lines or a graphical module? We should see it. 3 -- What is the backup utility? Does it use tapes? 4 -- Does the system have its own file and disk maintenance procedures? If so, how are they performed? 5 -- What administrative functions or upgrades require the system to be off-line, and for how long? 6 -- Is there a backup module for circulation in case the system is down? 7 -- Describe the way customer support works, what it covers, and hours of service. 8 -- What is the indexing capability for the catalog? How many indexes can we have? Can they be customized? 9 -- Describe the capacity for integrating selfcheck machines with the system. Is it SIP1/SIP2/NCIP compliant? 10 -- What report writing capability does the system have? 11 -- What "canned" reports are available? 12 -- Is there an API available? Can we develop applications that can directly access the database? 13 -- Is there a function for electronic ordering, such as from Baker and Taylor? Does B&T support your ordering module? 14 -- What flexibility is there for customizing the catalog? Can the catalog engine search external databases? 15 -- Is the system client-server or web based? 16 -- What is the capacity for e-mail functions, including e-mail notices? 17 -- Can the system integrate library fines with external payment interfaces (library cards, etc.)? 18 -- Which RFID vendors have successfully integrated with your system? 19 -- Can receipt printers work with the system? 20 -- Have you converted DRA Classic sites in the past? Describe your conversion process. What data can you *not* convert? 21 -- Can your system work with Epixtech's URSA module for inter-library loan? 22 -- Do you provide an integrated point of sale module? 23 -- What functions can our public do from home via our catalog -- pay fines? renew items? place requests? renew cards? 24 -- Does the catalog have multi-lingual support? 25 -- What are the options, or lack of, regarding database privacy (reading records of the public, retrospective history, etc.)? 26 -- Is there support for access via hand-helds? 27 -- What is the database platform? Proprietary? Oracle? Informix? SQL? Something else? 28 -- Can customized fields be added to either item or patron records? 29 -- What flexibility is there for searching item and patron records? Can additional item and patron fields be made searchable? 30 -- Can the system store content (not just indexing) for digital materials, photographs, e-books, digital audio? 31 -- Can staff get real-time statistics on demand? 32 -- Is there any way for users to get automatic bibliographies on request? 33 -- Is there any capacity for debit interfaces with functions such as printing? 34 -- What kind of hardware do you recommend? Does your configuration include RAID? 35 -- What database redundancy is built into the system, in case a disk is lost or corrupted? 36 -- What kind of support do you have for bookmobile operation, eg. a cache of the whole database changed every day? 37 -- Is there support for cover pages, excerpts, etc., such as we can purchase from Syndetic? 38 -- Can the public place requests for titles which are on order? 39 -- Is there integrated selector management -- that is, when you select a title from a database such as OCLC, can it be loaded into the system and ordered? 40 -- How is access managed to OCLC? 41 -- How are long overdue items managed -- patron notices, credit bureau reports, masking from the database, etc.? Does the capacity exist to transfer these items into an auxiliary database? 42 -- Explain the hierarchical nature of database locations (system, agencies, departments, or whatever). 43 -- How are item statuses used? Can they be converted from DRA Classic to the new system? 44 -- What is the procedure for processing lost items? 45 -- What kind of transaction statistics are kept for items? For patrons? 46 -- How does licensing work? How are fees determined? 47 -- Can the system handle consortia? How does this affect licensing fees? 48 -- What can be controlled by the systems calendar (eg. days when items are not due, fines not charged, etc.)? 49 -- What kind of patron delinquency statuses are available? Can patron statuses be converted from DRA Classic? 50 -- Does the catalog allow searching by item (not bibliographic) call numbers? 51 -- What is the hierarchy of the bibliographic database (bibliographic records, call number records, item records)? 52 -- What is the system of classifications for materials (material codes)? Can selfcheck checkouts be limited to specified item classifications? 53 -- Can the system allow automatic charges to patron records as certain classes of items are checked out? Can this feature be used with the selfcheck? 54 -- Is it possible to set up multiple databases within the system? 55 -- Is there a text catalog that can be used for modem access (for people who are not yet on the Internet)? 56 -- Does the system allow tracking between patron categories and item categories for circulation statistics? 57 -- Can fine records for patrons be converted to your system from DRA Classic? Pat Eyler Kaitiaki/manager migrant Linux sys admin the Koha project ruby, shell, and perl geek http://www.koha.org http://pate.eylerfamily.org