ddcc Integrated library system

From Wikipedia, the free encyclopedia

An integrated library systemor Library Automation (ILS), also known as a library management system (LMS),[1][2] is an enterprise resource planning system for a library, used to track items owned, orders made, bills paid, and patrons who have borrowed. An ILS usually comprises a relational database, software to interact with that database, and two graphical user interfaces (one for patrons, one for staff). Most ILSes separate software functions into discrete programs called modules, each of them integrated with a unified interface. Examples of modules might include:

acquisitions (ordering, receiving, and invoicing materials) cataloging (classifying and indexing materials) circulation (lending materials to patrons and receiving them back) serials (tracking magazine and newspaper holdings) the OPAC (public interface for users)

Each patron and item has a unique ID in the database that allows the ILS to track its activity. Larger libraries use an ILS to order and acquire, receive and invoice, catalog, circulate, track and shelve materials. Smaller libraries, such as those in private homes or non-profit organizations (like churches or synagogues, for instance), often forgo the expense and maintenance required to run an ILS, and instead use a library computer system.[citation needed]
Contents
[hide]

o o o o o

1 History 1.1 Pre-computerization 1.2 1960s: the influence of computer technologies 1.3 1970s-1980s: the early integrated library system 1.4 1990s-2000s: the growth of the Internet 1.5 Mid 2000s-Present: increasing costs and customer dissatisfaction 2 Requests for Proposal: preparation, writing, and evaluation 3 Examples 4 See also

5 References 6 Further reading 7 External links

[edit]History [edit]Pre-computerization
Prior to computerization, library tasks were performed manually and independently from one another. Selectors ordered materials with ordering slips, cataloguers manually catalogued items and indexed them with the card catalog system (in which all bibliographic data was kept on a single index card), and users signed books out manually, indicating their name on cue cards which were then kept at the circulation desk. Early mechanization came in 1936, when the University of Texas began using a punch card system to manage library circulation.[3] While the punch card system allowed for more efficient tracking of loans, library services were far from being integrated, and no other library task was affected by this change.

[edit]1960s:

the influence of computer technologies

Following this, the next big innovation came with the advent of MARC standards in the 1960s which coincided with the growth of computer technologies library automation was born.[4] From this point onwards, libraries began experimenting with computers, and, starting in the late 1960s and continuing into the 1970s, bibliographic services utilizing new online technology and the shared MARC vocabulary entered the market; these included OCLC (1967), Research Libraries Group (which has since merged with OCLC), and Washington Library Network (which became Western Library Network and is also now part of OCLC).[5]

[edit]1970s-1980s:

the early integrated library system

The 1970s can be characterized by improvements in computer storage as well as in telecommunications.[6] As a result of these advances, turnkey systems on microcomputers, [7]known more commonly as integrated library systems (ILS) finally appeared. These systems included necessary hardware and software which allowed the connection of major circulation tasks, including circulation control and overdue notices.[8] As the technology developed, other library tasks could be accomplished through ILS as well, including acquisition, cataloguing, reservation of titles, and monitoring of serials.[9]

[edit]1990s-2000s:

the growth of the Internet

With the growth of the Internet throughout the 1990s and into the 2000s, ILS begun allowing users to more actively engage with their libraries through OPACs and online web-based portals, where users

could log into their library accounts to reserve or renew books as well as authenticate themselves for access to library-subscribed online databases. Inevitably, during this time, the ILS market grew exponentially. By 2002, the ILS industry averaged sales of approximately US$500 million annually, compared to just US$50 million in 1982.[10]

[edit]Mid

2000s-Present: increasing costs and customer dissatisfaction

By the mid to late 2000s, ILS vendors had increased not only the number of services offered but also their prices, leading to some dissatisfaction among many smaller libraries. At the same time, open source ILS was in its early stages of testing. Some libraries began turning to such open source ILSs as Koha and Evergreen. Common reasons noted were to avoid vendor lock in, avoid license fees, and participate in software development. Freedom from vendors also allowed libraries to prioritize needs according to urgency, as opposed to what their vendor can offer.[11] Libraries which have moved to open source ILS have found that vendors are now more likely to provide quality service in order to continue a partnership since they no longer have the power of owning the ILS software and tying down libraries to strict contracts.[12] This has been the case with the SC LENDS consortium. Following the success of Evergreen for the Georgia PINES library consortium, the South Carolina State Library along with some local public libraries formed the SC LENDS consortium in order to share resources and to take advantage of the open source nature of the Evergreen ILS to meet their specific needs.
[13]

By October 2011, just 2 years after SC LENDS began operations, 13 public library systems across

15 counties had already joined the consortium, in addition to the South Caroline State Library. Librarytechnology.org does an annual survey of over 1,500 libraries and noted in 2008 2%[14] of those surveyed used open source ILS, in 2009 the number increased to 8%[15] and in 2010(most recent year available) 12%[16] of the libraries polled had adopted open source ILSs.

[edit]Requests

for Proposal: preparation, writing, and evaluation

When setting up a new ILS, the library will need to prepare a Request for Proposal in order to obtain information from ILS vendors about their products and the suitability of these products for the specific library. The process itself is long and technical, with various sections devoted to legalities, etc. However, there are several templates available to make the process slightly easier. Some additional information on how to prepare an RFP specifically for an ILS has been prepared by the American Library Association and can be found on their wiki here: http://wikis.ala.org/professionaltips/index.php/Request_for_Proposal_%28RFP%29 . The classic source and model RFP comes from a 1999 publication in ALA's Library Technology Reports.[17] This extremely detailed document, prepared by Richard W. Boss, is 107 pages long, comes with a helpful introduction and explains how to use the Model RFP. If your library does not own this back issue, it is

accessible through a paid ProQuest subscription. This article was updated in 2003 (volume 39, number 3), although the actual Model was not, and is only available in the 1999 issue. This updated version is available through the ALA Archives. Luckily, many institutions have been willing to share their RFPs for ILS online. Some useful ones for schools are listed: The Southwest Michigan Library Cooperative posted a PDF of a sample RFP for their members to use when looking to purchase a new ILS. The Toronto Catholic District School Board posted their actual RFP for an ILS, which was sent out to vendors in January 2012. This RFP covers most of the legal requirements, and gives a good example of background information that vendors require; however, it is missing critical information that the vendors should fill out regarding technical aspects of the ILS. Another source of useful information are the Library Journal annual reports (see for example, the 2010 report or 2009 report) based on surveys of various types of libraries, asking about their ILS, what services their ILS provide, what modules are supported, etc. Indications of market share are also often included, along with direct quotes from the surveys with user opinions. These reports, available on the Library Journal website (Archives), can be useful to librarians looking to send out RFPs for ILS, as they will be able to see at a glace which vendors provide the services and modules they are looking for and contact these select few in particular. This will help to avoid going through numerous responses to RFPs, which must be considered equally and carefully. Additional ILS reviews are widely available online; simply typing in the name of the ILS followed by the term "review" should retrieve many relevant documents which can help both in deciding who to send RFPs to and also in evaluating the responses to the RFP.

Library Management System

Overview : Library is regarded as the brain of any institute; many institutes understand the importance of the library to the growth of the institute and their esteem users (students). LMS support the general requirement of the library like acquisition, cataloguing, circulation. Library project system that offers many flexible and convenient features, allowing librarians and library users to maximize time and efficiency. Library System gives the all detailed information about students, staff and books. It will track on the how many books available in library and books issued to the students. It shows popular book among the students. It will

provide book lost in library. It keeps the record of the suppliers and book binders. It generates MIS reports for management. Our software is customizable for any library requirement. Features of library management system:

Only basic knowledge of computers is required for operation of Library Management System. As it has user-friendly application interface. Library Management System is Customizable and User Configurable. An inbuilt Settings module makes Library Management System flexibility to cater to diverse organizational needs. It is build on .NET technology - one of the most latest and upcoming Technologies in the fieldb

of Information Technology, which makes you a forerunner in the world of Information technology.

Library Management System brings information to the user's desktop through integration across all modules. Library Management System has pre-defined reports. These are used for normal reporting as well as Administration & Staff development purpose. Additionally, Library Management System can be easily customized for their own customized reports. Staff as well as student record is maintained Newspapers attendance is maintained Automatic fine fees calculation Keeps record of suppliers and binders Customized Report designing Configurable as per users requirements

Why you need it:

Improved customer service through greater access to accurate information. Increased productivity and job satisfaction among staff members as it eliminates duplication of effort. More economical and safer means of storing and keeping track of information. Easier access to Information like management reports and stock etc, as well as more accurate and faster results from statistical analyses. Reduces errors and eliminating the ennui of long and repetitive manual processing. Greater accountability and transparency in operations. Improved efficiency and effectiveness in administration and management as it has unprecedented access to real-time information. More reliable security for sensitive and confidential information. Appropriate knowledge-based action and intervention can now take place in a timelier manner.

SYSTEM IMPLEMENTATION Implementation is the stage in the project where the theoretical design is turned into a working system. The implementation phase constructs, installs and operates the new system. The most crucial stage in achieving a new successful system is that it will work efficiently and effectively. There are several activities involved while implementing a new project they are End user training End user Education Training on the application software System Design Parallel Run And To New System Post implementation Review End user Training: The successful implementation of the new system will purely upon the involvement of the officers working in that department. The officers will be imparted the necessary training on the new technology. End User Education: The education of the end user start after the implementation and testing is over. When the system is found to be more difficult to under stand and complex, more effort is put to educate the end used to make them aware of the system, giving them lectures about the new system and providing them necessary documents and materials about how the system can do this. 14 Training of application software: After providing the necessary basic training on the computer awareness, the users will have to be trained upon the new system such as the screen flows and screen design type of help on the screen , type of errors while entering the data , the corresponding validation check at each entry and the way to correct the data entered. It should then cover information needed by the specific user or group to use the system. Post Implementation View: The department is planning a method to know the states of t he past implementation process. For that regular meeting will be arranged by the concerned officers about the implementation problem and success SOFTWARE TESTING Is the menu bar displayed in the appropriate contested some system related features included either in menus or tools? Do pull Down menu operation and Tool-bars work properly? Are all menu function and pull down sub function properly listed ?; Is it possible to invoke each menu function using a logical assumptions that if all parts of the system are correct, the goal will be successfully achieved .? In adequate testing or non-testing will leads to errors that may appear few months later. This create two problem 1. Time delay between the cause and appearance of the problem. 2. The effect of the system errors on files and records within the system 15 The purpose of the system testing is to consider all the likely variations to which it will be suggested and push the systems to limits. The testing process focuses on the logical intervals of the software ensuring that all statements have been tested and on functional interval is conducting tests to uncover errors and ensure that defined input will produce actual results that agree with the required results. Program level testing, modules level testing integrated and carried out. There are two major type of testing they are 1) White Box Testing. 2) Black Box Testing. White Box Testing White box some times called Glass box testing is a test case design uses the control structure of the procedural design to drive test case. Using white box testing methods, the following tests where made on the system A) All independent paths within a module have been exercised once. In our system, ensuring that case was selected and executed checked all case structures. The bugs that were prevailing in some part of the code where fixed b) All logical decisions were checked for the truth and falsity of the values. 16

Black box Testing Black box testing focuses on the functional requirements of the software. This is black box testing enables the software engineering to derive a set of input conditions that will fully exercise all functional requirements for a program. Black box testing is not an alternative to white box testing rather it is complementary approach that is likely to uncover a different class of errors that white box methods like.. 1) Interface errors 2) Performance in data structure 3) Performance errors 4) Initializing and termination errors

OUTPUT DESIGN Outputs from computer systems are required primarily to communicate the results of processing to users. They are also used to provide a permanent copy of these result for latter consultation .Computer output is the most important and direct source of information to the users. Designing computer output should proceed in an organized well through out the manner. The right output must be available for the people who find the system easy o use. The outputs have been defined during the logical design stage. If not, they should defined at the beginning of the output designing terms of types of output connect, format, response etc, Various types of outputs are 12 External outputs Internal outputs Operational outputs Interactive outputs Turn around outputs All screens are informative and interactive in such a way that the user can full fill his requirements through asking queries. DATABASE DESIGN The general theme behind a database is to handle information as an integrated whole. A database is a collection of interrelated data stored with minimum redundancy to serve many users quickly and effectively. After designing input and output, the analyst must concentrate on database design or how data should be organized around user requirements. The general objective is to make information access, easy quick, inexpensive and flexible for other users. During database design the following objectives are concerned:Controlled Redundancy Data independence Accurate and integrating More information at low cost Recovery from failure Privacy and security Performance Ease of learning and use 13 SYSTEM ANALYSIS EXISTING SYSTEM: System Analysis is a detailed study of the various operations performed by a system and their relationships within and outside of the system. Here the key question is- what all problems exist in the present system? What must be done to solve the problem? Analysis begins when a user or manager begins a study of the program using existing system. During analysis, data collected on the various files, decision points and transactions handled by the present system. The commonly used tools in the system are Data Flow Diagram, interviews, etc. Training, experience and common sense are

required for collection of relevant information needed to develop the system. The success of the system depends largely on how clearly the problem is defined, thoroughly investigated and properly carried out through the choice of solution. A good analysis model should provide not only the mechanisms of problem understanding but also the frame work of the solution. Thus it should be studied thoroughly by collecting data about the system. Then the proposed system should be analyzed thoroughly in accordance with the needs. System analysis can be categorized into four parts. System planning and initial investigation Information Gathering Applying analysis tools for structured analysis 3 Feasibility study Cost/ Benefit analysis. In our existing system all the transaction of books are done manually, So taking more time for a transaction like borrowing a book or returning a book and also for searching of members and books. Another major disadvantage is that to preparing the list of books borrowed and the available books in the library will take more time, currently it is doing as a one day process for verifying all records. So after conducting the feasibility study we decided to make the manual Library management system to be computerized. 4 PROPOSED SYSTEM Proposed system is an automated Library Management System. Through our software user can add members, add books, search members, search books, update information, edit information, borrow and return books in quick time. Our proposed system has the following advantages. User friendly interface Fast access to database Less error More Storage Capacity Search facility Look and Feel Environment Quick transaction All the manual difficulties in managing the Library have been rectified by implementing computerization. 5 FEASIBILITY ANALYSIS Whatever we think need not be feasible .It is wise to think about the feasibility of any problem we undertake. Feasibility is the study of impact, which happens in the organization by the development of a system. The impact can be either positive or negative. When the positives nominate the negatives, then the system is considered feasible. Here the feasibility study can be performed in two ways such as technical feasibility and Economical Feasibility. Technical Feasibility: We can strongly says that it is technically feasible, since there will not be much difficulty in getting required resources for the development and maintaining the system as well. All the resources needed for the development of the software as well as the maintenance of the same is available in the organization here we are utilizing the resources which are available already. Economical Feasibility Development of this application is highly economically feasible .The organization needed not spend much m one for the development of t he system already available. The only thing is to be done is making an environment for the development with an effective supervision. I f we are doing so , we can attain the maximum usability of the corresponding resources .Even after the development , the organization will not be in a condition to invest more in t he organization .There fore , the system is economically feasible. 6 SYSTEM REQUIREMENTS This management system can be used in windows 98, Windows2000, Windows XP and Windows NT, supported for other platform such as Applet, Macintosh and UNIX. The system must be running Windows 98, Windows 98 or Windows NT4.0 operating system and must meet the following hardware requirements.

For Windows 95 based computers , a 486 / 66 MHz or higher processor with 8MB For Windows 98 based computers , a 500/88MHz or higher processor with 32 Mb of RAM For Windows NT based computers , a 488 / 66 MHz or higher processor with 16 MB of RAM For Windows 200 based computers , a 700/850 MHz or higher processor with 512 MB of Ram 7 DATA FLOW DIAGRAM 8

SYSTEM DESIGN INPUT DESIGN Input design is the process of converting user-oriented input to a computer based format. Input design is a part of overall system design, which requires very careful attention .Often the collection of input data is the most expensive part of the system. The main objectives of the input design are 1. Produce cost effective method of input 2. Achieve highest possible level of accuracy 3. Ensure that the input is acceptable to and understood by the staff. Input Data The goal of designing input data is to make enter easy, logical and free from errors as possible. The entering data entry operators need to know the allocated space for each field; field sequence and which must match with that in the source document. The format in which the data fields are entered should be given in the input form .Here data entry is online; it makes use of processor that accepts commands and data from the operator through a key board. The input required is analyzed by the processor. It is then accepted or rejected. Input stages include the following processes Data Recording Data Transcription Data Conversion Data Verification 11 Data Control Data Transmission Data Correction One of the aims of the system analyst must be to select data capture method and devices, which reduce the number of stages so as to reduce both the changes of errors and the cost .Input types, can be characterized as. External Internal Operational Computerized Interactive Input files can exist in document form before being input to the computer. Input design is rather complex since it involves procedures for capturing data as well as inputting it to the computer.