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

Collections have properties for content warning data #3098

Closed
4 tasks done
straleyb opened this issue Apr 22, 2024 · 0 comments
Closed
4 tasks done

Collections have properties for content warning data #3098

straleyb opened this issue Apr 22, 2024 · 0 comments

Comments

@straleyb
Copy link
Contributor

straleyb commented Apr 22, 2024

Descriptive summary

This ticket describes the need for works to include new properties which include true/false statements to blur on show page and search results as well as to display the content warning on the show page. This ticket is for the models to house the data and for indexing to index the data if needed.

  • Add property to collection that is a true/false for blurring image on show page
  • Add property to collection that is a true/false for blurring image on search results
  • Add property to collection that is a text value that contains the content warning statement.
  • Add in indexing needs to index the 3 properties into the proper fields.

Expected behavior

A collection can be created in a command line which includes the blurred image true/false statements and the content warning. The collection can be saved properly.

Related work

We need to lay out what these properties look like. Then we need to verify the system can handle to properties and then create the code which adds in the data. There COULD be extra work needed which ensures previously created objects get updated with content warning data (even if its "no content warning") and re-indexing may need to happen.

@lamtu1 lamtu1 self-assigned this May 22, 2024
@lamtu1 lamtu1 moved this from Ready to In Progress in Enhancement Workcycle 5 May 22, 2024
@lamtu1 lamtu1 moved this from In Progress to QA in Enhancement Workcycle 5 May 23, 2024
@straleyb straleyb moved this from QA to Done/Deployed to Production in Enhancement Workcycle 5 May 28, 2024
@straleyb straleyb self-assigned this May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Enhancement Workcycle 5
Done/Deployed to Production
Development

No branches or pull requests

2 participants