Rufus NTS
Rufus NTS
#done/process consolidated into Planning Stream etc
Outflow
- What is current SCQH? π Old Feb 2021 brainstorm that is unfinished
- What is our current consolidated plan of work?
- State of existing datahub.io
- Existing user database
- Discord server and users there
- ASIDE: switching to element from discord (v low priority => leave for now)
Current thought tree
- What is Datopian Product Roadmap and Plan (Dec 2021) (choice of DataHub Pages) - https://coggle.it/diagram/YcBHOVSjioht7ZJX/t/datopian-product-planning-dec-2021-choice-of-datahub-pages
- Do we want to develop products? π Yes. See Business Strategy and Product Strategy (Dec 2021)
- SCQH - Dec 2020
- Issue Tree - coggle unfinished and unprocessed but sort of obsoleted by answer in strategy doc
- What products do we want to develop? π DataHub Pages (+ CKAN SaaS)
- What is vision and plan for DataHub Pages? π DataHub Product Vision and Plan
- Do we want to develop products? π Yes. See Business Strategy and Product Strategy (Dec 2021)
Where does this issue tree fit in https://docs.google.com/spreadsheets/d/1sprrkUeMRa3nrma4HvY_k-T0zGYttXJikqe9XPPmSiA/edit#gid=755438186 (think we deprecate it β¦)
Documents to process
- DataHub Next vs Vercel - Feb 2021 by Anu - 2.5 pages with a few ideas (nothing super crucial)
- CKAN Next Gen ποΈ - diagram with a few screenshots of what a next gen showcase page could look like with a layout sketch. π¬ suggest this goes into a page with ideas for showcase page
- https://coggle.it/diagram/XwM2fshG0AglV4rq/t/datahub-job-stories-focused-on-the-power-users (Feb 2021) - list of job stories in coggle form
Team Meeting - Anu, Leo, Rufus
Present: Leo, Rufus, Anu
Leo Email
I've been going through portal js, datahub and the product documents we have.
Basically I've been trying to see how to make this sentence I said last year real "Make sharing new datasets stupidly easy" after a few trials and trying to see how things work the current state of the things we have is really far from it. This is something we have already discussed some time ago.
My first goal is to do the following:
- Have a CSV of the data we want to publish and [optional] have a markdown file with the text description then:
- run a single command/script, it creates a static webpage
- be able to git push into github pages and it just works
To get to publish a dataset with what we currently have we need to:
-
study and understand what Frictionless data is and how to create it (the end user shouldn't, they should be able to start without knowing anything about it)
-
understand what portal.js is, how to install it and that there are different ways of publishing with it, including a single dataset option
-
understand that portal.js is built on next.js which makes us lose focus, and then this runs over react.js which has its own complexity by itself.
-
Understand how to deploy a react application in github pages
Just installing the npm dependencies with a fiber connection takes about 1 minute which, from a user point of view can already be a problem, but the most frustrating thing is all the knowledge and work needed to just be able to set up things to start to build my data page.
This is quite a challenge for somebody that just wants to publish some data, with some text and maybe some graphics.
So my goal for the next days is to understand how to make this much simpler and from there build the scripts (this might or might not use all of portal.js in the first version).
Some notes:
- the user does NOT need to know frictionless, nextjs, react, portaljs
- the user should be able to run a simple script (the first one should be text based) that allows for a creation of a simple static webpage that can be pushed to github pages (maybe even create a script that does it for them)
- the user should be able to install the tool with a simple shell script and/or pip (python). Note that I choose python because it is one of the most used languages in the data and scientific domains, which means that most people would be able to run a python script.
For this some individual goals are:
- automatic generation of the frictionless json file
- templated UI (as for datahub)
- static website generation
- some default graphs that can be chosen (possible generated by Vega Lite)
The power users then should then be able to take advantage of all the setup (frictionless, portal.js and so on) to make more complex and personalized modifications.