Describe the bug
In the Downloads page, chips informing the dataset format are duplicated.
Observed behaviour
There are two chips indicate to a same file.
Expected behaviour
There must be one for each file.
To Reproduce
Check where we are getting this data from.
Additional context
These chips are based on the downloads.json file that is created here in the POS.
downloads.json is feed by the metadata files in the ETL output.
The ETL will write the metadata in the output in this line. We set write-modehere to define how we are going to write the metadata. While it's set to append, if we run the the ETL multiple times in the same place without cleaning up after ourselves we potentially will have multiple metadata files for the same input.
So wee need to change the metadata write-mode to overwrite and see what will happen.
Describe the bug In the Downloads page, chips informing the dataset format are duplicated.
Observed behaviour There are two chips indicate to a same file.
Expected behaviour There must be one for each file.
To Reproduce
Additional context These chips are based on the
downloads.json
file that is created here in the POS.downloads.json
is feed by the metadata files in the ETL output. The ETL will write the metadata in the output in this line. We setwrite-mode
here to define how we are going to write the metadata. While it's set toappend
, if we run the the ETL multiple times in the same place without cleaning up after ourselves we potentially will have multiple metadata files for the same input. So wee need to change the metadatawrite-mode
tooverwrite
and see what will happen.