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

Maybe opportunities to join efforts ? #17

Open
Edouard-Legoupil opened this issue Jun 18, 2019 · 3 comments
Open

Maybe opportunities to join efforts ? #17

Edouard-Legoupil opened this issue Jun 18, 2019 · 3 comments
Assignees
Labels
question Further information is requested

Comments

@Edouard-Legoupil
Copy link

Hi - Just discovering your package today - excellent - have you already seen https://unhcr.github.io/koboloadeR/docs/ ?

It seems that there are definitely ideas in common between the 2 packages...

Best,
Edouard

@Edouard-Legoupil
Copy link
Author

We have a group on skype for humanitarian data analyst: https://join.skype.com/qYBKC5q3wKp4
https://humanitarian-user-group.github.io/post/first-meeting/

@ernestguevarra
Copy link
Member

Sorry but am not available for Skype at the moment. I have a couple of projects that I am busy with. I've looked into your koboloader package. I am curious to see an actual output that uses the package.

As for the odkr package, it used to be on CRAN but had to be archived due to Java-related issues. I am aiming to re-release after addressing the issues.

My main goal for odkr is mainly as an interface to any ODK-type servers and pull out and/or push in data. From what I see this is the only similarity. Your package does more than this I think and this is admirable.

From my point of view, I think that the koboloadeR package is putting into one place too many functions that in my opinion can be broken apart to smaller but very focused packages that does specific aspects of what koboloadeR is doing. And then all these packages can then be integrated centrally through a Shiny app that draws on these packages. There are multiple reasons why I prefer this approach one of which is future-proofing of the whole system (not just the package itself).

I am keen to hear what your thoughts are and what your aim was for raising an issue/getting in touch.

Thanks.

@ernestguevarra ernestguevarra self-assigned this Jun 20, 2019
@ernestguevarra ernestguevarra added the question Further information is requested label Jun 20, 2019
@Edouard-Legoupil
Copy link
Author

Edouard-Legoupil commented Jun 23, 2019

Dear Ernest -

Thanks for your suggestions - we are now working on better documentation and are looking at getting the package on CRAN. Will asap add on the repo some output from the package so that you can quickly see what we get.

Actually the vision for the package is exactly the one you describe - i.e. an integration of a series of existing package to facilitates the analysis workflow. The existing functions in the packages are designed to support. We have already a shinyapp that helps users to navigate through those functions.

In this regard, I was looking at integrating your package for data retrieving on the server - especially when the form includes repeat elements.

If you see some precise functions within the package that could be pulled out in separate packages (I can only agree with your points on small more manageable packages), we would definitely consider your suggestions. Any other suggestions you would have would also be highly appreciated.

I hope you will be able to find to discuss at some points. Congrats again for the good work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants