Skip to content
Lidia edited this page Apr 24, 2015 · 17 revisions

Risk Data Collectors are the main agents that are in charge of collecting risk data about the entities that are taken into account for the risk analysis, and to send it to the Risk Data Repository to be made available to the other components within the platform.

Risk Data Collectors are independent components that can be implemented with any technology (e.g., by using scripting languages like Ruby, Python or Node.js or even with older languages like C).

Risk Data Collectors fall into two sub-groups. There are the so-called "external" Risk Data Collectors, i.e. those which are invoked from outside of the Domain Manager, perhaps by third parties such as Open Source Community members who want to provide data about their project to the RISCOSS Platform and there are the so-called "internal" Risk Data Collectors which are included in the platform and made available to be activated and configured when a project is registered in the Domain Manager and then are invoked directly and periodically from the Data Collector Manager within the Domain Manager.

External Risk Data Collectors store their data using the REST API (see Risk Data Collectors REST API) while internal Risk Data Collectors must follow a specific protocol in order for their configuration parameters to be made available to them and for them to be able to emit their results to the Domain Manager which then relays them on to the Risk Data Repository.

Guides/Tutorials for the Data Collector developers

Data Collectors Protocol

Information for the Modelers

The data collectors are producing the data inputs than can be used in the risk models.
LimeSurvey RDC