Dataset logos are uploaded but not stored in the database

Description

When a user uploads an image to be used as a dataset logo, the file is correctly uploaded (generating dataset_logo.thumb140, dataset_logo.thumb48, and dataset_logo_original), but no information is saved in the database about the uploaded file.

This can lead to several issues:

• It's impossible to detect missing or corrupted files (no DB record to verify integrity).
• Difficult maintenance or migration (no link between DB and files).
• Security concern: no way to check if a file has been altered.

Suggested improvement:

Store metadata about the uploaded image in the database, such as:

• MD5 hash (or other file fingerprint),
• Upload timestamp,
• Possibly the original file name.

This would improve the robustness and traceability of dataset logo management.

Are you thinking about creating a pull request for this issue?

Our organization does not currently plan to address this issue.

No files, tests, or entry points are named. Start by tracing the dataset logo upload flow and the persistence model used for uploaded files, then determine how database metadata and schema changes are handled. Done means each uploaded dataset logo has stored metadata that can be used to relate and verify the generated files.