manu-p-1 / meet

💳 Marqeta Hackathon Project - MEET - A structured and plan-based expense management platform for the modern age powered by Marqeta's modern card issuing API

Hey there, I'm Manu. 👋 Glad you found this page!

• I’m currently working on ... Really awesome projects! I enjoy collaborating with others to brainstorm creative ideas and solutions while seizing opportunities that help me do so
• I’m currently learning ... software engineering, data analysis, and management skills from experienced industry professionals
• Favorite Quote ... "Courage is resistance to fear, mastery of fear — not absence of fear." ~ Mark Twain
• Fun fact ... I'm a aviation geek ✈️ and credit card nerd 💳, so ask me about credit cards, commercial aviation, flight simulation, geography, and travelling!

meet's Issues

Database Modification for Department Token?

From the meeting (5/14/2021), there was a discussion about modifying department table to include the department token as its primary key. Also, we talked about the user and the account holder group tables to have the department token as a foreign key. Where did that end up?

Questions About Individual Users' Virtual Cards

Few questions about individual users' virtual cards:

1. Can individual users have multiple virtual cards? If so, can they possess multiple cards at one time?

2. Does each virtual card have their own identification number (16 digit number)?

"Internal Endpoint" for Manu, List of Users Given Department Token

Given a department token (GET request) provide a list of users in JSON.

Further Info and Consideration for Data

The first picture is just a display of all the possible components we can display.

The images below are possible graphical designs we can implement to display data.

Possible Pie Charts

1. For Departments

2. For Plans

Line Graph

The image below is just a sample display of a weekly time line. Daily, monthly, yearly, or aggregate timeline will be similar.

Velocity Controls

Answer these questions:

1. What are velocity controls?
2. Who do they apply to?
3. Provide code/pseudo-code examples.

My First Issue

Testing: Issue Board

Incorporate Budget Validator into Form

Validator created by @ssyuen, but we still need to make sure that 80% of the budget is reasonable, and what happens when you reach a number that's too small to borrow from. After this we can incorporate to actual form field.

Tooltips!

Use built-in dashboard features for building tooltips for each widget

Simulate User Spending on Dashboard

Write backend function, write frontend graph and test it out.

Truncate amounts to two decimal places

I keep getting a Data truncated for column warning. Either that, or i'll increase the precision in the db

Refactor project name

Title

Complete & Review README and code documentation

Look at new sections on branch

Considerations for Display of Statistical Data

Here are a few considerations for the data to display and the type of format

From a "CEO" perspective: view of all departments

1. General data

Department	Supervisor (?)	Number of Employees	Current Number of Plans	Expired Plans	Total Number of Plans	Initial GPA Balance	Additional Fund Added to GPA	Total Fund Distributed	Current GPA Balance

2. Statistical Data: These can be added on to the table above/ or acts as its own table). I just added these on this part (not sure how long you all want the length of the table to be).

*Note: Do you all want to add a filter option for the dates for the user? (ex. selecting all the dates from January )

Department	Supervisor (?)	Number of Employees	Total Number of Plans	Average Weekly Distribution	Average Monthly Distribution (Can be divided into 4 quarters if desire)	Average Yearly Distribution	Current GPA Balance

3. General Data of individual employees

Description: A simple display of all individual employees.

Employee ID	Last Name	First Name	Department	Plan (?)	Initial  Account Balance	Additional Fund Added	Total Amount Spent	Current Account Balance

From a "Department Supervisor" perspective: view of all employees

1. General data of Individual Employees

*Note: Same table as table 3 from "CEO" Perspective.

2. General Data of Individual Employee

Employee ID Last Name, First Name
Department

Last 4 Digits of Virtual Card (If there is one)
Opening Balance:
Closing Balance:

Plan	Date	Item/Transaction	Current Account Balance

3. Statistical Data of Employees

Employee ID	Last Name	First Name	Department	Average Weekly Spending	Average Monthly Spending	Average Yearly Spending	Current Account Balance

This is all considerations for now. In a way, these are the most basic and probably most used data.

NOTE: Besides providing a table, we can also allow the user to manually generate a table with their own desired data (A filter or sorting system)

Stagger Biz to Dept amount and Dept to employee amounts during simulations

Descriptions

We want to stagger the amounts (randomize which departments get how much money) and do the same thing when employees receive funds from the department.

Proposition

Divide the main accounts GPA available balance by 0.2. This allows us to deposit up to 80% of the funds. From there, for each department or each user, select a random value to distribute. This is slightly more complicated than it seems and you'll end up running into some intracacies

Catch Error on Insert

Catch Model Insertion/Update update errors to return useful information back

Convert Create/Manage Plan dates to 12 hour time from 24 hour

From UI, capture 12 hour time and convert 12 hour time into naive localized 24 hour UTC.

Department Utilization - cursor.fetchall error

Description

Find out the reason why we are receiving an intermittent tuple out of range error for department utilization. This may be part of a greater problem of the underlying math

Use Case: Simulate Distribution of Funds to Departments (Preplan)

With the created plan form fields, consider the logic in these use cases:

1. Start/End Dates

Start Date	End Date	Description
0	0	Plan begins immediately and lasts for an indefinite amount of time
0	1	Plan begins immediately and ends at the specified end date
1	0	Plan begins at the specified beginning date and lasts for an indefinite amount of time
1	1	Plan begins at the specified beginning date and ends at the specified end date

2. Amount to move is greater than amount in source account

Consider sending error to standard error page.

3. Velocity Controls - William's issue

Use Case: Simulate Distribution of Funds to Individuals (Preplan)

With the created plan form fields, consider the logic in these use cases:

1. Start/End Dates

Start Date	End Date	Description
0	0	Plan begins immediately and lasts for an indefinite amount of time
0	1	Plan begins immediately and ends at the specified end date
1	0	Plan begins at the specified beginning date and lasts for an indefinite amount of time
1	1	Plan begins at the specified beginning date and ends at the specified end date

2. Amount to move is greater than amount in source account

Consider sending error to standard error page.

3. Velocity Controls - William's issue

4. Create card for user use case (in another issue)