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:
here are the minutes of our meeting today:
VRVS Meeting in Forrest Room:
Date & Time: 28.05.2004, 11:00-12:00 MESZ
David Bouvet (DB)
Kostas Koumantaros (KK)
Marco Verlato (MV)
Mario David (MD)
Wolfgang Thoene (WT)
Wojtek Wislicki (WW)
(I thought there was someone else too, but not all the time !?)
- WT introduced the current GGUS concept and answers questions
about the current GGUS LCG concept.
- MV introduced the ticketing/helpdesk system that was used at INFN - the
concept behind this, was very similar to the current GGUS concept
- The current GGUS solution does not include a knowledge base,
this is currently under development
- All participants share the idea of the ROC Managers-Meeting,
to setup a centralised User Support,
- we do not think that user support is necessary 24/7 at the beginning,
but it should be possible in the future
- The main goal for the beginning should be to find a good classification
for the tickets and even more important to define the groups (support,
deployment etc.) which are involved in user support to define fast and
- all members of the "support task force" should use and test the GGUS
portal at http://www.ggus.org. To have "support rights" please use the
link that is provided in the portal. Everybody should send WT an email
with comments to the portal (please provide good and bad thoughts) up to 04-06-2004,
after this WT will send out a summary and schedule an additional meeting.
- WT will send out an email to the ROC and CIC Managers, asking to receive a list
of groups that are common in each ROC/CIC for Support issues.
- all members should provide a list of their current structures, to see how
the ROC is organised in terms of support. Please send a one page PowerPoint
or OpenOffice Impress file. WT will provide a list of common groups :-)
Thanks to all of you and have an nice weekend