As you are aware, we have deployed the ODD platform in our organization, and it has been in production for the past two months. ODD is not only functioning as a data catalog but also as a platform for downstream automation and governance. The tool is well-received by our community and is now a gateway to our data landscape, with an overall positive outlook.
As it begins to be utilized more and more as a catalog (quite often by non-technical users), there are a number of minor aesthetic / GUI design choices that are constantly being fed back for improvement proposals.
Today the number one request is that the "About/Description" section (on the data entity overview interface) should be at the top, and the metadata should be at the bottom.
The main reasoning for this is that as users come into the page the primary wish is to have an understanding of what exactly this dataset contains/is about & hence should be the first thing a user sees.
We can appreciate that design choices are somewhat ambiguous, but have seen (internally here at least) it's an opinion that was overwhelmingly supported by everyone and hence would love to contribute to implementing these changes from our side.
As you are aware, we have deployed the ODD platform in our organization, and it has been in production for the past two months. ODD is not only functioning as a data catalog but also as a platform for downstream automation and governance. The tool is well-received by our community and is now a gateway to our data landscape, with an overall positive outlook.
As it begins to be utilized more and more as a catalog (quite often by non-technical users), there are a number of minor aesthetic / GUI design choices that are constantly being fed back for improvement proposals.
Today the number one request is that the "About/Description" section (on the data entity overview interface) should be at the top, and the metadata should be at the bottom. The main reasoning for this is that as users come into the page the primary wish is to have an understanding of what exactly this dataset contains/is about & hence should be the first thing a user sees.
We can appreciate that design choices are somewhat ambiguous, but have seen (internally here at least) it's an opinion that was overwhelmingly supported by everyone and hence would love to contribute to implementing these changes from our side.
Attaching the screenshot for reference :