Any data catalog options for Shared Datasets?

[Anonymous]

We are currently working on a project to help users create their own reports and analyses using Shared Datasets.  Our planned architecture relies on creating new models in Analysis Services and then publishing them to our users as Certified Shared Datasets.  Most of the data will be fed from SQL tables; however, some calculated columns or measures will be needed.  

My problem is this...How do my users figure out what is in the datasets and what the various fields mean?

Right now, my users are NOT familiar with the data we have or how it is connected.  There are also a variety of definitions that are used by various groups.  We have been exploring using a Data Catalog product like Azure Purview, but it doesn't provide any insight into the datasets.  Ideally, I would like to provide a solution that allows a user to search by a field name, see it in the data model, and get a definition for that field.  It would be even better if it allowed them to see some sample data.

I have been trying to research the problem, but I haven't found any solutions (or maybe I am just looking in the wrong place).  

[StefanoGrimaldi]

hey, you can make this inside the model to certain extend, and users when creating new reports based on that dataset or using a excel power pivot connected to it can access the information, you can group in folders the columns inside each table, you can put on each table descriptions on what its inside that table or what its used, you can put in description to each column separately, if given a momment can provide example of each (note: using intuitive column names, and table name its a most for what you want, like really important here):

[Anonymous]

Thanks for the extra screenshots.  I am going to start trying to play around with this and see if this is a viable solution.  

[StefanoGrimaldi]

[StefanoGrimaldi]

you see , they can see the information you put on the model in the report creation view and the excel power pivot to know what that columns means, you can put information about relationships ,set up synomous etc. also hidding key columns used for relationship with dimensional tables helps, so that only the dimensional columns are avaible for the report and they dont use a key column by mistake etc. 

[lbendlin]

Azure Purview seems to go in that direction. Other companies use open source tools like Apache Atlas. 

Don't expect any turn key solutions. This is hard, hard work.

[Anonymous]

Thanks, @lbendlin.  I was hoping that Azure Purview might help, but unfortunately, it doesn't give the ability to see inside the datasets or annotate the data in any way.  I am 100% okay with handling the documentation and notation (and understand it is going to be hard work), but I was hoping it might be able to do the discovery like it can do natively with SQL tables.  I will take a look at Apache Atlas and see what kind of functionality it might offer.