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:
From discussion it’s not obvious that all experiments know how to write mock plus real data in a way that mock data can be dropped by the end of the exercise.
What measures should be taken to ensure this will work?
Should we have a small test right now in December?
24h CDR run at nominal rate with a mix of real and mock data?
The important step is not the test but obviously the preparation that needs to go into it.
Monitoring, logging and reporting - the proposal10m
(CERN), Julia Andreeva
CMS CSA07 metrics
The SRM dashboard - site & experiment readiness for production SRM v2.210m
Multi-VO site issues
For the sites supporting multiple VOs (the majority) the requested SRM setup must be compatible.