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 VRMS stakeholder meeting, August 2024 #417 and PD: VRMS Stakeholder Meeting Agenda and Notes #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 Create Table: User #15
  • role Create Table: skills (formerly role) 😄  #38
  • user_status_type Create Table: user_status_type #35
  • practice_area Create Table: practice_area #63
  • user_availability
    • day_of_week Remove Table: day_of_week from ERD & sheet #60
  • user_check - replaces term of use consent
    • check_type Create Table: check_type 😄  #59
  • referrer
    • referrer_category
• project Create Table: project #16
  • leadership_type Create Table: leadership_type 😄  #42
  • technology Create Table: technology #39
    • project_technology_xref Create Table: project_technology_xref #40
  • project_url Create Table: project_url #41
  • location Create Table: location #44
  • program_area Create Table: program_area 😄  #43
    • project_program_area_xref Create Table: project_program_area_xref #45
    • project_program_area_status Create Table: project_status (used to say project_program_area_status) #46
• recurring-event Create Table: recurring_event #14
  • event_type Create Table: event_type #50
  • brigade Create Table: organization (formerly brigade) #56
  • frequency Remove Table: frequency from ERD and sheet #53
  • day_of_week Remove Table: day_of_week from ERD & sheet #60
  • event Create Table: Event #47
    • event_history Create Table: event_history #49 - for old events, rather than delete
• permission Create Table: user permission #22
  • permission_type Create Table: permission_type #24
  • role Create Table: skills (formerly role) 😄  #38
  • permission_history - for old permisisons, rather than delete Create Table: permission_history #37
• check_in Create Table: check_in #58
  • event Create Table: 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 |
|<back:lightgreen>   </back>| Implemented |
|<back:lightblue>   </back>| Predefined data |
|<back:Orange>   </back>| Required |

|= |= Type |
| Borderless | Phase 3? |
| Dotted border | Phase 2 |
endlegend
<style>

node {
    LineStyle 3.0;3.0
}
mindmapDiagram {
  .done {
    BackgroundColor lightgreen
    LineStyle 1;0
  }
  .req {
    BackgroundColor orange
    LineStyle 1;0
  }
  .predefined {
    BackgroundColor lightblue
    LineStyle 1;0
  }
}
rootNode {
    HorizontalAlignment center
    MaximumWidth 200
    LineStyle 10;0
}
</style>
* Tables for VRMS
** user <<done>>
*** role <<req>>
*** user_status_type <<predefined>>
***_ practice_area
***_ user_availability
****_ day_of_week
*** user_check - replaces term of use consent <<req>>
**** check_type <<predefined>>
***_ referrer
****_ referrer_category <<predefined>>
** project <<done>>
*** leadership_type <<predefined>>
*** technology <<req>>
**** project_technology_xref <<req>>
*** project_url <<req>>
*** location <<req>>
*** program_area <<predefined>>
**** project_program_area_xref
**** project_program_area_status
** recurring-event <<done>>
*** event_type <<predefined>>
*** brigade
*** frequency <<predefined>>
*** event <<req>>
****_ event_history - for old events, rather than delete
** permission <<req>>
*** permission_type <<predefined>>
*** role <<req>>
***_ permission_history - for old permisisons, rather than delete
** check_in <<req>>
*** event <<req>>

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