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.

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

Add language information text field to pois #2799

Open
6 tasks
ztefanie opened this issue May 14, 2024 · 8 comments
Open
6 tasks

Add language information text field to pois #2799

ztefanie opened this issue May 14, 2024 · 8 comments
Assignees
Labels
💡 feature New feature or request ⛔ blocked Blocked by external dependency 🌈 ui-ux Issues that requires an UI/UX perspective. 😅 effort: medium Should be doable in <12h
Milestone

Comments

@ztefanie
Copy link
Member

ztefanie commented May 14, 2024

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: digitalfabrik/integreat-app#2794

Design Requirements

None.

@JoeyStk
Copy link
Contributor

JoeyStk commented May 14, 2024

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
Copy link
Member

MizukiTemma commented May 14, 2024

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 MizukiTemma added this to the 24Q2 milestone May 16, 2024
@MizukiTemma
Copy link
Member

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

@MizukiTemma MizukiTemma added the 📣 needs-internal-discussion Us developers need to discuss first which way of implementation is considered to be the best label May 16, 2024
@JoeyStk JoeyStk added the ❓ question Further information is requested label May 21, 2024
@dkehne dkehne modified the milestones: 24Q2, Backlog May 25, 2024
@dkehne
Copy link

dkehne commented May 25, 2024

#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..

@JoeyStk JoeyStk added 😱 effort: high Big change, which requires >12h 🌈 ui-ux Issues that requires an UI/UX perspective. ⛔ blocked Blocked by external dependency and removed ❓ question Further information is requested 📣 needs-internal-discussion Us developers need to discuss first which way of implementation is considered to be the best labels May 25, 2024
@JoeyStk JoeyStk modified the milestones: Backlog, 24Q2, 24Q4 May 25, 2024
@seluianova
Copy link
Contributor

seluianova commented May 25, 2024

Draft design 😀
PXL_20240525_131512718

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

@JoeyStk JoeyStk added 😅 effort: medium Should be doable in <12h and removed 😱 effort: high Big change, which requires >12h labels May 26, 2024
@nikolahoff nikolahoff self-assigned this Sep 2, 2024
@nikolahoff
Copy link

@JoeyStk "Decide on the state that a language can take on": state means language always or sometimes spoken, right?

@JoeyStk
Copy link
Contributor

JoeyStk commented Sep 4, 2024

"Decide on the state that a language can take on": state means language always or sometimes spoken, right?

Yes, exactly :)

@nikolahoff
Copy link

@MizukiTemma @JoeyStk here is the design for the language selection.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💡 feature New feature or request ⛔ blocked Blocked by external dependency 🌈 ui-ux Issues that requires an UI/UX perspective. 😅 effort: medium Should be doable in <12h
Projects
Status: Next Up
Development

No branches or pull requests

6 participants