Page 50 - DLIS007_LIBRARY AUTOMATION

Unit 3: Basic Knowledge of Library Software

Fund accounting Notes
Inter library loan
Bills and fines
Multimedia files

Interoperability and crosswalk
5. LMS must provide continuous backup in suitable media (as per the choice of libraries) so
that all transactions can be recovered to the point of failure.

6. LMS must be compliant with the following standards:
Z39.50 information interchange format
MARC 21, UNCODE (UTF-8 OR UTF-16)

Z39.71 holdings statements
Z39.50 information retrieval service (client and server version 3)
EDIFACT (EDI standard)
IEEE 802.2 and 802.3 Ethernet
HTTP, TCP/IP, Telnet, FTP, SMTP

7. The LMS should be based on web-centric architecture and extend support for a range of
multi-user and multitasking operating systems and RDBMSs.
8. The LMS must be compliant with UNICODE standard for multilingual support and RFID
for inventory management and self-issue/return facility.
9. Vendor/Developing group should provide training to enable library staff to familiarise
with system functions and operation should provide full and current system documentation
in hard copy and in machine-readable form suitable for online distribution, and the LMS
should include extensive online help for users and staff.
10. LMS must support multiple hardware architecture in terms of server, network
infrastructure, PC-workstations and peripheral devices.

11. LMS must be supported with regular maintenance and on-call service, periodical software
upgrades, continuous R&D, trouble-shooting of third party software such as database
package and the library automation package, distribution of problem fixes/patches and
emergency services for system failures and disaster recoveries.
12. The package must provide security to prevent accidental or unauthorised modification of
records through the establishment of access privileges unique to each user on the system
and restriction of specific functions to specific users.

13. LMS should provide graphical user interface, including but not limited to extensive online
help, user self-service and personalisation features. The system should be supported with
PC-based alternative that will allow circulation to continue in the event of system failure,
communication failure and downtime required for maintenance.

3.2.2 Functional Requirements

These are the minimum essential features to be supported by each functional units or modules
of any modern LMS:

LOVELY PROFESSIONAL UNIVERSITY 45