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:
The University of Edinburgh, James Clerk Maxwell Building, Mayfield Road, Edinburgh EH9 3JZ
As our HPC resources become more an more powerful, there is a corresponding increase in the size of output files produced (and in some cases, input files required).
Whether you're using HECToR, ARCHER, another PRACE resource, EUDAT's data services, or using the RDF directly, the problems are similar, and the best practice for moving large data files the same. This course will cover the techniques used to move large amounts of data (such as the use of GridFTP) and also provide a background to the authentication mechanisms required to get GridFTP working for you. We'll also introduce you to iRODS and to EUDAT's data services which can provide additional services (such as replication of your data between sites).