Dataland v96.0: Release notes - d-fine/Dataland GitHub Wiki

DALA-1424: Improve Swagger UI experience (API-only)

Our Swagger UI, which documents the use of the API, has been enhanced with various descriptions and examples. Essentially all path variables and request parameters now have descriptions and examples (see the first screenshot), and the JSON schemas of request and response bodies now have more expressive example values (see the second screenshot).

DALA-5942: Export aliases for improved download functionality

We’ve improved the CSV and Excel data export functionality by introducing human-readable aliases for column headers, replacing overly technical field names (e.g. SCOPE_1_GHG_EMISSIONS_IN_T instead of data.environmental.greenhouseGasEmissions.scope1GhgEmissionsInTonnes.value). The original JSON export remains unchanged. A new toggle in the frontend allows users to choose between exporting with the original headers or the new aliases, with alias export only available when "Values only" is selected:

468632073-00dccc0f-d24f-4790-9f76-32da5988a422

DALA-6051: Data export: Columns that cannot have a non-null value should not be exported

In our previous logic we added columns to our data export (CSV and Excel) that never contained any values. For example, for the Eu Taxonomy Financials framework we exported a list of aligned activities and their values, and additionally we exported one new column that contained the reported data quality for all those activities, even though the user selected that they want to export values only, no additional information. That is now fixed.

DALA-6070: Change the appearance of "Nuclear and Gas" data

The column order for nuclear and gas datasets has been aligned across the platform. Previously, the live data view displayed the columns in the order CCM, CCA, CCM+CCA, which differed from both the reports and the Dataland UI, where the order is CCM+CCA, CCM, CCA.

DALA-6096: "Nuclear and Gas" metadata not displayed in certain situations

Metadata for nuclear and gas components with null values is now properly displayed in the frontend. Previously, when a component such as nuclearAndGasTaxonomyCapex had a null value but still included metadata like data source or data quality, this information was not shown in the UI. This has been corrected to ensure that metadata is displayed consistently, even when the component value is null, as is already the case for other components.