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:
RUCIO: setting up a Rucio Special Interest Group (SIG) on metadata: email@example.com (from people outside CERN please, let me or Martin Barisits know about your interest and you will be added in to the mailing list)
Using Redmine to describe RI goals, metrics and KPIs fro DAC2115m
Partners and RIs round table: summer/fall status and plans20m
Short updates from DAC21 Activity Groups15m
(PIC), Andrea Ceccanti
(INFN), Marek Szuba
(GSI), Paul Millar
(DESY), DrRiccardo Di Maria
(CERN), Rizart Dona
(CERN), Rosie Bolton
(Square Kilometre Array Organisation), Yan Grange
(ASTRON, the Netherlands Institute for Radio Astronomy), frederic gillardo
Update on Activity-1 (Xavi on behalf of Yan, Frederic and Riccardo):
Interest in Rucio Agnostic RSEs as part of DAC21 by SKA.
We had some interesting discussion on deterministic RSEs, following some comments from Paul wrt the fact that determinism just means an algorithm defines where data is placed, and that that definition is configurable and not necessarily based on the standard method of hashing the file name.
Maybe DIRAC needs an RSE to be deterministic? this needs a bit further investigation
WP5 have an implementation of a Rucio data search using scope, finding a file and putting it in the shopping basket. The shopping basket basically contains data references.
The Interactive Analysis team is working on implementing reading the shopping basket. Combining this with the Jupyter kernel would be awesome.
SKA mentioned they would really be interested in the subscription-based use case, this would require the transmogrifier daemon to be activated. This was taken to DepOps.
QoS: Paul mentioned that there will be some tape capacity available at DESY for ESCAPE
July is the QoS month. The sub-task led by Paul should provide a real and concrete deployment to be tested by experiments. QoS status is as it was at the FDR. At our knowledge, nothing new has been integrated in the ESCAPE Rucio instance.
DLaaS proceeding and to be tried out soon by end-users of interested experiments.
Update on Activity-3:
OIDC Authentication on the ESCAPE Rucio instance is now working
Users can authenticate via the ESCAPE IAM
Detailed documentation of how to use will be circulated