Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Independent questionnaire language #1575

Open
janno42 opened this issue Mar 14, 2021 · 5 comments · May be fixed by #2367
Open

Independent questionnaire language #1575

janno42 opened this issue Mar 14, 2021 · 5 comments · May be fixed by #2367
Assignees
@hansegucker
Labels
[C] Backend Focuses on backend implementation [C] Frontend Focuses on frontend implementation [P] Major Major priority
Milestone
Winter 2024

Comments

@janno42
Copy link
Member

janno42 commented Mar 14, 2021 •
edited
Loading

The language of questionnaires should optimally fit the course's teaching language to encourage participants to think and answer in the language usually used within the course.

Therefore, the following things should be changed:

  • The language in which questionnaires are shown should be made independent from the page's overall language. An additional switch button should be added at the top of the voting page, which changes the questionnaire's language. (see https://docs.djangoproject.com/en/5.1/topics/i18n/translation/#switching-language-in-templates)
  • A new selection field "Main language" should be added to Evaluations, with the options "English", "German", and "Undefined" (or empty). Only staff users should be able to set it to "Undefined"; editors should be forced to choose a language.
  • When opening a voting page, the questionnaire per default should be shown in the language set as the main language for the respective evaluation. If the main language is undefined, the page's current language is used.
  • When a participant changes the questionnaire's language, this choice should be stored and used when reopening the same questionnaire.
@janno42 janno42 added [C] Backend Focuses on backend implementation [C] Frontend Focuses on frontend implementation [P] Medium Medium priority labels Mar 14, 2021
@karyon
Copy link
Collaborator

karyon commented Mar 14, 2021

Could you elaborate on the reasoning? I also think it's a little weird to have english comments in an all-german course because someone preferred to have the website displayed in english, but... why does it matter?

@janno42
Copy link
Member Author

janno42 commented Mar 15, 2021

During the last semesters, we received several messages stating that it would be easier for participants to display the questionnaire in the teaching language. Sometimes people start answering the questions only then to notice that the other language would be better and rewriting everything.
Also, the number of courses taught by people only able to speak one of the supported languages increased, making it more important to provide feedback for the contributors in the appropriate language.

@karyon
Copy link
Collaborator

karyon commented Mar 19, 2021

makes sense, thanks!

@pixunil
Copy link
Contributor

pixunil commented Apr 23, 2021 •
edited
Loading

Some little clarification questions / thoughts:

  • For me, it would be logical to use the questionnaire language also for results (I didn’t see it written out explicitely). This would imply that we have the same language control widget on both pages. Also, the selected user language for each individual evaluation must be saved not only for the voting period, but also until later, when the results are published (As a reminder that the implementation can not rely on a field of the voting form)
  • For consistency I ask myself whether it is sensible to have a configuration for each evaluation or whether it would be better to have a configuration for a group of evaluations. Possible variations include: instead for a single Evaluation, for a single Course, or one configuration for several Courses (which would be the same course across mulitple semesters).
  • When editors are forced to decide for an evaluation language, can staff only choose “Undefined” after editor have approved of the evaluation? Otherwise, we have to sensible handle a pre-selected “Undefined” language when the editor can only change away from it, but not to it.

@janno42 janno42 mentioned this issue Oct 15, 2021
Merged
@janno42 janno42 added [P] Major Major priority and removed [P] Medium Medium priority labels Oct 7, 2024
@janno42 janno42 added this to the Winter 2024 milestone Oct 7, 2024
@janno42
Copy link
Member Author

janno42 commented Oct 7, 2024

  • A language selection for the results page is not in the scope of this issue, as it is only meant to guide people to answer in the preferred language.
  • The language of the questionnaire should be set per Evaluation, because editors can't edit Courses.
  • Staff can always choose "undecided".

@hansegucker hansegucker mentioned this issue Jan 13, 2025
Open
@richardebeling richardebeling linked a pull request Jan 19, 2025 that will close this issue
Main language for evaluations #2367
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hansegucker hansegucker

Labels
[C] Backend Focuses on backend implementation [C] Frontend Focuses on frontend implementation [P] Major Major priority
Milestone
Winter 2024
Development

Successfully merging a pull request may close this issue.

Main language for evaluations hansegucker/EvaP
4 participants
@janno42 @karyon @pixunil @hansegucker