Flat Data Editor for crowd-sourcing data through user-friendly PR interface #64
Replies: 2 comments 2 replies
-
This is a wonderful suggestion, thanks for writing it out! We unfortunately don't know of anything existing that would support this workflow, but spent some time adding "edit" functionality to the Flat ui React component: https://github.com/githubocto/flat-ui/releases/tag/v0.11.0 We'd love to hear if anyone has other suggestions here, or wants to build an interface that creates a PR using the flat-ui component! |
Beta Was this translation helpful? Give feedback.
-
I have discovered https://github.com/dolthub/dolt and DoltHub which also look like very promising technologies in this space, and perhaps could be used as alternative techniques for the "git sourcing" approach I propose above. |
Beta Was this translation helpful? Give feedback.
-
I've only just discovered this great project, so forgive me if this question is somewhat uninformed ...
It seems that the Flat Data paradigm is currently based on Simon Willison's git-scraping model, with the assumption that the authoritative source of data is external to git, and will be fetched / updated via an HTTP or SQL request. And of course this is a great model for many use cases. But I have use cases in mind (involving public data) which would require a slightly different approach to maintaining the data:
One example use case is crowd-sourcing data about public transport networks which is not already openly accessible. The data set could be bootstrapped by project founders, and then opened up for the world to contribute to, a bit like OpenStreetMap but of course with a drastically reduced and simplified data set.
This alternative approach to data sourcing within git repos could be called "git sourcing", serving as a complementary technique to "git scraping". Indeed I could imagine scenarios where they could be combined; for example git scraping continually fetches / updates datasets from public APIs, and then git sourcing allows the general public to apply manual corrections / modifications on top of those via git rebase or merge. (The question of how to resolve merge conflicts in this scenario is left as an exercise for the reader 😉 )
So my questions are:
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions