vlead / feedback-portal Goto Github PK
View Code? Open in Web Editor NEWThis is the portal, where all kinds of feedback related to a lab or an experiment is filled in.
License: Other
This is the portal, where all kinds of feedback related to a lab or an experiment is filled in.
License: Other
As of now all feedback forms are do not have captcha this resulting flooding of database by writing automation script
Answers with rating responses need to store relatively.
Example:
If the option is 'g'
Answer need to be stored as 7/10 instead of 7
feedback portal header page should be same as vlabs.ac.in latest version
29/08/16
The API that allows "get" works on the state variable that is a dictionary that stores all the attributes of an object. To provide the same API to a persistent object retrieved by sqlalchemy, currently the attributes are copied to the state variable. This is a deep copy. Instead a delegate should be provided for a persistence object that does not do a deep copy but still retrieves the attribute.
Footer page of the feedback portal to be changed same as http://vlabs.ac.in page
The users of virtual labs will able to give the feedback for non Open-edX Labs.
Hence, Generic Lab and Experiment level Feedback forms need to be implemented where Lab name
and Experiment name need to be given as inputs by the user.
REST API Design and implementation ca be found at https://github.com/vlead/feedback-portal/blob/master/src/runtime/rest/api.org#dump-college-details-into-the-elastic-database
REST API documentation can be found at : https://github.com/openedx-vlead/college-cloud/blob/cc-april-delhi/src/design/index.org#dump-college-cloud-data-to-elk
Response on point of the MoM of the PRSG meeting on 21st October 2016
Prof Suraish Kumar reviewed the feedback forms newly included in the feedback portal, just before the 21st October 2016 meeting. His review comments assess the forms to be ' much better than the existing ones' and OK for use.
He was also keen on the inclusion of 'dynamic' feedback at the experiment level for capturing the 'learning extent of the students'. He suggested a method of feedback capture at the experiment level.
In view of the above, the feedback forms introduced can be considered as approved.
The inclusion of the experiment level 'dynamic'feedback is to be taken up with the consent of the Lab Developers/Institute Integration Coordinators. This question is therefore left to them to take a call.
Detailed analysis of Recommendation:
Context:
The feedback forms proposed and included in feedback.vlabs.ac.in were reviewed by Prof GK Suraish Kumar. A document that analyzes the feedback forms in relation to a standard feedback framework, the objectives of vlabs and other general factors was prepared by VLEAD and shared with him. The document also did a comparative analysis of the earlier forms and the proposed forms.
Recap
To recap, the revised feedback forms introduced into the feedback portal of Virtual labs, were at the 3 levels:
At a Generic Level
At Lab Level
At the Experiment Level
Review Comments
Prof Suraish found these above forms much better than the existing ones. He however suggested that experiment level feed back to assess the "Learning extent of the students " was required to be incorporated.
The question of incorporating experiment level feedback is to do with the experiment technicalities and is a subject that the Lab designers are to address. Prof Suraish felt that the feedback capture must be smooth and periodic. He suggested that this should be captured after every 1 or 2 sections of the experiment done by the student. The questions may also be picked up from the current evaluation quiz at the end of the experiment. His observation was as follows:" ... The only thing I would add is to display the answer irrespective of the student response to the question, and smoothly move on to the next part in the experiment. The emphasis (as you have elaborated) is also on the smoothness of these queries, without making them appear as formal evaluations'. Thus, VLabs would have much better and natural input on the learning. If numbers on
student testing' are needed for various administrative needs of the project, they have become available too by this process."
"If the student desires his/her `score' at the end of the experiment, let the student explicitly click a button to know it.
In addition, the same questions that exist now as a separate and optional evaluation at the end of each experiment, if suitable, can be the questions that are placed at various parts of the experiment."
This the gist of the review done by Prof Suraish Kumar. For easy reference, the extracts of the mails exchanged with him on this subject [document 1] and the Analysis document [2 above] are made available.
When people access feedback.vlabs.ac.in link it should redirect to vlabs.ac.in link
Currently ,
feedback portal footer page is not same as current version of vlabs.ac.in page this is to be updated
REST API : https://github.com/vlead/feedback-portal/blob/master/src/runtime/rest/api.org#dump-usage-to-elk is throwing following error while running through a script.
"List indices must be be integer"
Feedback form version need to be captured in Feedback Database.
All the questions in the feedback form need to store form version along with question name and its type.
All the feedback data of v1.0.0 is part of Data Service data. This feedback data needs to be migrated to version v2.0.0 which is running as a separate feedback service.
Implementation code has to be modularized. Need to reuse the code wherever the same code is repeated.
Dump all old feedback forms data (from 2015-10-14 to till date) into elastic search database for kebana to visualize the feedback usage
The following list of entities to persist:
Utils package is update for more info please refer to https://github.com/vlead/feedback-portal/tree/master/src/runtime/utils
Currently APIs required to push the usage analytics, feedback analytics are implemented part of feedback service. Going forward we need migrate these APIs (3) to dedicated service
Feedback service has the APIs for kibana to use here is the API link https://github.com/vlead/feedback-portal/blob/master/src/design/index.org
Defect Description:
In the feedback page the search option is present at the top instead the search functionality should be removed
Actual Result:
In the feedback page the search option is present at the top
Environment :
OS: Windows 7, Ubuntu-16.04,Centos-6
Browsers: Firefox-42.0,Chrome-47.0,chromium-45.0
Bandwidth : 100Mbps
Hardware Configuration:8GBRAM ,
Processor:i5
As a Lab User, when feedback is submitted, feedback portal should capture the client User IP (or) Gateway IP from where the feedback is submitted. This IP will be used for further feedback analysis.
Header page of the feedback-portal to be changed same as vlabs.ac.in latest release. (http://vlabs.ac.in)
The following are the list of object entities:
Feedback Portal service to be upgraded on (AWS)
Meta Data of Answers need to be captured in Feedback Database.
Example:
Showing following error on browser console when submit a feedback
{readyState: 4, responseText: "{"error":"error: (oursql.InterfaceError) (2002, "âŠt '/var/run/mysqld/mysqld.sock' (111)", None)"}â”", responseJSON: Object, status: 500, statusText: "Internal Server Error"}
System holds all the operations which are invoked by the System interface. System checks all the State, Authorization, Arity and Type checks and then performs the action.
Portable hard drive has ported with 70 labs in it. All these labs feedback should be stored into local feedback service.
This issue was figured out by @raghupathi while checking feedback forms on protable hard drive.
We have quick fixed this issue on production as well as all testing machines.
A data model for Feedback Service is to be defined.
All the Requirements need to be captured for Feedback Service.
Attendees : vlead staff
Date: 16/09/2016
Feedback form footer and header to be same as its source's footer and header. Feedback when accessed from vlabs.ac.in to be directed to vlabs.ac.in and not open edX from the header
Final approved questionnaire needs to be updated on feedback form.
Added followings labels to the question (Please rate your experience)
labels : Not good , to some extent, very well
In next release of feedback portal makefile and init.sh files to be modified as per https://github.com/vlead/lab-data-service repository
Currently all the APIs related to post processing of college cloud are implemented as part of feedback service these apis are used by both college cloud as well AWS cloud services.
Test cases for both the scenarios need to be implemented
I have been working on testing OpenedX labs with all the links including feedback. Today I found that experiment level feedback form is not working. But it was working till yesterday
@Developers : Can you please look into this issue.
From the observation at workshop conducted in GMRIT college. All feedback forms are not accessible with the bandwidth (20kbps). Whereas it is working for above this bandwidth.
To debug this we should test all feedback forms with debug mode.
Feedback service design need to be captured
Rating descriptors (not at all, To some extent, Very well from 0 to 10) need to be displayed on page. check this for clarifications
Dynamic Feedback Form need to be designed and implemented.
This issue captures all the feedback given by integration team.
Position of radio button and numbers is cluttered..some additional spacing may be given.. How do I know what falls into "Not at all" or "To some extent", etc categories.
Message box should have "information/warning/stop" indicator to state the objective.. Usability !!
Why do we need to go to another page on submitting... why can't it be a message box stating (better usability) "Thank you for the feedback".. If you plan to continue to have a page, have a hyperlink on "close" option
Defect Description:
The feedback page footer is different from the landing page footer instead in both the pages the footer should be same.
Actual Result:
The feedback page footer is different from the landing page footer
Environment :
OS: Windows 7, Ubuntu-16.04,Centos-6
Browsers: Firefox-42.0,Chrome-47.0,chromium-45.0
Bandwidth : 100Mbps
Hardware Configuration:8GBRAM ,
Processor:i5
The following CRUD operations are implemented for "Question" Entity.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
đ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. đđđ
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google â€ïž Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.