blockternship/dpanc

Self Health Management dApp for Diabetes

dpanc's Issues

[Display] Switching Pages Changes Query

When switching from dashboard to another page (i.e. Contact Us) followed by going back to the dashboard leads to the data "disappearing", but only takes a click on another filter (3 mo or 6 mo) to bring the data back.

Design contract for big data store

[Design] Provide global statistics

It would be extremely useful for users to see how their numbers are compared to other people.

This story is to design how we will store user's data in a global store of some kind.

Create csv parser

We need a service to parse incoming csv files and prepare them to be stored into IPFS

Implement User dashboard (report) view

depends on #15

The User dashboard view will default to past month. The User can select the time frame to show statistics over, such as 3 month, 6 month, etc.

Setup Truffle

We need to setup Truffle so that we can test & deploy our contracts.

This task is to setup a basic Hello World contract and setup a basic test for it (including ganache setup).

Upload user data to IPFS

When a user uploads their data on our basic user upload form, the data should be saved to IPFS.

The IPFS hash should eventually be saved to our dPanc contract, but the scope of this story is just to upload to IPFS and log the hash returned.

Setup web app to use React frontend, with Express.js proxy backend

Web app should leverage a React frontend, and use an Express.js proxy backend server to make API calls.

Should have a basic home page that makes an Express.js API call to render "Hello World" text.

Design data model for big data store

Spike OrbitDB

https://github.com/orbitdb/orbit-db

The current IPFS implementation that saves hashes on the Ethereum network does not scale well as time passes. 1 transaction is required per month of data stored.

We should look into OrbitDB as they offer a database implementation on top of IPFS. This allows us to create a database (data store) for each user, and save the hash that points to the OrbitDB database for that user. This means we only need to use 1 transaction to save the database hash, and subsequent updates to the user's data do not require any transactions.

Integrate web3 via MetaMask

Integrate web3 into our web app by leveraging the browser's MetaMask (if exists).

The scope of this task is to be able to detect MetaMask and to extract the user's first account address to display on the upload form as a pre-filled box.

Create basic user upload form

Create a basic upload form on home page using Google Material-UI framework (without metamask integration).

Should be static and buttons should not have any functionality.

Implement dPanc contract to store a user's OrbitDB database address

Implement the dPanc contract designed in #8 and #14

Store OrbitDB address in dPanc contract

Once a user submits their data for the first time, we should create an OrbitDB database for them and upload the OrbitDB address to our dPanc contract.

We will name the user's OrbitDB database as the keccak256 hash of their Ethereum address (using web3 utils).

Another per-requisite is #27 as the dPanc contract needs to be done and deployed.

Find simple and easy graphing library for basic UI

[Feature] Allow user to view last X months of data

Upon uploading a month of data, users are directed to the dashboard page which show stats for that month.

The user should be able to select how far back to look and generate statistics for.

The basic implementation can consist of having a couple additional buttons at the top of the dashboard (Last 3 Months, Last 6 Months, etc). When a user clicks on the button, then we will fetch the data pertaining to the time period and run calculations to render on the dashboard page.

Upload mock parsed data for building initial analysis services

In order to start working on analysis services independently of the csv upload and parsing process, we should provide a mock json file to provide a sandbox for these services.

Use separate views/pages

The Form view should be separate from the Dashboard view.

We will also want to have a sidebar or top navbar.

Setup Babel 7

https://babeljs.io/docs/en/next/v7-migration.html

Design data model for user data store

Design User dashboard (report) view

Should have a mock up of where each graph/data goes in the view.

Also should list out what data we will be calculating and showing to the user.

Design contract that stores user IPFS hashes

Build initial data analysis tools

This is so we can start to think about the user design and experience

Max velocity service does not handle negative velocities