Add batched catalog_cleaner DAG

[krysal]

Fixes

Related to #3415 by @obulat

Description

WIP. Tested with TSV files found in the S3 bucket .../shared/data-refresh-cleaned-data. The files for titles and tags were missing so I made only for URL fields.

Testing Instructions

To try locally, store the TSV files in tha DAG's folder. You will also need some of the dirty data there from upstream I'll prepare a file later but if you have access, you can download and upload the file as follows.

1. Download upstream sample data. These sources are two of the ones that need the HTTP protocol in the image or creator URL.

# Taken from upstream db
\copy (SELECT * FROM image WHERE source IN ('animaldiversity', 'geographorguk') LIMIT 20000)
     TO '/tmp/bad_rows_sample.csv' DELIMITER ',' CSV HEADER;

2. Start the catalog stack

just catalog/up

3. Copy the sample data to the database container

docker cp /tmp/bad_rows_sample.csv openverse-upstream_db-1:/tmp/bad_rows_sample.csv

4. Copy the sample data to the database

just catalog/pgcli
\copy image from '/tmp/bad_rows_sample.csv' WITH (FORMAT CSV, HEADER)

Checklist

• My pull request has a descriptive title (not a vague title likeUpdate index.md).
• My pull request targets the default branch of the repository (main) or a parent feature branch.
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added or updated tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no visible errors.
• I ran the DAG documentation generator (if applicable).

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[github-actions]

Full-stack documentation: https://docs.openverse.org/_preview/3601

Please note that GitHub pages takes a little time to deploy newly pushed code, if the links above don't work or you see old versions, wait 5 minutes and try again.

You can check the GitHub pages deployment action list to see the current status of the deployments.

Changed files 🔄:

• https://docs.openverse.org/_preview/3601/catalog/reference/DAGs.html

[obulat]

This is fantastic, @krysal! I'll be testing this PR locally, thank you for the detailed instructions on getting the data from prod.
I have a note on the name for this DAG: I believe this DAG could be used for updates that are not related to cleaning in the future. For instance, if we create a DAG that collects the filetype data in the same format (CSV with identifier and filetype), we could use this DAG. We could also use it for machine-generated tags (but I guess this would require upsert, not just replacement?), or the dimensions data (width, height - but this would also require updating the SQL command to allow for updating 2 columns at once?)
I'm not suggesting the addition of this functionality (upserting, handling of more than one column) in this PR, but I think changing the name of the DAG here to allow for these additions later could be appropriate. Or do you think it's better to create new similar DAGs later, @krysal?

[krysal]

I have a note on the name for this DAG: I believe this DAG could be used for updates that are not related to cleaning in the future. For instance, if we create a DAG that collects the filetype data in the same format (CSV with identifier and filetype), we could use this DAG.

@obulat That sounds like an interesting approach! I was focused on the case we have at hand, but I see it can be useful to generalize the DAG. I'll take note and close this for now given the project needs an official proposal plus an implementation plan. Also, sorry for taking so long to respond! I had to focus on other unfinished routes. This will be resumed in no time.