Workshop feedback page about wye HOT 19 CLOSED

@vnbang2003 I can take it up. Let me know if its fine.

from wye.

@shankisg If you plate is full let me know. We need to be a bit aggressive for next few days.

from wye.

@shankisg Can we make it high priority . We can hold other PR if required ?

from wye.

@vnbang2003
I assuming nothing has been implemented for feedback. Thinks I need to do

• Feedback models design
• Share feedback link with organisation and tutors.
• Then adding constraints for organisation and tutors to complete feedback else not allowing then go ahead with next workshop.

Questions

• What are the points we should add for feedback. My recommendation below and add you points also
  • Content of the workshop
  • Gained a good understanding
  • Trainer was well organised
  • The trainer was friendly and approachable
  • The venue was comfortable (relevant for tutor)
  • The length of the workshop was appropriate
  • Students participation (relevant for tutor)
  • Overall Rating
  • Extra comments
• Organisation have multiple user associated. Whether feedback is compulsory for all the users of the organisation, or if one user of the org share feedback that will work.

For more workshop survey question http://www.utas.edu.au/it/records/support/workshops/feedback

from wye.

We already have models WorkshopRatingValues, WorkshopVoting and WorkshopFeedBack.
We need to implement logic where we ask them to rate workshop for different type

1. Infra
2. Co-operation
   and others.

from wye.

Yes we need to add multiple choice and ask them to rate it.

from wye.

But in any of the models above we not maintaining any reference to user/presenter/organisation, to know has vote or not.

from wye.

@shankisg we need to rate for workshop . Each workshop completed will have presenter and requester.

from wye.

Thats true, but somewhere need to store which presenter or requester have shared the feedback.

from wye.

requester_rating = models.ForeignKey(
WorkshopRatingValues, related_name='requester_rating')
presenter_rating = models.ForeignKey(
WorkshopRatingValues, related_name='presenter_rating')
It show different in rating .

from wye.

@vnbang2003

Implementation of next part will contain

• Restricting organisation to add workshop unless they complete feedback
• Restricting presenter to take up next workshop unless they complete feedback
• Display message to presenter/organiser to share feedback.

Question:
If one presenter and one organisation had already share the feedback, are we going to show the share feedback message Yes or None.

from wye.

We will show already existing message and allow other to share if they want.

from wye.

@shankisg I think the basic version is check in right ?

from wye.

@vnbang2003
Following logic has been added for feedback

• Dynamic generation of feedback form depending on question in WorkshopRatingValues.
• Form will display all the questions from WorkshopRatingValues models plus a comment box.
• The workshop url will throw 404, unless workshop is completed.

So the restriction logic for feedback is pending. What you say?

Last question, when should we stop displaying message asking to share feedback. The problem here I am trying to point out is we are not tracking users(may be tutor or a organisation user) who have shared their feekback, so we don't know whom to display the message.

from wye.

@shankisg We can take who gave feedback in version 0.2 . You can open issue and mark for milestone v0.2. Let focus to get basic functionality up

from wye.

@vnbang2003
By Today I will add a pull request for organisation and presenter restriction logic to share feedback.

from wye.

@vnbang2003
one question
For presenter we are storing user_type as TUTOR, but what is the user_type for organisation users.

from wye.

For Organisation user type is POC or regional POC.

from wye.

ok

from wye.