-
Notifications
You must be signed in to change notification settings - Fork 4
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
add module for processing input data and help set up ui #5
Comments
I've started on something else a bit smaller for some staff data and I think I will build part of the data module in that work. The data module will output a dataframe with:
I was wondering about the structure. Might be better as a dataframe containing list variables in some places. So each free text question would be a list like this: Then we could write modules that are capable of processing dataframes defined in this way, as long as we pass them a few lookup tables for Question names, theme categories, and criticality levels. Any thoughts @milanwiedemann ? |
Incidentally @milanwiedemann I'm going to try to build the data module so that it runs live off the pinned data, pulling in the data as needed (based on the date range selected) rather than pulling all 10 years through which is what it does now. This may be hideously unstable or slow, but may as well give it a try and see what happens, and it may be useful elsewhere like with clinical data |
This is pretty large and complicated and depends on work elsewhere. It's not as necessary for prototyping as I thought it was. I'm going to move it to 0.3.0 so it doesn't hold things up |
Sort of closed enough by #50 |
I haven't thought about it in detail but I think we need a separate data module that does all this stuff- looks at the data in the application and figures out what everything is, what the date column is, where the location columns are, what they're called and how many there are, all that stuff. The data module can feed the other modules data as well as meta data (number of columns, number of categories...)
Originally posted by @ChrisBeeley in #2 (comment)
The text was updated successfully, but these errors were encountered: