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

Integrate user reporting flow from Results Page #645

Open
obulat opened this issue Apr 29, 2021 · 0 comments
Open

Integrate user reporting flow from Results Page #645

obulat opened this issue Apr 29, 2021 · 0 comments
Labels
design: needed Needs a designer's touch before implementation can begin 🌟 goal: addition Addition of new feature 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: frontend Related to the Nuxt frontend

Comments

@obulat
Copy link
Contributor

obulat commented Apr 29, 2021

This issue has been migrated from the CC Search frontend repository

Author: annatuma
Date: Thu Jul 09 2020
Labels: ✨ goal: improvement,🏷 status: label work required,🙅 status: discontinued,🚧 status: blocked

We want to find a way to allow users to flag images from the Results page.

If a user sees an image they would want to report, it is likely they aren't comfortable with the image. They may abandon the Results page, or quickly enter a new query or filter, in order to not see the image anymore. They are less likely to click on the image they want to report, to then look for a reporting mechanism, which is available currently from the Single Result page.

Let's think about how we can integrate a reporting flow from directly within the Results page.

Original Comments:

annatuma commented on Thu Jul 09 2020:

To me, this is both a question of how we design it, but also if/how we can implement such an integration directly from the Results page.

Assigning to @zackkrida and @panchovm to think about when the time comes.
source
@obulat obulat transferred this issue from WordPress/openverse-frontend Feb 22, 2023
@obulat obulat added 🌟 goal: addition Addition of new feature 🧱 stack: frontend Related to the Nuxt frontend labels Feb 22, 2023
@github-project-automation github-project-automation bot moved this to 📋 Backlog in Openverse Backlog Feb 23, 2023
dhruvkb pushed a commit that referenced this issue Apr 14, 2023
@AetherUnbound
Tighten exception handling, always flush buffer (#645)
0072114 
* Use more specific exceptions when catching errors

Using "except Exception" and then continuing is dangerous, since it might be preventing the appropriate termination of a script.

* Use and catch a specific retries-exceeded exception

* Return total values committed by all stores

* Clean up comments

* Add unittest for failure mode

* More descriptive log message
@obulat obulat added design: needed Needs a designer's touch before implementation can begin 🟨 priority: medium Not blocking but should be addressed soon labels Aug 11, 2023
@obulat obulat changed the title Integrate user reporting flow from Results Page (original #1046) Integrate user reporting flow from Results Page Aug 11, 2023
@fcoveram fcoveram mentioned this issue Dec 22, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
design: needed Needs a designer's touch before implementation can begin 🌟 goal: addition Addition of new feature 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: frontend Related to the Nuxt frontend
Projects
Openverse Backlog
Status: 📋 Backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@obulat