Document the use of each column and guideline for selection from sources #1410
Labels
📄 aspect: text
Concerns the textual material in the repository
🌟 goal: addition
Addition of new feature
🟧 priority: high
Stalls work on the project or its dependents
🧱 stack: catalog
Related to the catalog and Airflow DAGs
Current Situation
As part of the Data Normalization project and per recent feedback from new contributors, we need to have a clear understanding of what is the meaning and use of each database column. This indeed to add a broad description given that each provider has particular particularities that should be documented in its provider script or doc describing the particular script.
Image table
Audio table
Suggested Improvement
Document in markdown tables the following information for each media db table (currently
image
andaudio
).Benefit
After this should be easy to point to newcomers and recall what is the meaning of each table.
Alternatives
We could keep the notes directly on each database table. PostgreSQL supports a
COMMENT
SQL command that can be applied to columns, constraints, functions, etc. It's not in the SQL standard but many DBMSs support something similar. The con of this approach is that it is more hidden than a simple markdown document, there is no public access to the database and therefore people will have to reach the code to see them anyway. I wonder if this is a common/popular way to document a database.Additional context
Depends on:
The text was updated successfully, but these errors were encountered: