DUPLICATE OF
☑ cool new feature
☑ could help many users!
☐ removes a „bug“
☐ nice to have
☐ nobody needs it
#myTop10_2024
What inspired this wish list request?
Often incoming data is quite cryptic and some data curation is needed.
Jmp already provides nice solutions, which help the user to curate the data "on the fly", like recode.
Many of the curation steps are "persistent" - such that no further curation is needed when the data table gets updated with the latest data:
- formula columns
- column property: Value Label
- ...
A special issue are column names:
Here there is a clear trade-off between human-readability and compatibility to incoming data.
- The user might rename a column - but then the data table cannot be updated anymore.
- the user might add an additional column with the correct name and link it to the original column by a column formula - but this approach is just useful for a few column names.
- possibility to give columns different names in different languages
- save the alternative name as a new column parameter + Script to toggle between original and alternative column names.
https://community.jmp.com/t5/Discussions/Ho-to-handle-cryptic-Column-names/m-p/722751/highlight/true...
I guess everyone has found their own workaround to deal with the problem.
Surprisingly, there is no "official" solution, like column alias
What is the improvement you would like to see?
Please add a new column property: Column alias
If a column alias is defined,
- the alias column name replaces the column name in the table header, all lists, reports, plots and views.
- the alias column name can be used alternatively in filters (so the user can search with the original and the alternative name)
- it can be used in Table operations like update and concatenate - as an alternative to the original column name
Why is this idea important?
Significant simplification of data curation
6 Comments