The Selection Between An Open Source And Vended Software in Libraries: Opportunities & Risks
•Download as PPTX, PDF•
1 like•949 views
The Selection Between An Open Source And Vended Software in Libraries: Opportunities & Risks
Recommended
Recommended
More Related Content
What's hot
What's hot (11)
Viewers also liked
Viewers also liked (14)
Similar to The Selection Between An Open Source And Vended Software in Libraries: Opportunities & Risks
Similar to The Selection Between An Open Source And Vended Software in Libraries: Opportunities & Risks (20)
More from Hong (Jenny) Jing
More from Hong (Jenny) Jing (8)
Recently uploaded
Recently uploaded (20)
The Selection Between An Open Source And Vended Software in Libraries: Opportunities & Risks
- 1. The Selection Between An Open Source And Vended Software in Libraries: Opportunities & Risks Jenny Jing July 11, 2016
- 2. 1. Academic Libraries & Challenges 2. Technology, Vended Product & Open Source (OSS) 3. Project Management & Software Development 4. Library Technology & OSS 5. Functional Requirements, Opportunities & Risks 6. Selection and Evaluation, Opportunities & Risks 7. Summary Overview
- 3. Technology Data/Resources 1. Academic Libraries & Challenges UsersStakeholders $, Time https://en.wikipedia.org/wiki/Zachman_Framework
- 4. 2 Technology 工欲善其事 He who wishes to do his work well 必先利其器 Must first sharpen his tools
- 5. Types Pros Cons OSS Freedom: licenses Functions Customize & fix Reduce Cost Community/Collaboration Selection, tracking codes Lack of support, maintain Standards, risks Documentation Security? Stable? Vended Product Stable product Usability Support Documentation Security One-size-fits-all Cost Can’t customize Slow to fix Vended Product & Open Source (OSS) Organizational Adoption of Open Source Software: Barriers and Remedies.
- 6. What: Scope Why: Goal & Purpose Who: Responsibilities When: Time Frame How: Functions Resources/Cost Risk/Opportunity Quality Control 3. Project Management: Vended Product vs OSS Vended Product Usability Sales Person Fixed Time Frame RFP Cost Training/Support Testing OSS Usability System, developer Time consuming Functional requirements Free, other resources Security, Maintain, Reliability Testing/co-operation
- 7. Software Development Lifecycle: Vended Product vs OSS https://en.wikipedia.org/wiki/Systems_development_life_cycle Plan & Analysis • Systems analysis • Facts & Requirements • Integration & testing • Evaluation Vended Products Selecting the OSS: • RFP * Study, research • Vendor marketing * Communities/Other libraries • Consulting service * Experts’ recommendations
- 8. Software InfrastructurePlatforms ILS: Voyager, Aleph ILL, Etc. Link resolver : 360 Link library guides: LibGuides Online databases IR (Scholarly Publications): DSpace DAM (Digital Preservation): Islandora Discovery Systems: Summon Websites: Library Homepage 4. Library Technology & Challenges
- 9. Type OSS OSS OSS ILS Koha Evergreen NewGenLib IR DSpace Eprints Digital Commons DAM Fedora Islandora ContentDM Exhibition Omeka Open Exhibits Collective Access Archive AtoM ArchiveSpace Digital Preservation Archive-It Archivematica RDM CKAN Dataverse Library OSS
- 10. 5. Functional Requirements: Stakeholders Managers Staff Users Resource/$ Workflow Usability Outputs: • Project Goal/Time Frame/Resources/Cost • A List of Functional Requirements by made by Modules: • A Table of Role/Responsibilities: Who, When, What • A Table of Opportunities & Risks: H, M, L • Use Cases/Standards/How to test & evaluate
- 11. Vended Product vs OSS • Cost/Resources • Functions/workflow • IT staff’s skill sets • IT Staff’s attitude • User experience • Feedback/review Functional Requirements : Stakeholders https://journals.ala.org/ltr/article/view/4618/5454
- 12. Types Opportunities Risks OSS Cost Functionality User Experience Community, co-operation Functional requirements QA Control, Versioning Staff Skills/Training Time Vended Product Stable product Usability Support, Training One-size-fits-all Cost Can’t customize Opportunities & Risks : Stakeholders (Sample Project)
- 13. System/AdminInterface/Web Data/DB Data: Queries, Perl, XML, DB: Oracle, MySQL, Access Tools: Perl, Excel, XSLT Programing: php, Javascript, html, etc. Publish Tools: Drupal, WordPress Server: Shell scripting, config, maintain, etc. OS: UNIX, Windows Editor tools: Vi, Pico Functional Requirements: Systems
- 14. Vended Product vs OSS • Release activities • Community activities • License and documentation • Functions/Features • Users’ population, longevity • Programming languages • Technology components • Integration: Work with other systems • External: IT, Third party support Functional Requirements : Systems (Sample Projects) https://journals.ala.org/ltr/article/view/4618/5454
- 15. Opportunities & Risks: Systems Types Opportunities Risks OSS Functions Customize & fix Improve User Experience Enhance co-operation Test and Evaluation License, Productivity Installation, Configuration Maintain, Admin, Upgrade Support: Community Documentation Reliability, Security Vended Product Stable product Support, Training Documentation Security Vendor lock-in Cost Can’t customize Slow to get help
- 16. Web pages ILS DAMIRRDM DS Mobile Access Library Data (metadata) Functional Requirements: Data & Database Functional Requirements
- 17. Functional Requirements : Data & Database • Databases: MySQL, PostgreSQL • Data Format and Size • Search Engine: Solr • API access to data • Import/Export • Schema/Standards • Query language • Maintain, Upgrade • Migration https://journals.ala.org/ltr/article/view/4618/5454
- 18. Opportunities & Risks : Data & Database (Sample) Types Opportunities Risks OSS Reduce Cost Functions Improve User Experience Enhance co-operation Data Format and Size Schema/Standards Import/Export Migration Search, Query language Documentation Vended Product Stable product Usability, Standards Support Documentation Cost Data Format and Size Can’t access the databases Data Format and Size Slow to get help
- 19. 6.Selecting & Evaluation: Sample Project Functionality Reliability Usability Efficiency Maintainability Portability Security Compatibility Evaluating Open Source Software Quality Models Against ISO 25010
- 20. Opportunities & Risks: Sample Project
- 21. Managers Staff Users Cost/ Resource Workflow Usability 7. Summary Functions, Opportunities & Risks Data Format Size Metadata Security Import/Export Hardware/Software Config, maintain Functions, Opportunities & Risks Functions, Opportunities & Risks Ideal Solution
- 22. Sample Project: DAM/IR Selection 1. Big Picture2 Scan 3.Functions 4 Research 5. Case 6. Test
- 23. Selection : Vended Product vs OSS Web pages ILS DAMIRRDM DS Mobile Access Return vs Resources/Cost
- 24. References • https://en.wikipedia.org/wiki/Zachman_Framework (1992) • https://en.wikipedia.org/wiki/Systems_development_life_cycle • Major Open Source ILS Products: https://journals.ala.org/ltr/article/view/4618/5454 • Evaluating Open Source Software Quality Models Against ISO 25010 • Success and Abandonment of OSS Library Management Systems: http://publications.drdo.gov.in/ojs/index.php/djlit/article/view/8866 • Moving Towards the Next-Generation Library: BRAC University Experience
- 25. Thank you! • 独木难成林 • A tree does not make a forest
Editor's Notes
- In the past few years, IRs are developed within the context of the open access(OA)movement, shrinking library budgets, the increasing costs of traditional scholarly journals and publications, and the increased development of software platforms for IRs.
- Confucius
- Open source software (OSS) is software created and distributed with licensing agreements The distinction between open source and proprietary software is not that one is free and the other is not. They are each based on differing methodologies and business models. They have their own pros and cons. These must be reviewed within the library context. Success and Abandonment of OSS Library Management Systems (Journal of Library & Information Technology, Vol. 35, No. 6, November 2015, pp. 398-407) which was published last year and it is found that out of 31 open source library management systems only 15 systems are currently active. Maximum active open source LMSs have institutional support. Fifty per cent of LMS project are inactive or abandoned.
- Defines project goals into defined functions and operation of the intended application. It is the process of gathering and interpreting facts, diagnosing problems and recommending solutions/software. Analyzes end-user information needs and requirements. Identify, Read Reviews, Compare, and Analyze can be abbreviated as "IRCA". Important attributes to consider include functionality, cost, market share, support, maintenance, reliability, performance, scaleability, useability, security, flexibility/customizability, interoperability, and legal/license issues.
- New Systems have emerged: Scholarly communication — New scholarly communication and publishing Data curation — Data curation challenges are increasing as standards for all types of data continue to evolve; more repositories, many of them cloud-based, will emerge; librarians and other information workers will collaborate with their research communities to facilitate this process. Digital preservation —the general lack of strategic leadership for establishing architecture, policy, or standards for creating, accessing, and preserving digital content is likely to emerge.
- The distinction between open source and proprietary software is not that one is free and the other is not. They are each based on differing methodologies and business models. They have their own pros and cons. These must be reviewed within the library context.
- In general, there are three layers of a system, including: the Interface, the system, and the data. Each layer requires different types of skills. To simplify this image, the interface is like the part of a tree above the ground, the system is like the whole body of a tree including the part below the ground, and the data is like the water inside of a tree, in order to visualize, the data are like the fruits of the tree, and that’s what the users want. Commercial: Buy the seed OSS: free seed In house: own seed
- The release activity shows the progress made by the developers Success and Abandonment of OSS Library Management Systems (Journal of Library & Information Technology, Vol. 35, No. 6, November 2015, pp. 398-407) which was published last year and it is found that out of 31 open source library management systems only 15 systems are currently active. Maximum active open source LMSs have institutional support. Fifty per cent of LMS project are inactive or abandoned.
- Where is library data? They can be in different systems, for example, in ILS, it can be in a MARC record, in local dbs, it can be an Excel file, in IR it can be an RDF or XML record, in DAM …..how could we control the data in different library systems? Metadata schema. Metadata is used to both improve accessibility and discoverability; and to control authentication for the data we have.
- Here is a report about the general cost of an IR for a library