Skip to content
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

If a user wants to know the definition of a data field in a GEAR report, how can we best display that data to them #250

Open
hatfieldjm4 opened this issue Mar 6, 2024 · 0 comments
Assignees
Labels
DEV Relates to work in the development environment documentation Improvements or additions to documentation help wanted Extra attention is needed question Further information is requested

Comments

@hatfieldjm4
Copy link
Collaborator

Using the GEAR GUI Data Dictionary, how can we improve the user experience to display the definition of a data field in GEAR if the user would like more information about the definition/intent of the data field? Should we create a database object for the data dictionary, create APIs for it, and somehow reference it on the front end when a user hovers over a column header?

Perhaps we can start with an easy solution and then prioritize a better solution after launch. Let's discuss any ideas you have.

@hatfieldjm4 hatfieldjm4 added documentation Improvements or additions to documentation help wanted Extra attention is needed DEV Relates to work in the development environment labels Mar 6, 2024
@hatfieldjm4 hatfieldjm4 added the question Further information is requested label Mar 7, 2024
hatfieldjm4 added a commit that referenced this issue Mar 12, 2024
…. This also addresses the 'easy solution' portion of issue #250, though a more elegant solution for users consuming the data dictionary will be needed.
@github-project-automation github-project-automation bot moved this to In progress in Deploy GEAR 3.0 Aug 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DEV Relates to work in the development environment documentation Improvements or additions to documentation help wanted Extra attention is needed question Further information is requested
Projects
Status: In progress
Development

No branches or pull requests

3 participants