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.
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.
Permanent link for public information only:
Permanent link for all public and protected information:
* End-points for ALICE at RAL
* CMS transfer rate to RAL
* NDGF Status and requests from ALICE and ATLAS
* Transfers of Job Log back to CERN
* Data Transfers from the WN to CERN (LHCb)
Summary of the Service Status and Experiments Activities15m
As agreed in the MB
of 30 May, a combined action list was setup and reviewed
weekly through the LCG ECM. The state of this list was
regularly reported to the MB, and covered in the paper (see
attachment) submitted to the LHCC comprehensive review.
Please see that document for details of the various problems
(including some of the above) and their resolution.
The 3D Phase 2 sites should specify milestones for
installing and commissioning their 3D installations.
TRIUMF and PIC did so. NDGF and SARA-NIKHEF should specify
the milestones for hardware, software and operations.