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:
b. Maria added Christoph into the e-group firstname.lastname@example.org where general savannah migration information circulates.
c. The technical precisions on each of the above tickets appear inside the tickets.
Summary on above agenda points 1-4:
1. The ticket submission can be possible from any GGUS user. The web form will have a URI like https://ggus.eu/pages/ticket_cms.php. Its layout should be like the TEAM ticket's form, so much simpler that the USER ticket submission form. The MoU field is even not necessary. ACTION: Christoph will comment in Savannah:134411 if anything else is needed on the form.
2. The "Notify site" value on this CMS-specific web ticket submission form will be taken from SiteDB.
3. There is a need to define CMS-specific GGUS SUs based on the expertise of the CMS squads. ACTION: Christoph will propose SU values to discuss in another such meeting.
4. The "Type of Problem" will have different CMS-specific values. Details and observations on the Cc field in Savannah:134416#comment4 ACTION: Christoph will propose ToP values to discuss in another such meeting. Guenter to check the ToP-Cc technical details.
Christoph asked what supporters at the sites, working in their local ticketing system, should do when they see the SU of a ticket is incorrect and they wish to re-assign the fastest way. Answer is: Do this directly in GGUS!