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:
Discussion the workplan details, the template (to be put on the Wiki next week) and aggregation of key topics of interoperability that have been identified up to that moment by ALL interoperability cases. The WP leader will come with the main presentation for the discussion and we will enrich/revise it with more options during the meeting. Tasks should be ready to contribute to the discussion with structured info (no presentations required though)
TNA4.1 - D4Science-AquaMaps Interoperability1h
Open discussion on specifications, procedures, requirements driven by the aquamaps case. The case representative should lead with a technical presentation about what can be consumed both directions and the discussion to be driven should elaborate the protocols/technologies, enlarge the case and evaluate the feasibility of the individual items.
TNA4.1 - D4Science-DRIVER Interoperability45m
The results of the initial interoperability focusing meetings will be presented and discussion on each case will extend/refine towards global convergence via diffusion and harmonization.
TNA4.1 - Other (FAO) Repositories Interoperability1h
Similar to the AquaMaps session, led by FAO representative. Apart from the technologies the repositories themselves have to be presented too along with all currently available information.
Similar to the AquaMaps session, led by TERADUE representative.
TNA4.1 - D4Science-INSPIRE Interoperability1h
Similar to the AquaMaps session, led by CERN representative.
TNA4.2 - Participation to Standardisation Bodies45m
Collective enumeration and proposals on where the project (by its members) should/can be placed for pushing the specs it needs / adopts. The precise topics should be driven mostly by the discussion of previous sections (as they define the targeted specs/bodies). The discussion will be led/coordinated by the task leader but contributions should come from all attendants.