Data Overview, Schema, and Dictionary Development

[eekevall]

Challenge Brief:

There is a need to create a comprehensive data overview, schema, and dictionary for the Greenstand project. This will streamline the data management process, ensure consistency across the project, and improve the overall quality of the data; ultimately leading to better outcomes for the project.

The goal of this ticket is to establish a clear understanding of the data Greenstand generates, its structure, relationships, and formats, as well as to prepare the data for use in various projects, including the Northeastern University partnership.

The scope of this task includes the following:

• Developing a data overview that summarizes the key characteristics of our data, including the number of records, fields, data types, and any relevant metadata.
• Creating a schema that defines the structure of our data, including the relationships between tables, fields, and data types.
• Building a dictionary that defines the meaning and format of each field in our data, along with any validation rules or constraints.
• Preparing the data for use in various projects by cleaning, transforming, and formatting it according to project requirements.

Deliverables:

• A comprehensive data overview document that summarizes the key characteristics of our data.
• A schema diagram that illustrates the structure of our data and relationships between tables, fields, and data types.
• A dictionary that defines the meaning and format of each field in our data, along with any validation rules or constraints.
• Data preparation scripts or tools that can be used to clean, transform, and format the data for use in various projects.

[Davidezrajay]

@eekevall Thanks for leading the way here.. Please reach out if I can support you any way.
Here is the data we are ultimately headed towards. https://github.com/Greenstand/Greenstand-Overview/blob/master/Greenstand-Token.md#data-requirements

https://github.com/Greenstand/greenstand-documentation/blob/e08ee6f3dca76befc8c66a8170b6800d27501d3c/docs/introduction/domain-model.md#domain-model