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 guides to Frictionless Data specifications v1 #332

Closed
20 tasks
danfowler opened this issue Dec 2, 2016 · 10 comments
Closed
20 tasks

Update guides to Frictionless Data specifications v1 #332

danfowler opened this issue Dec 2, 2016 · 10 comments
Assignees
Milestone

Comments

@danfowler
Copy link
Contributor

danfowler commented Dec 2, 2016

This is an issue for updating the current user guides.

We need at least two (related) types of guides for Data Packages: one set oriented toward users (developers, publishers, and consumers of data) and one set for implementors (developers seeking to create new implementations).

User Guides

This is a set of guides for publishers and consumers of data using the tools that exist. They should collectively answer the question "how do I X with a Data Package?". As there are many tools (some with overlapping functionality), it is important that this set of guides is oriented from a "use case" standpoint rather than a tool-specific one. We should also show how these tools fit together, because it is not always obvious.

Problems

  • They are out of date w/r/t tools
  • They are out of date w/r/t specs
  • They are not super well organized
  • It is not obvious how to contribute (more implementations will come and need user-friendly guidance)

Requirements

  • It must be clear that these are "user" and not "implementor" guides with clear guidance on where to go to find information on implementions
  • The guides must reflect the current state of Data Package tooling and be easy to update
  • They should list the date published and the version of Data Packages they target so that readers can be reasonable confident that they are reading up-to-date information
  • The URL structure must be flexible enough to allow for multiple use cases/languages
  • It should be easy to contribute new guides for new languages (e.g. related to tool-fund)
  • The user guide must pull from a stable and illustrative set of updated Data Packages for examples: (e.g. https://github.com/frictionlessdata/example-data-packages or
  • Contributor of guide should be listed

Tasks

  • Decide on home: these could continue to be listed under /guides/ or moved to a github repo alongside the implementations github repo
  • List use cases to target (e.g. reading metadata from a Data Package, downloading a Data Package to disk, importing a Data Package into an SQL interface, exporting a Data Package from an SQL interface, creating a Data Package, validating a Data Package for adherence to spec, validating the data within a Data Package. updating a Data Package, joining fields in two Data Packages, etc.)
  • For each use case with a clear guide that can be written to address it, create a /guides/{use-case}/{interface} where {use-case} can be something like validating-data or sql and {interface} can be something like python, javascript, cli, or webapp.
  • Translate the existing guides to Jupyter notebooks following the above format
  • Create guidance to update or add to guides for other languages/interfaces
  • Other Cleanup
#examples
/guides/working-with-sql/python/
/guides/working-with-sql/ruby/
/guides/validating-data/python
/guides/validating-data/goodtables-io
/guides/creating/javascript

Implementors Guide

@danfowler danfowler self-assigned this Dec 2, 2016
@roll roll added the specs-wg label Dec 9, 2016
@danfowler danfowler changed the title Communicate recent changes to specs on way to v1 Communicate changes to specs V1 Dec 12, 2016
@danfowler
Copy link
Contributor Author

Renamed to reflect that we will do all this communication after the V1 release.

@roll roll added the priority label Dec 15, 2016
@pwalsh pwalsh changed the title Communicate changes to specs V1 Announce Frictionless Data specifications v1 Jan 15, 2017
@pwalsh pwalsh self-assigned this Jan 15, 2017
@pwalsh pwalsh changed the title Announce Frictionless Data specifications v1 Update guides to Frictionless Data specifications v1 Jan 15, 2017
@pwalsh pwalsh modified the milestone: Current Jan 15, 2017
@pwalsh pwalsh assigned danfowler and unassigned danfowler and pwalsh Mar 9, 2017
@pwalsh
Copy link
Member

pwalsh commented Mar 16, 2017

@danfowler now based on #341 being ready for you, and based on @roll starting next Monday on js and py updates for v1, I think you could start a branch that does this - updating our guides for v1. This will, along with the work that @roll will start next week, help us all pick out more issues in the specs and get them tip top.

@Stephen-Gates
Copy link
Contributor

I made a start at https://discuss.okfn.org/t/tutorial-for-handcrafting-a-table-schema/5577
Happy to review, test or author some guides. Let me know the framework for contributions and I'll fit in. In the meantime, I'll write some stuff in Google Docs.

@danfowler
Copy link
Contributor Author

@Stephen-Gates
Copy link
Contributor

I'm also scribbling notes about Tabular location data. Contributions welcome - very draft at present.

@pwalsh
Copy link
Member

pwalsh commented Jun 15, 2017

@pwalsh
Copy link
Member

pwalsh commented Jun 15, 2017

@danfowler specifically, to this issue that already exists #114

@roll
Copy link
Member

roll commented Nov 15, 2017

@serahrono
@vitorbaptista
If we're back for an active usage of this issue track I think we need to update/close this issue. Probably many of these steps are already done. And those that not done but actual we could extract as things to do.

@serahkiburu
Copy link
Contributor

This issue was moved to frictionlessdata/website#152

@serahkiburu
Copy link
Contributor

#360

@roll roll moved this to Done in Open Knowledge Dec 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

5 participants