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

Create a data management command to copy data from the old mature tables to the new sensitive ones #2627

Closed
AetherUnbound opened this issue Jul 11, 2023 · 1 comment
Labels
💻 aspect: code Concerns the software code in the repository 🌟 goal: addition Addition of new feature 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: api Related to the Django API ⛔ status: blocked Blocked & therefore, not ready for work 🔧 tech: django Involves Django

Comments

@AetherUnbound
Copy link
Contributor

Description

Create a Django data management command which will move data from the previous mature-related tables to the new sensitivity-related ones. Instructions for how to perform this change are present in the implementation plan associated with this work: https://docs.openverse.org/projects/proposals/trust_and_safety/content_report_moderation/20230517-implementation_plan_mature_copy_change.html#code (steps 4-5).

A deployment of the API will be necessary before handling downstream tickets.

Additional context

Part of #383, blocked by #2626

@AetherUnbound AetherUnbound added 🌟 goal: addition Addition of new feature 💻 aspect: code Concerns the software code in the repository 🔧 tech: django Involves Django 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: api Related to the Django API labels Jul 11, 2023
@AetherUnbound AetherUnbound added the ⛔ status: blocked Blocked & therefore, not ready for work label Jul 11, 2023
@AetherUnbound
Copy link
Contributor Author

Closing in favor of #3723 based on #3568.

@AetherUnbound AetherUnbound closed this as not planned Won't fix, can't repro, duplicate, stale Jan 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository 🌟 goal: addition Addition of new feature 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: api Related to the Django API ⛔ status: blocked Blocked & therefore, not ready for work 🔧 tech: django Involves Django
Projects
Archived in project
Development

No branches or pull requests

1 participant