EU Library System Migration to AWS Cloud
•Download as PPTX, PDF•
1 like•1,251 views
Presented on the L&T conference, held on 26 Th of February 2013 in Jeddah, Saudi Arabia.
Recommended
Recommended
More Related Content
Similar to EU Library System Migration to AWS Cloud
Similar to EU Library System Migration to AWS Cloud (20)
Recently uploaded
Recently uploaded (20)
EU Library System Migration to AWS Cloud
- 1. Dr. Grete Pasch Mr. Anes Essid, MLIS, System & E-resources librarian Effat University Library Effat University
- 2. Outline Background: Effat University (EU) Library EU Library system from local to cloud computing A.Essid & G.Pasch - L&T 2013
- 3. Background Effat University (EU) Library: • EU Library holds approximately 20,000 books, 2,500 periodicals, 150,000 eBooks, 100 databases apart from numerous laptops, tablets, and eBook readers. • The Library system was based on Horizon ILS (Integrated Library System) until 2010 when it was migrated to Glifos ILS. A.Essid & G.Pasch - L&T 2013
- 4. Glifos Library system : Architecture, Modules & functionalities A.Essid & G.Pasch - L&T 2013
- 5. A.Essid & G.Pasch - L&T 2013
- 6. Library system from local to Cloud-Based system • Glifos’s recent release of ILS, a LAMP (Linux Apache MySQL PHP) based version poses the following : Issue • The existing server at EU, Microsoft is unable to support the Linux environment Three possible solutions: 1. Purchasing a Linux server 2. Acquiring a dedicated hosting service 3. Trading up to a cloud-based server A.Essid & G.Pasch - L&T 2013
- 7. Library system from local to Cloud-Based system The procedure 1. Create an AWS (Amazon Web Services) account 2. Acquire an instance supporting Linux/UNIX Platforms 3. Deploy the instance with an AMI (Amazon Machine Image) 4. Create the required volume for the application from the “Elastic Block Store“ [size required: 250 GB] 5. Launch the instance 6. Install the library system A.Essid & G.Pasch - L&T 2013
- 8. Library system from local to Cloud-Based system A.Essid & G.Pasch - L&T 2013
- 9. Library system from local to Cloud-Based system 7. Migrate the library data 8. Ensure data integrity and deployment of all functionalities 9. Test the system to verify each module The Result: • The new system stands equivalent to the old system in all functionalities A.Essid & G.Pasch - L&T 2013
- 10. Final Concern Despite the great efficiency of the new system, the EU Library is left with the following concerns: 1. Would this provide a high level of user satisfaction? 2. Would it be cost effective? A.Essid & G.Pasch - L&T 2013
Editor's Notes
- Hello every body, this is going to be a quick presentation giving you an overview of our experience with the Cloud based ILS
- I take this opportunity to shed some light on the library system with a reference to its context.The library houses 20,000 print books, in addition to its 150,000 electronic books and 100 academic full text databases, we also have 50 laptops and Ipads as well as 5 kindles.As a brief history, and in early 2010, Effat library decided to change the Library system from Horizon to Glifos, since it offers more features and has a low cost ownership and maintenance.
- Since we will focuson the library system, I think we need first to define quickly what an ILS is : ‘’It is a multifunction application that allows libraries to manage, catalog and circulate their materials to patrons’’, It compromises:- Two interfaces, user and admin Integrated modules Server Database : the LS has tow databases, Bibliographic database that stores record and Patron database records
- One of main module offered by Glifos ILS is the OPAC which an acronym of Online Public Access Catalog, and this a ‘’web-based program providing Internet access to the library collection.’’, in other word ,this is the interface where users can search, reserve or renew library material.The cataloging allows the library staff to ’ catalog resources, manage the authority files, tag and categorize content, import and export bibliographic records.’’And in addition of cataloging, circulation, which enables the library staff to track where is the collection, who has the book, and it is typically used to manage users, circulatematerials, processreturns, renewals and fines, so every thing related to the patron is integrated together.Another function provided by Glifos is the Report, which enables the library staff to generates up-to-date data including: Library Users with Pending Items, Call Number, Labels, Fines Control, Inventory, Most Requested items, Catalogued Materials….All these module are integrated in the system system and running locally on Microsoft Platform
- In 2012, the Vendor releases a new LAMP-Based (Linux/Apache/MySQL/PHP) version of the ILS, which means that the new release will not supported by our local server. Given this new requirement, three options are possible : Purchasing a new server under Effat Library Budget Acquiring a dedicated hosting service, which will be very expensive- Acquiring a Cloud based server, the low cost of the option, the flexibility that it offers, since we can add any computing resources instead of ordering and installing new server, as well as it enable us to minimize the hardware-related downtime and the ability to implement new technology-based library quickly, make this option the most convenient.so we decided to run the first test of the new system on a Amazon Cloud Server
- In the next presentation I will try to explain to different steps on how to set up the AWS for Glifos LS : The first step is to create an AWS accountThen, acquire an instance (A copy of an Amazon Machine running as a virtual server ) with the technical requirements needed by the new version of Glifos : Platform: Linux/UNIXOnce acquired, we deployed the instance with an AMI (Amazon Machine Image, it is an encrypted machine image stored in Amazon S3, and It contains all the information necessary to boot instances of your software.)After acquiring the Instance, we got the “Elastic Block Store" (EBS) which provides block level storage volumes for use with Amazon EC2 instances, and then we create the required volume for your application (Size: 250 GB, Volume Type: Standard), and now the instance is ready for use Work then proceeded on installing the system and migrating the library's data. The team found it convenient to be accessing the system on the AWS server, as it offers full functionality, security, and is always available. The development team was able to access, manage, install, configure, and test without the limitations often imposed by the institutional IT departments, that often hesitate to enable server permissions or install software for remote administration
- In this phase, we had to make sure that the migration was successfully completed, the data integrity is maintained and all functionalities are deployed.
- At this point, the new system has been proven to be functionally equivalent to the old system. But since working through the AWS had been so smooth, the developers and library team wondered if it wouldn't be more efficient to simply run the library application in the cloud. In order to reach a decision, two questions had to be answered: Would this provide a high level of user satisfaction? And would it be cost effective?