One of the requirements of our university is to collect feedback from students on all the teachers instructing them, in the middle and at the end of each semester. We collect this feedback electronically using an open-source application. One of the key benefits of this application is that it makes it impossible for the administrator to trace the response submission to the student who submitted the response. One survey is generated per course offered in the semester.
The second RADICORE based application that I have built is the Survey Reports application. This application uses the database of the survey application and uses its contents to generate two reports for each survey. The first report lists students who are participating in the survey but have not as yet submitted their feedback, while the second report is a compilation of responses submitted by the students, represented statistically, along with a student comment section appended to the report.
Using RADICORE to create the survey reports application
After importing the survey application’s database into the survey reports application, two tables per survey have to be imported from the database into RADICORE’s data-dictionary. This exercise is all that is needed to bootstrap the survey, making it possible to print both the reports. Each time a student fills out a survey, a record is added in both these tables in the survey application database. This database has to be dropped and then imported again into the survey reports application in order to update the application with the latest data.
This RADICORE application is also role based with a distinct role created for each Head of Department (HoD). This has to be done to create a custom view for each HoD such that they are able to view reports for teachers from their department only.
A new feature of RADICORE used in this deployment is its capability of hosting multiple independent applications. I used this feature to create a new instance of a Survey Reports application each time a survey exercise is conducted in the university. These application instances are completely independent of each other but use the same authentication and authorization infrastructure. This allows the HoDs to login to a single RADICORE instance and access feedback reports across all the surveys that were conducted in the university.