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

[super] Publishing data tutorials / patterns #91

Closed
4 of 7 tasks
rufuspollock opened this issue Dec 1, 2013 · 10 comments
Closed
4 of 7 tasks

[super] Publishing data tutorials / patterns #91

rufuspollock opened this issue Dec 1, 2013 · 10 comments

Comments

@rufuspollock
Copy link
Contributor

@rufuspollock
Copy link
Contributor Author

@tlevine if you have done any data packaging please feedback here re improvements in process and instructions (current tabular tutorial is up at http://data.okfn.org/publish and could no doubt be improved). geo tutorial is in progress ...

@rufuspollock
Copy link
Contributor Author

@peterdesmet this is the main issue on the publishing documentation side that i'm working through

@jalbertbowden any feedback you have based on your experience warmly welcomed here.

@rufuspollock
Copy link
Contributor Author

Terminology question: should it be "publish" or "package" data tutorials etc (publish to me in this context = package up then put online).

@tlevine
Copy link

tlevine commented Aug 18, 2014

I only just noticed this somehow. The main feedbacks are that

  1. I'd like a thing that writes the package for, akin to npm init.
  2. The data package specification should allow nested CSV files. I did it anyway, but I recall that this was improper.

@rufuspollock
Copy link
Contributor Author

@tlevine great feedback

@tlevine
Copy link

tlevine commented Aug 18, 2014

It was a while ago that I did this, so it's possible the tutorial was different then.

By "nested" CSV, I mean CSV with a column of type CSV.

@rufuspollock
Copy link
Contributor Author

@tlevine ah ok - so this is like the existing thing of columns of type json ...

Please keep the feedback coming - really useful!

@jalbertbowden
Copy link

i'm going to catch up on all of this...but off the top of my head, now that dat is in alpha, i think we should all start dabbling with it and provide feedback

@rufuspollock
Copy link
Contributor Author

rufuspollock commented May 6, 2016

Is this now a DUPLICATE of #182?

@danfowler
Copy link
Contributor

This issue was moved to #51

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

No branches or pull requests

5 participants