###### tags: `gitcoin` `fdd` `dsl` # Data Storage Layer for GitCoin Fraud Detection and Defence ## Getting from Current State to Short Term Goal * Formalize Data Portals * Portal for internal data users (Data Scientists) * Portal for incoming data (Data Sources) * Portal for outgoing data (Data Sinks) * Inventory data sources * Inventory data transformations * Inventory data sinks * Create data dictionaries * Identify sensitive data elements * Data with external sensitivity, e.g. PII * Data with internal sensitivity, e.g. sybil criteria * Create organizational structure around ownership of and access to sensitive data elements * Create rules for accessing sensitive data ## States ![current-fdd-dsl](https://lucid.app/publicSegments/view/caa9e2d4-0855-459d-beba-63aa767bd228/image.png "Current FDD DSL") Figure 1: Current state of FDD DSL ![goal-short-term-fdd-dsl](https://lucid.app/publicSegments/view/59fe843b-19ca-4557-8a8d-f032812ae657/image.png "FDD DSL:Short Term Goal") Figure 2: State of FDD DSL at short term goal. Green background indicates ownership by FDD organization. Green data portal is the interface between FDD data engineers and FDD data scientists ![generic-data-lake](https://lucid.app/publicSegments/view/92a2aa72-6c5c-4b93-a305-562a3d4471f6/image.png "Generic Data Lake") Figure 3: Generic, conceptual, block diagram of a data lake. This needs to be morphed into "FDD DSL: Long Term Goal" by determining what is needed and what is fluff in this context.