LimeSurvey Reporting Solution “Data Analysis Layer” Development Approach

[A] LONG-TERM [Context of Reporting Solution] I am looking for a long-term reporting solution for our LimeSurvey driven assessments. LimeSurvey does not have the capabilities I need so a reporting solution that can work with LimeSurvey and work behind the scenes will be necessary. It will need to be seamless behind the scenes but interfacing with our LineSurvey front-end UIX. Currently we have the logic and report design working within MSExcel which imports a LimeSurvey CSV file (exported from the LimeSurvey admin interface. So I need to design this so that it is user-driven rather than the manual process that is in place today. You do not need to know LimeSurvey as I posses the understanding of all our assessments as well as the LimeSurvey data model. However here is what you need to know in order to be considered for this initial design approach: (1) MySQL [[login to view URL]] (2) R [[login to view URL]; [login to view URL](programming_language)] (3) VBA [[login to view URL]] (4) MS Excel (5) Server-side Scripting languages (Python, Perl, Java, Ruby…) ----------------------------------------------------------------------------------------------------------------- [B] DEVELOPMENT APPROACH [Requirements for this project] For this project I need you to review the current “MS Excel Report Generator” and determine if the formulas within this program are (1) salvageable or (2) whether they have to be redesigned so that they can be transferred over to R. If they have to be redesigned I will redesign them. Once we determine this part of the project then I need you to determine how we get to the next step. Currently LimeSurvey and it’s database (MySQL-PQI) are working fine for our needs. We would like to minimize any programming and/or connections directly to the LimeSurvey overall solution so we have designed a separate Database (MySQL-DSH) that includes all the necessary tables needed for the overall reporting solution (an it’s associated data) and we have created triggers to insert, update or delete the data from these tables. So the MySQL-DSH database should be the only database we need to connect to. *see attached document for full description of this section ----------------------------------------------------------------------------------------------------------------- [C] TO BE PROVIDED [Information necessary to determine an approach] *see attached document for full description of this section ----------------------------------------------------------------------------------------------------------------- [D] OUTCOME [What I need from you in order to move this forward] *see attached document for full description of this section ----------------------------------------------------------------------------------------------------------------- [E] OPPORTUNITY [Opportunity to be part of developing this solution] *see attached document for full description of this section ----------------------------------------------------------------------------------------------------------------- NOTE: There is no development necessary for this project just your research, expertise and design of an approach for developing this layer. Development will come after this along with a new bid on that development effort.