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

Create Table: practice_area #63

Closed
14 of 17 tasks
ericvennemeyer opened this issue Sep 9, 2022 · 2 comments
Closed
14 of 17 tasks

Create Table: practice_area #63

ericvennemeyer opened this issue Sep 9, 2022 · 2 comments
Assignees
Labels
complexity: missing feature: table creation p-feature: practice area ui/ux, engineering, devops, data science, marketing, etc. PII: FALSE Table or function does not have or use Personally Identifiable Information (PII) role: db architect s: CTJ stakeholder: Civic Tech Jobs s: hackforla.org stakeholder: hackforla.org website s: kb stakeholder: knowledgebase s: VRMS stakeholder: VRMS size: 2pt Can be done in 7-12 hours

Comments

@ericvennemeyer
Copy link
Member

ericvennemeyer commented Sep 9, 2022

Overview

We need to create the practice_area table so that we can update a shared data store across hackforla.org, vrms, civictechjobs, and tables (onboarding) project.

Details

A table and a model are the same thing

Action Items

  • identify and document table description (see spreadsheet under Resources)
    • if not, reach out to PD leads
  • compare and check off the data fields (below) against the ERD. Note any fields in the ERD that's missing from the list. (see Resources)
  • compare the check off associated tables (below) against the ERD. Note any associated tables in the ERD that's missing from the list (see Resources)
  • create a single model in Django (defining schema)
  • write a test for the relationships this model will have with other models (e.g., creating a user and assigning them a set of permissions on a project).
  • write an API end point
  • write API unit tests
  • document the endpoint

Resources/Instructions

Description

Dictionary of practice areas

Data Fields

  1. Copied from spreadsheet and checked off according to ERD. (unchecked items indicate a mismatch between ERD and spreadsheet, which requires a review)

    • (PK) id - int - Record Id
    • name - varchar
    • description - varchar
  2. In ERD only (having items here indicates a mismatch, which requires a review)

    • icon - URLField - (see CTJ for examples)
    • (FK) status_id - int

Associated Tables

  1. Copied from spreadsheet and checked off according to ERD. (unchecked items indicate a mismatch between ERD and spreadsheet, which requires a review)

    • user (one-to-many, many-to-many array of ids)
    • permission (one-to-many)
    • permission_history (one-to-many)
  2. In ERD only (having items here indicates a mismatch, which requires a review)

    • None
@fyliu fyliu mentioned this issue Sep 11, 2022
39 tasks
@fyliu fyliu added this to the All tables added milestone Sep 25, 2022
@ExperimentsInHonesty ExperimentsInHonesty added p-feature: practice area ui/ux, engineering, devops, data science, marketing, etc. s: CTJ stakeholder: Civic Tech Jobs s: VRMS stakeholder: VRMS s: hackforla.org stakeholder: hackforla.org website and removed MVP labels Mar 4, 2023
@ethanstrominger ethanstrominger added the s: kb stakeholder: knowledgebase label Apr 20, 2023
@ethanstrominger ethanstrominger self-assigned this May 3, 2023
@ExperimentsInHonesty ExperimentsInHonesty added the PII: FALSE Table or function does not have or use Personally Identifiable Information (PII) label May 4, 2023
@ExperimentsInHonesty
Copy link
Member

@ethanstrominger I dont see any questions on this right now, so pushing back to in progress. During todays meeting we will discuss how and where to put PRs on the board so that we don't miss them.

fyliu pushed a commit that referenced this issue May 31, 2023
* Issue 63 Create Practice Area Model
@Neecolaa

This comment was marked as resolved.

AzaniaBG pushed a commit to AzaniaBG/peopledepot that referenced this issue Apr 19, 2024
fix: add filenames for the code snippets

docs: fix CONTRIBUTING-related issues

Fix: create card for new issue automation

A recent project board name change broke the automation. This commit updates it to the new project name.

Issue hackforla#63 Create Practice Area Model (hackforla#156)

* Issue 63 Create Practice Area Model

issue 43: Create Program Area model (hackforla#161)

* feat: add model: program_area | feat: register admin: program_area | feat: add endpoints: program_area

Update README.md (hackforla#171)

added skill model

fixed bug in serializer.py

Feature technology table (hackforla#175)

* feat: add model: technology

* feat: register admin: technology

* feat: add endpoints: technology

* Lint warnings and code clean up. Removed unnecessary migration files. Corrected admin name.

* "Lint and code cleanup. Removing previous technology migration. Admin.py name update."

* Modified migrations for technology table.

Removed requirements for python version in pre-commit

fix: lint script not fixing code formatting

swapped black and flake8 in lint.sh file

feat: add language model and api endpoints

feature branch rebase with squashed commits for language model

Update issue templates

Add Permission-type tables
Squash all previous minor commits

Update existing Django model by deleting URL fileds

removed language table models and tests

Updated CONTRIBUTING.md file

Create pull_request_template.md

Add pr template from website team to this repo

Rename recurring_event to event

Set up django-linear-migrations

script: update superuser script to take no input

script: update scripts to take extra commandline args

config: show missing lines in coverage report

tests: add test for ProgramArea model

tests: program_area list

docs: move convenience scripts descriptions to a file

docs: update scripts descriptions for script fixes

squashed 28 commits

rebase origin main to update local main branch
@shmonks shmonks moved this to Done in P: PD: Project Board Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity: missing feature: table creation p-feature: practice area ui/ux, engineering, devops, data science, marketing, etc. PII: FALSE Table or function does not have or use Personally Identifiable Information (PII) role: db architect s: CTJ stakeholder: Civic Tech Jobs s: hackforla.org stakeholder: hackforla.org website s: kb stakeholder: knowledgebase s: VRMS stakeholder: VRMS size: 2pt Can be done in 7-12 hours
Projects
Status: ✅Done
Development

No branches or pull requests

5 participants