-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Display Table Metadata when asking user to 'Pick your starting data' #14596
Comments
Hi @PhilBailey70 |
It's similar, but I mean before you even start creating a question, rather than when you are in a question/dashboard
|
@PhilBailey70 You are talking about "Ask a question" > Simple/Custom question > "Pick your starting data" selector, whereas #9422 is both for that, and every other data-selector (like when joining tables etc in Custom question or database-selector in Native question). Would probably be a thing to look at, when cleaning up our selectors #4874 |
Cool thanks
|
I just enetered metadata descriptions for our databases into the Data Reference pages, expecting to see these descriptions shown when I created a new question. Surely this is one of the most obvious things you would want to tell your users i.e. what's in these databases...
I would like the list of databases to:
a) be much wider as I don't see why it has to be so restricted in size
b) to show any metadata descriptions from the Data Reference attributes.
It would be a natural extension to then see the table level metadata descriptions once you have selected the database.
There are other areas in the interface where this data could be shown too (e.g. Admin:Data Model & Admin:Databases) so perhaps you could put a Data Reference menu option in Admin to allow people to decide if/where to display the metadata descriptions.
It's hardly critical, but would help new users to have a better understanding of what the heck they might be looking at - so helps the self-service experience - one of the tool's major strengths.
⬇️ Please click the 👍 reaction instead of leaving a
+1
orupdate?
commentThe text was updated successfully, but these errors were encountered: