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 aim of this first brainstorming meeting is to exchange technical information on the standardisation activities of the Solid project between representatives of Solidimplementors and CERN developers of popular and very visible applications, like Indico and Invenio.
Mitzi László and Sarven Capadisli explain the structure of the developers' community, the way they interoperate and assign priorities.
Mitzi László, Sarven Capadisli
Short description of Indico30m
The application, the development team, the other Indico instances, challenges around content ownership and more.
Short description of Invenio30m
Lars explains the application's purpose, structure, contributions by the community, challenges for integrating input, dissemination and influence on Zenodo and CDS.
Lars Holm Nielsen
Lunch in Restaurant 21h
The CS3MESH project10m
In this presentation we will explain the objective of the CS3MESH4EOSC EU project. Europe is facing a fragmentation of different services that are very difficult to connect to each other like you were using a centralized global service like DropBox or Google Drive. The project aims at bringing the same user-friendly functionality already offered by global services and individual on-premise deployments on a pan-European cross-institution mesh that relies on the federation of different sites by using well-known APIs. The project involves defining and promoting a set of APIs that will allow to connect these isolated service islands while retaining user privacy and data sovereignty.
Hugo Gonzalez Labrador
(University of Vigo (ES)), Jakub Moscicki
Developer tools and implementation30m
Mitzi and Sarven explain what is in focus now for the solidproject.org: The community, the software repositories, the code review processes, the communication channels. They explain where implementation efforts take place, explain inrupt's role https://solid.inrupt.com/, as well as the work done at MIT and elsewhere.
Sarven explains some Solid applications e.g. https://dokieli/ ,
which showcases various disparate parts – Web standards, technologies and social ideals – coming together in a cohesive way to serve a futureresearch communication ecosystem.