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

Feedback for unsuccessful searches should be sent automatically #2969

Open
osmers opened this issue Oct 23, 2024 · 7 comments
Open

Feedback for unsuccessful searches should be sent automatically #2969

osmers opened this issue Oct 23, 2024 · 7 comments
Labels
discussion-needed Native Affects the native project Task waiting-for-cms Web Affects the web project

Comments

@osmers
Copy link

osmers commented Oct 23, 2024

Is your feature request related to a problem? Please describe.
Currently we have an extra obstacle for users to communicate and also for municipalities to get to know content that is currently missing from the app but being searched for by the target group.

Describe the solution you'd like
When a term is searched and returns no results, the feedback form opens and allows users to send in their failed query. It could be helpful to send it, even if users navigate away from the feedback form in order to give municipalities more information without users having to become active.

Describe alternatives you've considered
We keep it, as it is - maybe also bcs of potential problems such as "misuse" by bots or humans. That could create many non relevant feedbacks for municipalities.

Additional context
We had this idea bcs we were discussing how to give municipalities more confidence in the quality of their content and one aspect is knowing that they cover the information their target group needs/seaches for.

@ztefanie
Copy link
Member

I understand this requirment and as integreat is only as good as the content, i think we should think of a solution. To avoid "spam" that is caused by typos, i have a few ideas:

  1. in the app we add a "did you mean" feature. I think this would be nice for the user experience anyways.
  2. We add a "automatic feedback" flag to the feedback sent without the form and in the cms the automatic feedback is displayed differently, e.g. grouped by search results with a counter how often these words have been searched @digitalfabrik/cms-team

@steffenkleinle
Copy link
Member

steffenkleinle commented Oct 25, 2024

This is loosely related to #2926 which includes a design if no search results are found.

@steffenkleinle steffenkleinle added Web Affects the web project discussion-needed Native Affects the native project labels Oct 25, 2024
@ztefanie
Copy link
Member

ztefanie commented Nov 5, 2024

I understand this requirment and as integreat is only as good as the content, i think we should think of a solution. To avoid "spam" that is caused by typos, i have a few ideas:

  1. in the app we add a "did you mean" feature. I think this would be nice for the user experience anyways.
  2. We add a "automatic feedback" flag to the feedback sent without the form and in the cms the automatic feedback is displayed differently, e.g. grouped by search results with a counter how often these words have been searched @digitalfabrik/cms-team

@osmers Can you please add you thoughts what you think about this approach?

@osmers
Copy link
Author

osmers commented Nov 5, 2024

Sorry @ztefanie :)
I think the first idea would be really good and I'd like to add that a "similar" suggestion came from the city of Regensburg: https://tasks.tuerantuer.org/wp/3722 (it includes adding a Stichwortsuche to avoid spelling mistakes - see last comment with screenshot in the issue)
The second idea is definitely helpful for admins in the municipalities and I'll check with the CMS team, but I assume that adding the flag shouldn't be too complicated. The grouping is already done for positive or negative reviews, not sure if it's also done for the same search word. If not, that would be good too. I'd make this two different issues for the CMS team and it would probably make sense to implement the CMS side first and then the app side, right?

For the app we could start with the first suggestion as this could already help.
Please add your thoughts on a Stichwortsuche or whether having both would be doppeltgemoppelt :)

@ztefanie
Copy link
Member

ztefanie commented Nov 5, 2024

Hi @osmers
Thanks fot the feedback.

Ok please create the two tickets for cms and link them here.

I will create a ticket for UI/UX how to realize the Schlagwortsuche / Did-you-mean-suggestion.

@ztefanie
Copy link
Member

ztefanie commented Nov 5, 2024

Releated to: #2981

@osmers
Copy link
Author

osmers commented Nov 5, 2024

CMS issue for label: digitalfabrik/integreat-cms#3171
CMS issue for cummulative feedback: digitalfabrik/integreat-cms#3172

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion-needed Native Affects the native project Task waiting-for-cms Web Affects the web project
Projects
Status: No status
Development

No branches or pull requests

4 participants