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

update readme with clarifying socrata api documentation #181

Open
wants to merge 2 commits into
base: dev
Choose a base branch
from

Conversation

ryan-hall
Copy link

Adding a note describing differences in writing to Socrata datasets from RSocrata/SODA compared to the Data Management API. This is to help prevent confusion when automating data updates to Socrata that should make use of transforms applied on the platform during ingress.

@tomschenkjr
Copy link
Contributor

Ryan-

Thank you for raising this and for the explanation. It looks like this description is in the README.md file. Do you think it would be useful to also include in the R help files, e.g., ?write.socrata as well?

Not pertinent to this particular pull request, but relatedly, would it be valuable to shift write.socrata to support the Socrata Data Management API? It appears the "old" way is not compatible with SDM methods. But, do you know if SDM actions are backward compatible with those who originally created it through the old method? We may need to think how to arrange the various write methods.

Finally, thank you for signing the CLA. It appears there is some issues with passing unit tests. But, is unrelated to your contributions so we can solve that at another time.

@ryan-hall
Copy link
Author

excellent idea to include with ?write.socrata as well.

re: shifting to SDM, wholly agree on some thought needed for the various write methods. I plan on working on that this quarter and would appreciate any and all input.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants