Unit 4 Library Automation: Applications of Open

Total Page:16

File Type:pdf, Size:1020Kb

Unit 4 Library Automation: Applications of Open Library Automation – UNIT 4 LIBRARY AUTOMATION: Software Packages APPLICATIONS OF OPEN SOURCE SOFTWARE Structure 4.0 Objectives 4.1 Introduction 4.2 Open Source Movement 4.2.1 Open Source Software 4.2.2 Open Source Software: Development Path 4.2.3 Open Source Software vs. Commercial Software 4.3 Open Source Software: Philosophy, Principles and Licensing 4.3.1 Philosophy of Open Source Software 4.3.2 Principles of Open Source Software 4.3.3 Licensing of Open Source Software 4.3.4 Open Source and Open Standards 4.4 Open Source Software and Libraries 4.4.1 Use of Open Source Software 4.4.2 Prospects and Problems 4.4.3 Use of Open Standards 4.5 Open Source Software in Libraries: System Level 4.5.1 Open Source Operating System 4.5.2 LAMP Architecture 4.5.3 LAMP Components 4.6 Open Source Software in Libraries: Domain Level 4.6.1 Automated Library System 4.6.2 Digital Library System 4.6.3 Cataloguing Tools 4.6.4 Other Library Activity Tools 4.7 Towards Open Library System 4.8 Summary 4.9 Answers to Self Check Exercises 4.10 Keywords 4.11 References and Further Reading 4.0 OBJECTIVES After going through this Unit, you will be able to: • know what is open source movement and how is it improving computing infrastructure; • understand differences between commercial and open source software; • identify advantages of using open source software and open standards in library system; and • understand the emerging concept of open library system. 141 Library Automation 4.1 INTRODUCTION Present library services are software-centric. As per the availability and distribution policy, software products are divided into two groups – closed source commercial products and open source free to use products. Commercial software in the domain of library activities are available against huge license fees along with separate annual maintenance contracts, updating fees and many other hidden costs. As a result, adaptation of a commercial LMS in library (for example) is not one-time capital expenditure but it leads to considerable recurring expenditure on already strained library budget. Moreover, these commercial LMSs are basically available in a generic or fit-to-all size model and provide no scope for customisation to suite the need of a particular library (Mukhopadhyay, 2008). This is an alarming situation for libraries in India. Libraries are paying huge sum of money to procure commercial LMS but unfortunately not in a position to even change the colour of the user interface. Another serious lacuna is the non- transparent nature of these software in the use of global de jury or de facto standards. Application of open source software in different library activities may be a viable alternative solution to get rid of the problems related with the application of commercial software. The tradition of open source software started with the advent of ARPANET (now Internet) in 1969 and boosted with the development of open source operating systems like GNU Linux. Naturally, one question is coming to your mind – what is open source software and how is it different. According to OSI (Open Source Initiative, 2003) – “Open source promotes software reliability and quality by supporting independent peer review and rapid evaluation of source code. To be certified as open source, the license of a program must guarantee the right to read, redistribute, modify, and use it freely”. Open source software are available freely to end users. Here the term Free has dual meaning – users are given freedom to customise the source code and these software are available free of cost. An open source software is attached with four freedoms – read (source code is available for verification), use (binary code is available for application), modify (source code is available for modification and customisation), redistribute (source code in original or in modified form is available for redistribution). In the area of library services, the greatest benefit of open source software is the opportunity for library professionals to work at the system level and to participate in software development process as co-developers. Fortunately, the domain of library and information science, right from the beginning of the open source movement, is benefited through structured effort and software philanthropy. We have matured ILS like Koha (comparable to any global ILS) from HLT, New Zealand, comprehensive digital library software like DSpace from the MIT, US (with support from HP), Greenstone Digital Library Software (or GSDL) from University of Waikato (presently supported by UNESCO). Apart from these very popular open source software, the arena is presently fielded with an array of promising software like MARCEdit and ISISMARC (MARC cataloguing tools), WEBLIS (ILS based on CDS/ISIS), YAS toolkit (Z39.50 client and server), Lucene and Solr (Text retrieval engines), Unicode-compliant multilingual tools etc. Most of these open source software in the domain of LIS are very transparent in the use of standards and generally deploy open standards for achieving interoperability. 142 This brief introduction gives you idea on open source software and the possibilities Library Automation: Application of Open Source for applications of open source software in enhancing library systems and services. Software Now we are all set to discuss open source software in depth. The discussion mainly cover six areas – 1) history, development, features and advantages of open source; 2) philosophy, principles and IPR issues related with open source; 3) use and advantages of open source software in libraries in general; 4) application of open source software in library activities at the system level; 5) application of open source software in library activities at the domain level; and 6) the emerging concept of open library systems that manages open contents and supported by open standards and open source software. Self Check Exercises Note: i) Write your answers in the space given below. ii) Check your answers with the answers given at the end of this Unit. 1) Enumerate the problems for application of commercial software in libraries. ...................................................................................................................... ...................................................................................................................... ...................................................................................................................... ...................................................................................................................... ...................................................................................................................... 2) What do you mean by open source? Enumerate the freedoms associated with open source. ...................................................................................................................... ...................................................................................................................... ...................................................................................................................... ...................................................................................................................... ...................................................................................................................... 3) List a few open source software in the domain of library services. ...................................................................................................................... ...................................................................................................................... ...................................................................................................................... ...................................................................................................................... ...................................................................................................................... 4.2 OPEN SOURCE MOVEMENT This section covers systematically the definition, scope and origin of open source software including the fundamental differences between open source and close source software. 143 Library Automation 4.2.1 Open Source Software Open Source Software (OSS) is not a new idea. You already know that the open source movement started with the Internet. Recently, technical and market forces joined together to draw a niche role of open source movement. Open source movement has all the potentials to define computing infrastructure of the next century (Marco & Lister, 1987). Open source is a software development model as well as a software distribution model. OSS development follows Linus Torvalds’s (Linus Torvalds is the developer of Linux operating system – an open source system software) style of development – release early and often, delegate everything and be open to the point of promiscuity. Raymond (2001a; 2001b) termed this type of software development as bazaar style of development in comparison with traditional software development process (termed by Raymond as cathedral model), which is carefully crafted by individual wizards or small group of experts working in splendid isolation. The Open Source Initiative (2004), a forum to promote open source software movement as a viable alternative to commercial software claims – “This rapid evolutionary process produces better software than the traditional closed model, in which only a very few programmers can see the source
Recommended publications
  • Open Source Software Vs Proprietary Software Sakshi Singh, Madhvik Verma, Naveen Kumar N
    International Journal of Scientific & Engineering Research Volume 8, Issue 12, December-2017 735 ISSN 2229-5518 Open Source Software Vs Proprietary Software Sakshi Singh, Madhvik Verma, Naveen Kumar N Abstract— Open Source software are the most revolutionizing concept that has been put forth in the Information Technology spectrum. This new release has raised quite a lot of brows, similar to when the Internet was launched. For a very long time, there has been a tiff going on between the Proprietary software and the open source software and how the open source software are taking over their ancestors. The technical experts often indulge in conversations as to which of the two software is better and why. People also get confused as to which type of software can be listed as Open source. In this paper we aim to emphasize that the open source development cycle has been there in the market for quite some time and has a huge user base now, thus giving it a strong hold in the software market. It has encouraged the use of new strategically placed actions which has in turn made a huge base for open source software systems. On the other hand, many experts also suggest that this is just momentary and it will pass over a period of time whereas the proprietary software are there to stay. This paper gives the understanding and recommendations for both the kind of software thus giving the user a proper understanding of which software is suitable for their use and thus they can make a better choice for their purpose.
    [Show full text]
  • Major Open Source ILS Products
    Chapter 3 Major Open Source ILS Products t least four open source ILS products are available system, called Catalist, which was not compliant with the today: Koha, Evergreen, and OPALS. (see table looming Y2K issue. Rather than purchase a commercial A4). While there may be some additional products, system, HLT contracted with a consulting company named these four have emerged as the most widely implemented Katipo Communications to develop a new Web-based sys- and serve as good examples of the current state of the tem. They named this new system Koha, the Maori word art of the open source ILS. While each of these products for gift or donation, and released it as open source, allow- bears a great deal of similarity in approach, they also dif- ing libraries anywhere to use and help develop and sup- fer in features and functionality and in their appeal to port the software. The HLT libraries began using Koha on different types of libraries This section provides detailed January 1, 2000. information regarding each of these systems. A fairly quiet period followed the initial release of Koha, with a few individuals and libraries picking up on the system. No groundswell of interest resulted right away. The initial version of Koha was quite adequate for History and Background three libraries of HLT that together served a commu- Koha nity of about 30,000 residents with a collection of about 80,000 volumes. At that point, Koha did not have some Koha claims the status of being the first open source of the features considered mandatory for most libraries— November/December 2008 November/December library automation system.
    [Show full text]
  • Candidate Resume
    Flat No-a/303, Dharti Park, Behind Shriniwas , Palghar Thane MH 401501 India P : +91 9321883949 E : [email protected] W : www.hawkcl.com Hawk ID # 33574 IT / System Analyst Residential Country : India Nationality : India Resume Title : System Analyst Notice Period : 1 Days EDUCATION Qualification Institute / College /University Year Country B E / B Tech JNTU 2007 India CAREER SUMMARY From Month/ To Month/ Position Employer Country Year Year System Analyst Reputed Company 07/2010 / Software Verus Solutions 10/2007 07/2010 Developer Private Ltd ADDITIONAL CERTIFICATE AND TECHNICAL QUALIFICATION Name Of The Course Course Date Valid Upto Name Of Organisation Current Salary Expected Salary (Monthly In USD): Not Mention (Monthly In USD): Not Mention Additional Skills : Professional Summary • Eight years of experience in design, development, deployment and maintenance of enterprise web applications in ERP, Utility and Marketing domains. • Expertise in Client/ Server and application development using Java, J2ee technologies. • Experienced in leading and mentoring teams with 3-5 members. • Strong knowledge on Object Oriented Programming. • Expertise in web application development using frameworks like Struts , Spring and Hibernate. • Excellent Knowledge of MVC Architecture. • Have worked on application servers like Jboss and Tomcat. • Have worked on build and deploy tools like Ant and Maven. • Have worked on continuous integration tools like Hudson (aka Jenkins). • Have worked on consuming the SOAP web services using Apache Axis API. • Good understanding of Rest Services (RestEasy). • Working knowledge on relational databases like Oracle 10g and Postgresql 8. • Pro-active, highly motivated, results oriented and leadership skills with great team ethics. Technical Expertise • Programming Languages : Java 5/6/7.
    [Show full text]
  • Arxiv:1812.09167V1 [Quant-Ph] 21 Dec 2018 It with the Tex Typesetting System Being a Prime Example
    Open source software in quantum computing Mark Fingerhutha,1, 2 Tomáš Babej,1 and Peter Wittek3, 4, 5, 6 1ProteinQure Inc., Toronto, Canada 2University of KwaZulu-Natal, Durban, South Africa 3Rotman School of Management, University of Toronto, Toronto, Canada 4Creative Destruction Lab, Toronto, Canada 5Vector Institute for Artificial Intelligence, Toronto, Canada 6Perimeter Institute for Theoretical Physics, Waterloo, Canada Open source software is becoming crucial in the design and testing of quantum algorithms. Many of the tools are backed by major commercial vendors with the goal to make it easier to develop quantum software: this mirrors how well-funded open machine learning frameworks enabled the development of complex models and their execution on equally complex hardware. We review a wide range of open source software for quantum computing, covering all stages of the quantum toolchain from quantum hardware interfaces through quantum compilers to implementations of quantum algorithms, as well as all quantum computing paradigms, including quantum annealing, and discrete and continuous-variable gate-model quantum computing. The evaluation of each project covers characteristics such as documentation, licence, the choice of programming language, compliance with norms of software engineering, and the culture of the project. We find that while the diversity of projects is mesmerizing, only a few attract external developers and even many commercially backed frameworks have shortcomings in software engineering. Based on these observations, we highlight the best practices that could foster a more active community around quantum computing software that welcomes newcomers to the field, but also ensures high-quality, well-documented code. INTRODUCTION Source code has been developed and shared among enthusiasts since the early 1950s.
    [Show full text]
  • Open Source Licensing Information for Cisco IOS Release 15.4(1)T
    Open Source Used In Cisco IOS Release 15.4(1)T Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices. Text Part Number: 78EE117C99-15140077 Open Source Used In Cisco IOS Release 15.4(1)T 1 This document contains licenses and notices for open source software used in this product. With respect to the free/open source software listed in this document, if you have any questions or wish to receive a copy of any source code to which you may be entitled under the applicable free/open source license(s) (such as the GNU Lesser/General Public License), please contact us at [email protected]. In your requests please include the following reference number 78EE117C99-15140077 Contents 1.1 bzip2 1.0.0 1.1.1 Available under license 1.2 C/C++ BEEP Core 0.2.00 1.2.1 Available under license 1.3 cd9660 8.18 1.3.1 Available under license 1.4 cthrift-without-GPL-code 0.3.14 1.4.1 Available under license 1.5 CUDD: CU Decision Diagram Package v2.4.1 1.5.1 Available under license 1.6 Cyrus SASL 2.1.0 1.6.1 Notifications 1.6.2 Available under license 1.7 DTOA unknown 1.7.1 Available under license 1.8 editline 1.11 1.8.1 Available under license 1.9 Expat XML Parser - Series 1 v1.2 1.9.1 Available under license 1.10 freebsd-tty-headers n/a 1.10.1 Available under license 1.11 ftp.h 4.4BSD? 1.11.1 Available under license 1.12 inflate.c c10p1 1.12.1 Available under license 1.13 iniparser 2.8 Open Source Used In Cisco IOS
    [Show full text]
  • Vol.22- No.2 (Apr-June, 2015)
    INFLIBNET NEWSLETTER ISSN : 0971- 9849 Vol. 22, No.2 (April to June 2015) Mentions Openness metrics Measuring Research Diversity Citations Social Media PLOS work Time scholarly Indicators Sources filters Social Networks Social Blogs & Media Blogs rapid Analytics significant Speed CapturesAltmetricstools communication articles Scientific Broadness peer-reviewImpact Article Altmetrics: Measuring the Broader Impact of Scientific Research Pallab Pradhan, Scientist-B (LS) IndCat e-PG Pathshala http://indcat.inflibnet.ac.in/ http://epgp.inflibnet.ac.in/ Editorial Board SOUL Helpline INFLIBNET’s Institutional Repositary Tel. : +91-79-23268300 http://ir.inflibnet.ac.in/ Dr. Jagdish Arora VIDWAN N-LIST (E-resources for College) Mrs. Roma Asnani http://vidwan.inflibnet.ac.in/ http://nilst.inflibnet.ac.in/ Mr. Mohit Kumar UGC-INFONET Digital Library Consortium Open Journal Access System (OJAS) http://www.inflibnet.ac.in/econ/ http://www.inflibnet.ac.in/ojs/ Shodhganga Integrated e-content Portal http://shodhganga.inflibnet.ac.in/ http://content.inflibnet.ac.in/ Page No. Contents 1. From Director's Desk 3. Training Programme on SOUL 2.0, INFLIBNET Centre, Gandhinagar 3. User Awareness Programmes on Access to E-resources under N-LIST One-day User Awareness Programme on Access to E-resources under N-LIST, Swami Ramanand Teerth Marathwada University, Nanded, Maharashtra, 22nd May, 2015 4. National Workshops and Specialized Training Programme Two-day Workshop on Ethical Issues & Use of Anti-Plagiarism for Research Integrity, INFLIBNET Centre, Gandhinagar,
    [Show full text]
  • Long-Term Sustainability of Open Source Software Communities Beyond a Fork: a Case Study of Libreoffice Jonas Gamalielsson, Björn Lundell
    Long-Term Sustainability of Open Source Software Communities beyond a Fork: A Case Study of LibreOffice Jonas Gamalielsson, Björn Lundell To cite this version: Jonas Gamalielsson, Björn Lundell. Long-Term Sustainability of Open Source Software Communities beyond a Fork: A Case Study of LibreOffice. 8th International Conference on Open Source Systems (OSS), Sep 2012, Hammamet, Tunisia. pp.29-47, 10.1007/978-3-642-33442-9_3. hal-01519071 HAL Id: hal-01519071 https://hal.inria.fr/hal-01519071 Submitted on 5 May 2017 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Distributed under a Creative Commons Attribution| 4.0 International License Long-term Sustainability of Open Source Software Communities beyond a Fork: a Case Study of LibreOffice Jonas Gamalielsson and Björn Lundell University of Skövde, Skövde, Sweden, {jonas.gamalielsson,bjorn.lundell}@his.se Abstract. Many organisations have requirements for long-term sustainable software systems and associated communities. In this paper we consider long- term sustainability of Open Source software communities in Open Source projects involving a fork. There is currently a lack of studies in the literature that address how specific Open Source software communities are affected by a fork.
    [Show full text]
  • 1. with Examples of Different Programming Languages Show How Programming Languages Are Organized Along the Given Rubrics: I
    AGBOOLA ABIOLA CSC302 17/SCI01/007 COMPUTER SCIENCE ASSIGNMENT ​ 1. With examples of different programming languages show how programming languages are organized along the given rubrics: i. Unstructured, structured, modular, object oriented, aspect oriented, activity oriented and event oriented programming requirement. ii. Based on domain requirements. iii. Based on requirements i and ii above. 2. Give brief preview of the evolution of programming languages in a chronological order. 3. Vividly distinguish between modular programming paradigm and object oriented programming paradigm. Answer 1i). UNSTRUCTURED LANGUAGE DEVELOPER DATE Assembly Language 1949 FORTRAN John Backus 1957 COBOL CODASYL, ANSI, ISO 1959 JOSS Cliff Shaw, RAND 1963 BASIC John G. Kemeny, Thomas E. Kurtz 1964 TELCOMP BBN 1965 MUMPS Neil Pappalardo 1966 FOCAL Richard Merrill, DEC 1968 STRUCTURED LANGUAGE DEVELOPER DATE ALGOL 58 Friedrich L. Bauer, and co. 1958 ALGOL 60 Backus, Bauer and co. 1960 ABC CWI 1980 Ada United States Department of Defence 1980 Accent R NIS 1980 Action! Optimized Systems Software 1983 Alef Phil Winterbottom 1992 DASL Sun Micro-systems Laboratories 1999-2003 MODULAR LANGUAGE DEVELOPER DATE ALGOL W Niklaus Wirth, Tony Hoare 1966 APL Larry Breed, Dick Lathwell and co. 1966 ALGOL 68 A. Van Wijngaarden and co. 1968 AMOS BASIC FranÇois Lionet anConstantin Stiropoulos 1990 Alice ML Saarland University 2000 Agda Ulf Norell;Catarina coquand(1.0) 2007 Arc Paul Graham, Robert Morris and co. 2008 Bosque Mark Marron 2019 OBJECT-ORIENTED LANGUAGE DEVELOPER DATE C* Thinking Machine 1987 Actor Charles Duff 1988 Aldor Thomas J. Watson Research Center 1990 Amiga E Wouter van Oortmerssen 1993 Action Script Macromedia 1998 BeanShell JCP 1999 AngelScript Andreas Jönsson 2003 Boo Rodrigo B.
    [Show full text]
  • Tilburg University Free and Open Source Software Schellekens, M.H.M
    Tilburg University Free and Open Source Software Schellekens, M.H.M. Published in: The Future of the Public Domain Publication date: 2006 Link to publication in Tilburg University Research Portal Citation for published version (APA): Schellekens, M. H. M. (2006). Free and Open Source Software: An Answer to Commodification? In L. Guibault, & B. Hugenholtz (Eds.), The Future of the Public Domain: Identifying the Commons in Information Law (pp. 303- 323). (Information Law Series; No. 16). Kluwer Law International. General rights Copyright and moral rights for the publications made accessible in the public portal are retained by the authors and/or other copyright owners and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights. • Users may download and print one copy of any publication from the public portal for the purpose of private study or research. • You may not further distribute the material or use it for any profit-making activity or commercial gain • You may freely distribute the URL identifying the publication in the public portal Take down policy If you believe that this document breaches copyright please contact us providing details, and we will remove access to the work immediately and investigate your claim. Download date: 27. sep. 2021 Free and open source software: an answer to commodification? Maurice Schellekens 1. Introduction Linux is a PC operating system which is distributed under the General Public License (hereinafter: GPL). The GPL allows for the (royalty-)free use, modification and redistribution of the software. Given these license conditions, Linux users believed they could use the operating system without too many license worries.
    [Show full text]
  • Third-Party Copyright Notices and Licenses
    Third-Party Copyright Notices and Licenses For Intel® Omni-Path Software The following is a list of third party licenses that Intel has operated under in the course of producing Intel® Omni-Path Software. BSD 2-clause License ............................................................................................................. 4 RedHat shim ...................................................................................................................... 4 EFI Developer Kit (EDK) ...................................................................................................... 4 EFI Developer Kit II (EDK II) ................................................................................................ 5 BSD 3-clause License ............................................................................................................. 6 Automatically Tuned Linear Algebra Software ......................................................................... 6 chashtable ......................................................................................................................... 6 FreeBSD ............................................................................................................................ 7 HPC Challenge Benchmark ................................................................................................... 7 HyperSQL Database Engine (HSQLDB) ................................................................................... 8 jgraphx ............................................................................................................................
    [Show full text]
  • Beyond the NDA: Digital Rights Management Isn't Just for Music
    Reprinted with permission from the January 2004 issue of the Intellectual Property & Technology Law Journal. Beyond the NDA: Digital Rights Management Isn’t Just for Music By Adam Petravicius and Joseph T. Miotke heft of proprietary information causes companies to lose to a particular project, little regard is given to whether the T billions of dollars each year.1 Yet to compete effective- information is actually needed for the project. ly, companies often must share their most valuable secrets Before sharing its proprietary information, a company with third parties, even their fiercest competitors. should carefully consider the scope of information that needs Companies routinely enter into non-disclosure agreements to be shared. This should be done both at the beginning of (NDAs) when sharing their proprietary information but then each relationship and periodically throughout the relation- forget about them shortly after they are signed, assuming ship. When doing so, a company should not just identify that their information is fully protected by the NDA. general categories of information to be shared but should However, there are a number of steps that companies should identify the specific information in each category. For exam- consider taking to protect their proprietary information after ple, if a company decides to share its customer information, signing an NDA. These steps range from simple steps, such it may not be necessary to disclose customer names; names as marking information appropriately, to sophisticated tech- could be withheld or replaced with random, unique identi- nological solutions, such as using digital rights management fiers. (DRM) software. One factor that should be considered when determining Although a well-drafted NDA provides significant legal which information to share is the scope of protection provid- protection to a company’s proprietary information, the best ed by the relevant NDA.
    [Show full text]
  • OSS Disclosure
    Tape Automation Scalar i6000, Firmware Release i11.1 (663Q) Open Source Software Licenses Open Source Software (OSS) Licenses for: Scalar i6000 Firmware Release i11.1 (663Q). The firmware/software contained in the Scalar i6000 is an aggregate of vendor proprietary pro- grams as well as third party programs, including Open Source Software (OSS). Use of OSS is subject to designated license terms and the following OSS license disclosure lists all open source components and their respective, applicable licenses that are part of the tape library firmware. All software that is designated as OSS may be copied, distributed, and/or modified in accordance with the terms and conditions of its respective license(s). Additionally, for some OSS you are entitled to obtain the corresponding OSS source files as required by the respective and applicable license terms. While GNU General Public License ("GPL") and GNU Lesser General Public Li- cense ("LGPL") licensed OSS requires that the sources be made available, Quantum makes all tape library firmware integrated OSS source files, whether licensed as GPL, LGPL or otherwise, available upon request. Please refer to the Scalar i6000 Open Source License CD (part number 3- 01638-xx) when making such request. For contact information, see Getting More Information. LTO tape drives installed in the library may also include OSS components. For a complete list- ing of respective OSS packages and applicable OSS license information included in LTO tape drives, as well as instructions to obtain source files pursuant to applicable license requirements, please reference the Tape Automation disclosure listings under the Open Source Information link at www.quantum.com/support.
    [Show full text]