Database Management View Instead of Datasets/ETLs view

NateBI

Currently users view their assets in a list in the Data tab. They have to use naming conventions, or tags to group these assets and the same goes for ETLs. The list can be filtered and includes shared assets by default but regardless it quickly becomes a mess that only encourages redundant asset creation due to low visibility and lack of options for better organisation.

A more "industry standard" view would be to present assets within a database management GUI design. Users could view their assets in relation to a project and/or a database layer like RAW, SRC, MART. Within these projects/databases ETLs could be deconstruced into blocks of code or SHORT MagicSQL flows (people already do this to avoid creating huge flows) to generate templates that could be tested and shared.

Tihs layout naturally encourages people to consider better govenerance practices aligns with other tools in the industry that prioritise quality assurance.