Tables to add for VRMS

[fyliu]

Dependency

• [ ] We are waiting for VRMS to give us a list based on their current features. Had meeting with them on 2024-08-15, check back in with them on 2024-08-29. See #417 and #377 for updates.

Overview

As contributors helping build to out the backend, we need a list of tables from which to create new issue for and then to add those tables to the project. In this issue, we decide on the list of tables that VRMS needs to have to function.

Update

Since we're now using the spreadsheet directly to create all the issues, we don't need to use this for that purpose. We can still use this to prioritize what tables we should work on.

Action Items

• [ ] Reference VRMS v3 models and pick out relevant ERD models to implement
• [ ] Reference VRMS v4 models and pick out relevant ERD models to implement
• [ ] Pick out what's required immediately for functionality and what can wait for a later Phase 2 (strikeout tables that are not immediate needs
• [ ] Create issues and link to the items (do not click items to create issues, create the issues using the Create Table form and then add the issue # after the item text)
  • [ ] Add the issue links to the spreadsheet under the "Has Issue" column
• [ ] Implement the tables and check off the boxes

Tables we need

italicized items are tables with initial data

• [ ] user #15
  • [ ] role #38
  • [ ] _user_statustype #35
  • [ ] practice_area #63
  • [ ] user_availability
  • [ ] day_of_week #60
  • [ ] user_check - replaces term of use consent
  • [ ] _checktype #59
  • [ ] referrer
  • [ ] referrer_category
• [ ] project #16
  • [ ] _leadershiptype #42
  • [ ] technology #39
  • [ ] project_technology_xref #40
  • [ ] project_url #41
  • [ ] location #44
  • [ ] _programarea #43
  • [ ] project_program_area_xref #45
  • [ ] project_program_area_status #46
• [ ] recurring-event #14
  • [ ] _eventtype #50
  • [ ] brigade #56
  • [ ] frequency #53
  • [ ] _day_ofweek #60
  • [ ] event #47
  • [ ] event_history #49 - for old events, rather than delete
• [ ] permission #22
  • [ ] _permissiontype #24
  • [ ] role #38
  • [ ] permission_history - for old permisisons, rather than delete #37
• [ ] check_in #58
  • [ ] event #47

Visual list

Mindmap

click to expand


Source to generate mindmap on live server

click to expand

``` @startmindmap title Tables for VRMS header Referencing Tables for VRMS from https://github.com/hackforla/VRMS/tree/development/backend/models and https://github.com/hackforla/VRMS/tree/development/backend-mvp-04/models endheader legend left |= |= Type | | | Implemented | | | Predefined data | | | Required | |= |= Type | | Borderless | Phase 3? | | Dotted border | Phase 2 | endlegend * Tables for VRMS ** user <> *** role <> *** user_status_type <> ***_ practice_area ***_ user_availability ****_ day_of_week *** user_check - replaces term of use consent <> **** check_type <> ***_ referrer ****_ referrer_category <> ** project <> *** leadership_type <> *** technology <> **** project_technology_xref <> *** project_url <> *** location <> *** program_area <> **** project_program_area_xref **** project_program_area_status ** recurring-event <> *** event_type <> *** brigade *** frequency <> *** event <> ****_ event_history - for old events, rather than delete ** permission <> *** permission_type <> *** role <> ***_ permission_history - for old permisisons, rather than delete ** check_in <> *** event <> ```

Resources/Instructions

• VRMS v4 data models
• VRMS v3 data models
• PeopleDepot ERD
• Guide to create new table issues
• "Create Table" Issue Form

[jbubar]

@fyliu this is awesome.. can you also include the join tables? just out of curiosity on my end

[ExperimentsInHonesty]

review this with the VRMS team to see if there are any other tables that they need. See also the spreadsheet with all tables