-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Creating a visual schematic diagram for data wrangling workflow in {datawizard}
#87
Comments
What would it contain? I can start a draft with powerpoint |
@DominiqueMakowski How about something like this? (cc @bwiernik, @strengejacke, @mattansb, @etiennebacher) Of course, there is a lot of room for improvement here. Specifically,
|
I can give it a go next week (do ping me then if you remember :)
It's okay not to be comprehensive otherwise we will be obsolete as soon as we add a new function, better perhaps to create like a wordcloud or something like that |
Yeah, I agree. That's why I had put the |
I think a separate viz of data cleaning versus data summary functions would be good |
@DominiqueMakowski It will be nice to have something like this in the JOSS paper. |
Will do within the next couple of days |
Would be nice to generate a wordcloud of the functions tho |
Wordlist for wordclouds (https://www.wordclouds.com/):
data_filter()
standardize() |
you're right, I'll come up with a diagram prototype nonetheless and then we can fine-tune the wordcloud |
Thanks, Dom! This looks like a great start. I think one way this can be improved is by making it visually less busy and more minimal. Additionally, we need to mention only a few (key and most useful) functions and just have I don't like the star shape in the "Transformations" section. Maybe this can be an ironing table with a shirt on it? Instead of "No dependencies", I'd write "Lightweight", since we do import |
I also want to hear what @etiennebacher, @strengejacke, @bwiernik, @mattansb think about the current status of the illustration and how it can be further improved. |
I agree with Indra's comments and don't have much more to add there. I like the ironing metaphor (maybe the function names in a cloud of steam?). And agree that making the function names less busy/stand out more would be good |
Looks good. I would maybe change the color of the bg color of the washing machine to a lighter blue? And for transform use the non |
Looks good to me too, but it's a bit hard to read most function names in steps 2 and 3. Maybe you can remove the very small ones to increase the size of the others? |
Thank you all for great suggestions! WDYT, @DominiqueMakowski? Will this be possible? Don't know how complicated it will be to design. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
@DominiqueMakowski Let us know if these suggestions make sense. |
bump |
bump |
Is that the correct list? Preparation: Transformation: |
thanks for the bumps 🙊 |
These need to change to their new names:
Btw, feel free to not include all of them. Whatever looks better with the chosen graphic design. |
recode_values() not change_code() |
bump |
IMHO, the current
README
is quite dull and long-winded, and doesn't provide much insight into how this package can be useful for the users.What we need is for it to feature a visual schematics like the following ones in our other popular high-level packages:
Of course, paging our in-house visualization wizard @DominiqueMakowski! 🪄
Needless to say, this is low-priority and if you think so necessary, we can definitely wait for the package to even mature further.
The text was updated successfully, but these errors were encountered: