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:
Provenance in Astronomy: data model and implementations
Salle du Conseil (Observatoire de Paris)
Salle du Conseil
Observatoire de Paris
77 Avenue Denfert-Rochereau, 75014 Paris
The objective of this meeting is to finalize the IVOA Provenance Data Model working draft before entering the promotion process to make it an IVOA recommendation. A session of the meeting will be dedicated to the presentation of the different implementations (and use cases) based on this standard.
Our Astronomy use cases generally require some information on the activities : description, configuration (config file, parameters) and context (ambient conditions, execution environment, ...)
New relations to specialized entities20m
Activity description, configuration and context would require specialized relations : hadDescription, hadConfiguration, hadContext
Mapping with PROV20m
Following the requirements, we should be able to serialize our model in the W3C PROV formats, e.g. by defining specific values for prov:type for the different entities and relations
Mapping with ProvONE for workflows20m
Some concepts relevant for astronomy may already exist in the ProvONE extension to PROV, we should ensure that our concepts are compatible. We also have the example of UniProv that uses partially PROV, ProvONE and internal concepts
Preparation of ADASS in College Park20m
François will have a talk on ProvTAP, we should propose posters on ProvDM and ProvSAP as well to advertize more widely the IVOA Provenance data model