Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tables to add for VRMS #25

Open
39 tasks
fyliu opened this issue Aug 25, 2022 · 2 comments
Open
39 tasks

Tables to add for VRMS #25

fyliu opened this issue Aug 25, 2022 · 2 comments
Labels
complexity: small All steps are laid out in detail so that someone new to the project can work on it dependency Issue has dependencies p-feature: API private endpoint role: product s: VRMS stakeholder: VRMS size: 1pt Can be done in 4-6 hours

Comments

@fyliu
Copy link
Member

fyliu commented Aug 25, 2022

Dependency

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

Visual list

Mindmap

click to expand

mindmap

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

@jbubar
Copy link
Member

jbubar commented Aug 29, 2022

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

@ExperimentsInHonesty
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity: small All steps are laid out in detail so that someone new to the project can work on it dependency Issue has dependencies p-feature: API private endpoint role: product s: VRMS stakeholder: VRMS size: 1pt Can be done in 4-6 hours
Projects
Status: 🧊Ice Box
Development

No branches or pull requests

5 participants