In order to enable an iCal export link, your account needs to have an API key created. This key enables other applications to access data from within Indico even when you are neither using nor logged into the Indico system yourself with the link provided. Once created, you can manage your key at any time by going to 'My Profile' and looking under the tab entitled 'HTTP API'. Further information about HTTP API keys can be found in the Indico documentation.

I have read and understood the above.

Additionally to having an API key associated with your account, exporting private event information requires the usage of a persistent signature. This enables API URLs which do not expire after a few minutes so while the setting is active, anyone in possession of the link provided can access the information. Due to this, it is extremely important that you keep these links private and for your use only. If you think someone else may have acquired access to a link using this key in the future, you must immediately create a new key pair on the 'My Profile' page under the 'HTTP API' and update the iCalendar links afterwards.

SciChat is an instant messaging application which will be used as a logbook for ESS experiments. Scientists can communicate about experiments, even when they are remote. Posts about newly completed runs can be automatically posted with data visualization and pushed to users' mobile phones. This captures valuable information about the experimental process automatically, that can be linked to the metadata catalogue. Feedback from ESS users in test experiments has been very positive.

Webjive is a web based tool for accessing the control system in MAX IV facility. This application allows user-friendly interactions with all the process variables of the control system exposed through Tango. It started as "easy and quick-to-use web interface" with the aim of helping our staff to interact with the control system. It is being used for monitoring as well as control.
It has two root level views named Devices and Dashboards. The Devices view exposes the configuration of all the devices in the control system in an interactive treelike hierarchy to reflect domain/family/member structure of Tango devices. The Dashboard view allows the users to create their own interfaces (dashboards) referencing the tango devices and/or the attributes they are interested in through just drag-and-drop of predefined but easily extendible library of widgets, and connecting them to tango devices and/or attributes. These dashboards can be edited, saved and also shared between the users. A running dashboard reflects the state of the connected components with real-time events.
The frontend is developed using React, Redux and Typescript whereas the backend includes a GraphQL based API which exposes Tango, a Mongo Database for persistence and JWT based authentication.
We are currently working on the third root view called Synoptic which will include the overall view of all the hardware devices of the control system to which Webjive is connected.