Create a crowd source data exchange

[bodhish]

It clear that whatever disaster happens people would join together and crowdsource data. Most of these efforts are majorly created using google and airtable sheets.

The key challenges here are data duplication and validation. On every issue, multiple teams try to maintain a copy of the same data with different statutes. It always makes sense to have a single backend that could integrate all of this together at the same time giving the maintainers freedom to choose their own workflow.

An ideal system should be like a crowdsourced information exchange where multiple parties could plugin custom integrations. Example: Live sync from google sheets, Tweet when valid data is created.

Good to Have Features

• The system should be extensible with no-code tools
• Should allow all parties involved to have their own workflows with a unified data schema
• API driven. The system can choose not to have a public interface (Give out API's so that end users can create white-labeled FE's)
• Should have options to flag records, request for deletion, and upvote for every resource
• There should be a scoring mechanism with which the people could validate trusted sources.
• System should flag duplicates / have an intelligent mechanism to merge duplicates together.
• Should have webhooks that could update data from pre-registered sources

WIP DOC

[MadHatter92]

LIFE should target to become the standard keepers on this. Let's create the schema for each of the categories, with what information to input where, circulate as google sheets. Let our airtable work as the interchange. Flow can look like: Google Form > Google Sheet -> Zapier -> Airtable -> Front end Suggesting google sheets as it will be easiest to broadcast to the largest group Was thinking of some other database but think that wont be needed, there are barely 1000 decent hospitals in india

[PallabiRoy27]

Is there a chance that folks dealing with the black market will abuse the scoring mechanism? I feel like we should have a protective layer to prevent monopolisation.

[MadHatter92]

Is there a chance that folks dealing with the black market will abuse the scoring mechanism? I feel like we should have a protective layer to prevent monopolisation. captcha + IP check maybe

[MadHatter92]

Summarising call notes:

1) Create standard schema 2) Get one POC from each group 3) Get each group to adapt their data to our schema 4) Every group gets its own sheet for each category on airtable, data submitted via forms gets its own sheet 5) This feeds into a master sheet 6) Build upvote / downvote functionality

The above to be tested for Oxygen.