Make some decisions about how to move v0.3 backend functionality to v0.4

[heyitsalexander]

Overview

The existing database structure for v3 needs a bit of housekeeping and reorganizing. Dev team will work together to make migration to v4 more efficient.

Action Items

• [ ] Create backend endpoint

• [ ] Discuss how Shaun likes to organize backend

[jbubar]

We decided not to put in the time to change anything about v0.3 backend and to just add it into v0.4 as it is right now

[jbubar]

This issue can be closed

[jbubar]

Ok.. @chukalicious and I were looking at the backends and we might change our mind.. Here are some of the things that we discovered...

1. The v0.4 backend already has models for users, projects, and meetings
2. if we chose to keep the users projects and meetings (looks more like the recurringEvents model) (from v0.4) we will need to add a few things

• user model needs: (requires an understanding of many to many relationship with mongoose) - volunteerOnProjects //projects that the person has volunteered on - managerOnProjects //projects that the person has project admin privileges
• projects model needs: (requires an understanding of many to many relationship with mongoose) - Volunteers //the project volunteers - Manager //the project managers - who can edit meeting times on that project
• we need to add some sort of worker to retrieve the meetings from the day
• We need to change our checkin model to work with our new worker that we will create

3. We do not have an endpoint for checkins in v0.4 yet!
4. We found an old schema that we do not understand from v0.4 that looks to be written for SQL (https://github.com/hackforla/VRMS/issues/437#issuecomment-748313069)
5. Might need to think about the old data and how we will be transferring it over

[jbubar]

https://github.com/hackforla/VRMS/issues/1183 - issue that I made to copy over v0.3 to v0.4... not sure if it is still relevent

[JackHaeg]

@jbubar @Spiteless if you all want to discuss this, if not, let's close this :)