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

creating a database schema for CivicTechJobs #417

Closed
4 tasks
blulady opened this issue Jul 12, 2023 · 2 comments
Closed
4 tasks

creating a database schema for CivicTechJobs #417

blulady opened this issue Jul 12, 2023 · 2 comments
Labels
feature: Architecture Pertains to project architecture and settings feature: Documentation Pertains to documentation of any kind PBV: dev all issues for engineering roles (devops, backend, frontend, db) role: backend Pertains to backend tasks size: 5pt Can be done in 19-30 hours

Comments

@blulady
Copy link
Member

blulady commented Jul 12, 2023

Overview

Before building a database we should probably have a schema.

Action Items

  • create a database schema
  • create an ERD in lucid chart (used in People Depot team)
  • submit the database schema before the dev team
  • confirm with the rest of the team that we correctly understand the work flow and needs of the team

Resources/Instructions

https://www.databasestar.com/how-to-design-a-database/
https://www.databasestar.com/database-timezones/
https://www.lucidchart.com/blog/database-design-best-practices
https://www.conceptatech.com/blog/best-practices-how-to-design-a-database
People Depot ERD

From the dev team discussion 23-07-11:
Job Postings:
Job Posting name/id
many to one relationship with project
many to one relationship with users profile

UsersProfile/Project Managers:
name
many to one relationship with project
one to many relationship with job postings

Projects:
project name/id
one to many relationship with users profile?
one to many relationwhip with roles

@blulady blulady added role: backend Pertains to backend tasks feature: Documentation Pertains to documentation of any kind feature: Architecture Pertains to project architecture and settings labels Jul 12, 2023
@blulady blulady self-assigned this Jul 12, 2023
@kcoronel
Copy link
Member

@MattPereira @bzzz-coding since Sarah has off-boarded from the project I removed her from this issue and moved this back into the Icebox. Something I would add to the top of the issue to make it more specific would be whether this schema is for the CMS or for CTJ. Additionally, if for CMS (my assumption), we discussed not having a 1 to 1 relationship between project managers and CMS but instead having project emails/profiles have a 1 to 1 relationship with the CMS.

@ghost ghost added size: 5pt Can be done in 19-30 hours and removed size: missing labels Sep 19, 2023
@ExperimentsInHonesty ExperimentsInHonesty added the PBV: dev all issues for engineering roles (devops, backend, frontend, db) label Jun 12, 2024
@nooriaali9 nooriaali9 mentioned this issue Aug 22, 2024
4 tasks
@nooriaali9
Copy link
Member

Closing this issue - since it is outdated/ not a priority anymore - based off of #552

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature: Architecture Pertains to project architecture and settings feature: Documentation Pertains to documentation of any kind PBV: dev all issues for engineering roles (devops, backend, frontend, db) role: backend Pertains to backend tasks size: 5pt Can be done in 19-30 hours
Projects
Archived in project
Development

No branches or pull requests

5 participants