Indico

Indico
Name	Indico
Developer	CERN
Released	2002
Programming language	Python
Operating system	Cross-platform
License	GNU Lesser General Public License

Indico

Indico is an open-source event management and conference planning platform originally created to manage scientific meetings and conferences. It provides facilities for event registration, abstract submission, scheduling, booking, and archival, and has been adopted by research institutions, universities, and professional societies. The project originated at CERN and has influenced workflows at laboratories, academic departments, and international collaborations.

History

Indico traces its origins to a need for coordinated meeting management at CERN during the early 2000s when projects such as Large Hadron Collider operations and collaborations like ATLAS and CMS required systematic scheduling. Early development intersected with software efforts at European Organization for Nuclear Research and contributions from groups involved in World Wide Web Consortium standards and Open Source Initiative practices. Over successive releases the platform incorporated features inspired by conference systems used at institutions such as Massachusetts Institute of Technology, Stanford University, and University of Oxford. The software evolved alongside related projects in event calendaring and booking systems used at Fermilab, DESY, and national laboratories participating in international programs such as CERN Openlab. Indico's roadmap has been shaped by interactions with funders, stakeholders like European Commission projects, and standards bodies including Internet Engineering Task Force working groups.

Architecture and Features

Indico's architecture is a Python-based web application that integrates with databases and web servers common in enterprise research environments. Its stack has drawn on technologies and best practices from projects like Django (web framework), SQLAlchemy, and packaging conventions influenced by Debian and Red Hat Enterprise Linux distributions. Core features include event creation and hierarchical categorization, programme scheduling with parallel sessions, abstract submission and peer review workflows, participant registration and payment handling, and room and resource booking. The platform supports document attachments, multimedia archival compatible with repositories such as Zenodo and integration patterns seen in Invenio digital library systems. For calendaring and interoperability, Indico provides export formats compatible with iCalendar standards and synchronization approaches related to Google Calendar, Microsoft Exchange, and CalDAV servers used by institutions like Harvard University and Princeton University.

Deployment and Integration

Indico is designed for deployment in institutional infrastructures including research centers, universities, and consortia. Typical deployments use reverse proxies like NGINX or Apache HTTP Server, database backends such as PostgreSQL or MySQL, and caching layers influenced by solutions like Redis and Memcached. Integration points commonly implemented include single sign-on using LDAP, SAML 2.0 via providers such as Shibboleth and identity federation platforms like eduGAIN, as well as OAuth2 connectors compatible with GitHub and GitLab. Payment integrations follow gateways used by many organizations, comparable to implementations at University of California campuses and international societies like IEEE. Backup, monitoring, and continuous deployment practices mirror patterns employed by projects hosted on GitHub and automated with tools like Jenkins or GitHub Actions.

Security and Privacy

Indico's security model addresses access control for event organizers, reviewers, and attendees, using role-based permissions similar to systems at National Institutes of Health and European Space Agency. Deployments commonly employ TLS as recommended by Internet Engineering Task Force and certificate management patterns aligned with Let's Encrypt automation. Authentication and authorization practices follow federation protocols used by eduGAIN and enterprise IAM solutions such as Keycloak. For privacy and data protection, sites often implement retention policies informed by frameworks like the General Data Protection Regulation and institutional guidance from legal offices at University of Cambridge and Max Planck Society. Auditing, logging, and secure coding practices reflect standards seen in projects adopted by European Research Infrastructure Consortiums and are consistent with recommendations from OWASP.

Use Cases and Adoption

Indico has been used for a wide range of events: large scientific conferences for collaborations like ALICE (particle detector), workshops and seminars at institutions such as Imperial College London, internal meetings and room booking at laboratories including CERN and Fermilab, and thematic schools and summer programs run by organizations like ICTP. Professional societies and engineering consortia, including chapters of IEEE and ACM, have adopted similar event-management paradigms for symposia and proceedings. Academic departments at universities such as University of Toronto, University of Edinburgh, and École Polytechnique have deployed instances to manage courses, exams, and departmental seminars. The platform’s archival capabilities support scholarship workflows analogous to repositories like arXiv and conference proceedings publishers including Springer Nature and IOP Publishing.

Development and Community

Development of Indico is coordinated through collaborative platforms and embraces contributions from developers, system administrators, and user communities across research institutions. Governance and contributions reflect collaborative models used by projects like Invenio, Django, and community-driven infrastructures supported by Open Source Initiative. The project maintains documentation and issue tracking practices comparable to those on GitHub and hosts community events, training, and workshops similar to developer outreach by Mozilla Foundation and Apache Software Foundation. Major contributions have come from staff at CERN and partner institutions, and the ecosystem includes plugins and integrations developed by members of the broader scientific software community.

Category:Free software