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

Nice-to-haves #185

Closed
aspina7 opened this issue Sep 18, 2019 · 8 comments
Closed

Nice-to-haves #185

aspina7 opened this issue Sep 18, 2019 · 8 comments
Labels
discussion enhancement New feature or request

Comments

@aspina7
Copy link
Member

aspina7 commented Sep 18, 2019

[sitrep::msf_dict] consider a simpler way to have an overview of vriable value options - clicking in to each one defeats the purpose of reading in a dictionary (should be able to have dictionary open and look things up while recoding). Also double check that the value options that are produced are correct (though this seems to be have been a one-time issue. comment

@aspina7 aspina7 added enhancement New feature or request discussion labels Sep 18, 2019
@aspina7
Copy link
Member Author

aspina7 commented Sep 18, 2019

[Sitrep - renaming vars] making non-DHIS datasets fit is very painful. Add explanation of sitrep::msf_dict_rename_helper() - also add to this function to say whether those variables are OPTIONAL or NECESSARY for the template to run. Consider also changing variables to alphabetic order.
comment comment 2 comment 3
This should also address comment 4 and clarify what class variables need to be, e.g. sex as a factor (also add to notes?)
Cross reference with the [variable names & data dictionary] point under training heading above.

@aspina7 aspina7 mentioned this issue Sep 18, 2019
50 tasks
@aspina7
Copy link
Member Author

aspina7 commented Sep 18, 2019

create functions to add sample size calculations see #5

@aspina7
Copy link
Member Author

aspina7 commented Sep 18, 2019

Consider changing rmd outputs to those from officer package which allows us to put pagebreaks in (and generally gives more control of word doc outputs)

@aspina7
Copy link
Member Author

aspina7 commented Sep 18, 2019

on all plots - make y axis numbering go to top of axis, this happens because of expand(c(0,0)

@aspina7
Copy link
Member Author

aspina7 commented Sep 18, 2019

[see: https://github.com/reconhub/incidence/issues/105] on epicurves - possible to add a 2 weekly moving average? - issue posted on recon. Long term issue case.

@aspina7
Copy link
Member Author

aspina7 commented Sep 18, 2019

[Discussion] would be good to also output a document (beside the word) which summarises what datasets were used (and their file paths), starting cases, dropped cases where the output is. And maybe warnings/errors?

@zkamvar
Copy link
Member

zkamvar commented Sep 18, 2019

The one-big-issue-listing-a-whole-bunch-of-little-tasks is not really easy to reference when working on a specific task, so what I've done is made issues of each little task and am tracking them all in a github project, which makes it easier to track progress: https://github.com/R4EPI/sitrep/projects/1

I think we can keep this issue open as a discussion of these tasks.

@aspina7
Copy link
Member Author

aspina7 commented Sep 18, 2019

meeeennngg, y u no tell me about dis many moons ago?

@aspina7 aspina7 closed this as completed Jul 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants