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:
1) Can the experiment run on SL6?
2) Can the experiment run on mixed clusters?
3) If experiments cannot run on mixed clusters do they prefer a big bang upgrade or a gradual upgrade moving WNs from one queue to another?
4) Does the experiment have already SL6 sites?
5) Are there time constraints?
6) Do the experiments have an upgrade procedure in place? ) Most problematic sites will be the shared ones which will have to follow more than one procedure.
7) Comunication with sites ) Same as above.
8) Present sites plans
*) Do sites want to test (there will be a number that do)? is there a testing procedure?