LimeSurvey RDC

Since LimeSurvey™ is highly flexible in what types of surveys can be implemented, this single Survey based Risk Data Collector can be seen as a "meta" collector, in that is can collect any type of user input collectable from LimeSurvey™ (Creating LimeSurvey Questionnaires provide instructions to create surveys compatible with this RDR).

The LimeSurvey™ Survey based Risk Data Collector requires 4 input values in addition to the mandatory "targetEntity" input value. They are as follows:

Name	Meaning
username	The user name of the user account with which the LimeSurvey™ Survey based Risk Data Collector should log in to the running LimeSurvey™ instance.
password	The password of the user account with which the LimeSurvey™ Survey based Risk Data Collector should log in to the running LimeSurvey™ instance.
url	The domain for the LimeSurvey™ instance which contains the survey to collect from, for example: http://limesurvey.merit.unu.edu/
surveyID	A numeric ID of the LimeSurvey™ survey which should be collected from.
responseID	A numeric ID of the specific response instance of the LimeSurvey™ survey which should be collected.

The results of the Survey based Internal Risk Data Collector are specific to the individual survey which is collected so therefore cannot possibly be enumerated here but for a given survey, all of the results from the survey will appear in the results of the LimeSurvey™ Survey based Risk Data Collector. The following table include the set of data inputs defined in the survey for gathering contextual indicators for the adopter organization.

Data Point	Meaning	Posible values
CurrentSupply	The most significant current source of supply of OSS in the adopter organization	1: in-house production 2: other company 3: organisation contributing the OSS community 4: organisation not contributing the OSS community 5: external developers hired temporary by the organization
StrategyIntegration	The adopter organization is currently has a collaboration/partnership relation with some OSS Community	0: No, 1: Yes
StrategyInitiative	The adopter organization has created an OSS community	0: No, 1: Yes
StrategyFork	The adopter organization has forked an existing OSS Project	0: No, 1: Yes
StrategyTakeover	The adopter organization has taken the control of an existing OSS Project	0: No, 1: Yes
StrategyAcquisition	The adopter organization is using some OSS Component without contributing to the community	0: No, 1: Yes
StrategyRelease	The adopter organizaton is not using OSS components produced by a OSS Community	0: No, 1: Yes
SkillComm	Competence in OSS communication practices tool inside the adopter organization	0: Low 0.5: Medium 1:High
SkillRelease	Competence in OSS release practices tools inside the adopter organization	0: Low 0.5: Medium 1:High
SkillPatch	Competence in patching OSS components inside the adopter organization	0: Low 0.5: Medium 1:High
SkillLegal	Competence in OSS software legal issues insed the adopter organization	0: Low 0.5: Medium 1:High