Abstract
The last two years have been atypical to the Indico community, as the development team undertook an extensive rewrite of the application and deployed no less than 9 major releases of the system. Users at CERN have had the opportunity to experience the results of this ambitious endeavour. They have only seen, however, the “tip of the iceberg“.Indico 2.0 employs a completely new stack, leveraging open source packages in order to provide a web application that is not only more feature-rich but, more importantly, builds on a solid foundation of modern technologies and patterns. But this milestone represents not only a complete change in technology – it is also an important step in terms of user experience and usability that opens the way to many potential improvements in the years to come.In this article, we will describe the technology and all the different dimensions in which Indico 2.0 constitutes an evolution vis-à-vis its predecessor and what it can provide to users and server administrators alike. We will go over all major system features and explain what has changed, the reasoning behind the most significant modifications and the new possibilities that they pave the way for.
Highlights
Indico1 was born of a European Project, a joint initiative of CERN, SISSA, University of Udine, TNO, and University of Amsterdam
The European Project started in May 2002, and ended two years later
Afterwards, CERN took over the core modules that had been developed internally and put them together in a software platform aimed at fulfilling its own needs
Summary
Indico was born of a European Project, a joint initiative of CERN, SISSA, University of Udine, TNO, and University of Amsterdam. Creating a new index always requires iterating over all the objects to populate it, which may take a long time Another problem with ZODB is the fact that it is a niche product, so it lacks a large community and the third-party tools and support that usually comes with it. 2. The Solution In 2014 the Indico project received the resources required to abandon ZODB and move to PostgreSQL, leveraging the SQLAlchemy object-relational mapper to keep using Python objects instead of having to write SQL queries. To update an Indico instance with code customizations will require building a new Python package containing both upstream and local changes before installing it. It is worth mentioning there may be conflicts between local and upstream changes that would need to be resolved manually.
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
