Create an "acknowledgement of harmful content" type page #2595
Labels
🕹 aspect: interface
Concerns end-users' experience with the software
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
Problem
This is somewhat related to #2550 and could potentially be merged into it
Also related to #2593.
Openverse aggregates works from sources that include catalogue materials with harmful (racist, violent, colonial, etc) content. For example, this result from Boston Public Library includes a violent racial slur both in the title and the text in the image (CW: racial slurs, racism). This work is sourced from BPL but hosted on Flickr. The Flickr page does not include any information about the historical context of the work either, so this example would not be covered by #2593, though the image would be marked sensitive based on the sensitive text detection work.
However, none of that would necessarily make it clear why Openverse displays such content.
Description
In addition to #2550, either as a section of that page or a separate page altogether, make explicit the fact that Openverse aggregates works from sources that hold works in their collections that include harmful content. I don't think we need to use the term "sensitive" in this particular case, because we're discussing specifically works that have been used to harm specific communities. This is different from "sensitive" in a sense because it's universally true that racial slurs have been and are used to harm people, whereas "sensitivity" is more about subject tolerance of exposure to such things and also includes broader things like nudity which aren't necessarily harmful. The distinction is important.
The link to this page should be available in the pages menu and either:
My preference is the first one with the third one being a runner-up if we need to exclude it from some providers for some reason. I don't think the second one is viable because it would require us to decide which of the terms in our sensitive terms list are "harmful" vs "sensitive".
This would need to be available alongside provider-specific links to similar acknowledgements/explanations as described in #2593.
The text was updated successfully, but these errors were encountered: