Add language information text field to pois

[ztefanie]

Motivation

In our target group interviews, we (= target group team) got the input, that end users are insecure about going to pois, because they do not know if the language they know are spoken there. As which language is spoken is very different for every location, we want a text field, and hope the cms users will fill it with, e.g. "on thursday afternoon russian, on other days only german an englisch", or similar.

Proposed Solution

• [ ] Decide on a design
• [ ] Decide on the state that a language can take on
• [ ] For each state add a multi select for languages
• [ ] Add checkbox for default text instructing users to check the description or seek the organization for further information
• [ ] Inform users that even if their language is not listed, it might still be arranged/available.
• [ ] Put it out in API

Alternatives

We discussed if we just tell the cms users to add this information to the description field, but having this field is a constant reminder and as it is a important feature for the target group, we decided adding this field is the best way to go.

User Story

As a app user I want know if at a poi my language is spoken so that I know if it is worth for me to go there. As a cms user, I want to add information about languages spoken at a poi.

Additional Context

See: https://openproject.tuerantuer.org/projects/community-feedback/work_packages/3231/activity blocks: https://github.com/digitalfabrik/integreat-app/issues/2794

Design Requirements

None.

[JoeyStk]

This is pretty similar to #2421, which was closed as it was doubtful whether or not this would be properly filled in by the municipalities and would actually be helpful. I suppose it's up to us to do some careful research about it

[MizukiTemma]

Another point of discussion was that it can lead to exclusion: for example, when the (mightiest) languages of an user is not listed or the listed languages give an impression that the POI is only for certain (ethnic) groups, they may feel not welcomed.

[MizukiTemma]

This issue was added to the milestone Q2 so we don't forget to come back to the discussion. Feel free to move it.

[dkehne]

2421 was closed because it was not flexible/adjustable and this issue #2799 is a compromise to enable municipalities to add infos in their own way, if they want.

from the feedback of the target group it become more significant again..

[seluianova]

Draft design 😀

@nikolahoff For further information you can contact @MizukiTemma. We would like to start working on this issue around October :smile:, so not really urgent :)