Alright, now I'm all done with the metadata instructions and examples. Let's do some meta :)

We created some metadata 4 the HH paper which could be implemented

Since the table in the issue description is not that easy to edit and read, I created one on the cloud (1_Arbeitsinhalte/AP1/metadata/). I extracted the list of tables from one of the last CI-runs, so it should be up to date.
We will take care about moving all the entries from the table in this issue to the table. But not all rows are filled here, so we might need some help from you.

Thank you @ClaraBuettner :) Will you let us know, when entries are moved to the cloud table? Then we will continue filling it out there.

Some thoughts about table relations:
I think it'd be helpful to know to what other table the fields in resources fields refer to. A good place could be the field description.
Something like

            "schema": {
                "fields": [
                    {
                        "name": "zensus_population_id",
                        "description": "ID of Census cell, refers to field society.destatis_zensus_population_per_ha_inside_germany.id",
                        "type": "serial",
                        "unit": null
                    },

Or, if applicable, via the foreign key.
This makes it easier for users to join multiple tables (additional to example queries).

Thank you @ClaraBuettner :) Will you let us know, when entries are moved to the cloud table? Then we will continue filling it out there.

Yes, @Alonsoju95 will let you know.

Hi, everyone!
All entries have been moved to the cloud table.
The link: https://wolke.rl-institut.de/s/9RyJKLP2HRGxdYf

I created a new tab 'Tables' in the mentioned document on the nextcloud, where I removed all the duplicates etc.

For the following tables I need the sources even if they are not in need of metadata:

demand.egon_etrago_electricity_cts
demand.egon_demandregio_sites_ind_electricity
demand.egon_osm_ind_load_curves_individual
demand.egon_sites_ind_load_curves_individual