-
Notifications
You must be signed in to change notification settings - Fork 103
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 of data types in the R-Instat grid #6266
Comments
I would prefer different codes for different types of columns. I don't see a problem with users learning a few codes, particularly as they may not use all of them regularly, and only a few will be in a particular dataset. I feel that the general codes will be less useful and ambiguous, I don't really see an advantage to grouped codes. |
So, I now know what you don't want! a) Do you want to keep D for date, or change it to d? As you can gather, I really don't mind, but would just like us to make a decision! |
I understand this is now resolved and @dannyparsons will implement. |
Currently we define some types of data. This could usefully be extended - at least visually in the grid.
For example, from the structured menu, we can define columns to be
circular
. Then this is noted in the column metadata, but nothing is indicated in the name in the grid.We can now define columns as
survival
. This is not noted (currently) in the metadata, nor the grid.We will have low flow variables etc. there are lots of different ones.
We define dates as D. So far this is for daily data. We have date-time and time coming. How do we show this in the grid.
@volloholic suggestion is simple, and is as follows:
a) We use D - or should it be d for date, or date-time or time. They are all a date-time sort of thing.
b) We use s for structured, so this could be survival, circular, low-flow. It just indicates that it is defined.
Separately to this is that details of the structure, and the type of date is given in the metadata. So that needs to be added for the survival.
This needs @dannyparsons to check. If agreed it needs to be implemented.
If quicker for him to do than explain, then he should. Otherwise he could suggest who implements.
The text was updated successfully, but these errors were encountered: