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: project_status (used to say project_program_area_status) #46

Open
15 of 16 tasks
Neecolaa opened this issue Sep 4, 2022 · 8 comments · May be fixed by #449
Open
15 of 16 tasks

Create Table: project_status (used to say project_program_area_status) #46

Neecolaa opened this issue Sep 4, 2022 · 8 comments · May be fixed by #449
Assignees
Labels
complexity: small All steps are laid out in detail so that someone new to the project can work on it feature: table creation p-feature: program area all projects have a program area. the CoPs's program area is CoP role: back end s: hackforla.org stakeholder: hackforla.org website s: org stakeholder: the org (includes stats) size: 2pt Can be done in 7-12 hours

Comments

@Neecolaa
Copy link
Member

Neecolaa commented Sep 4, 2022

Overview

We need to create the project_status 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

  • add issue link to the tables tab of the spreadsheet
  • identify and document table description (see spreadsheet under Resources)
  • 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)
  • Create issue for updating projecttable connecting current_status_id to project_status
    -- This was done in the PR attached to this issue instead of creating a new one.
  • 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

Post issue tasks

Resources/Instructions

Description

Dictionary of status options for project and program_area

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)

    • None

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)

  2. In ERD only (having items here indicates a mismatch, which requires a review)

    • None
@Neecolaa Neecolaa changed the title Create Table: project_program_area_type Create Table: project_program_area_status Sep 4, 2022
@Neecolaa Neecolaa mentioned this issue Sep 4, 2022
39 tasks
@fyliu fyliu added this to the All tables added milestone Sep 25, 2022
@ExperimentsInHonesty ExperimentsInHonesty added p-feature: program area all projects have a program area. the CoPs's program area is CoP stakeholder: missing labels Mar 5, 2023
@ExperimentsInHonesty ExperimentsInHonesty added s: hackforla.org stakeholder: hackforla.org website s: org stakeholder: the org (includes stats) and removed stakeholder: missing labels Apr 7, 2023
@ExperimentsInHonesty

This comment was marked as resolved.

@ExperimentsInHonesty ExperimentsInHonesty changed the title Create Table: project_program_area_status Create Table: project_status (used to say project_program_area_status) May 4, 2023
@Neecolaa Neecolaa added the feature: ERD/SS adjustment Requires adjustments to be made to the ERD & Spreadsheet label May 5, 2023
@Neecolaa

This comment was marked as resolved.

@Neecolaa

This comment has been minimized.

@Neecolaa Neecolaa removed role: db architect feature: ERD/SS adjustment Requires adjustments to be made to the ERD & Spreadsheet labels Mar 1, 2024
@shmonks shmonks moved this to Prioritized Backlog in P: PD: Project Board Jun 7, 2024
@fyliu
Copy link
Member

fyliu commented Jun 21, 2024

Need to have initial data in the spreadsheet for project_status table

@fyliu fyliu added complexity: small All steps are laid out in detail so that someone new to the project can work on it ready for product and removed complexity: missing labels Jun 24, 2024
@ExperimentsInHonesty
Copy link
Member

Initial data is
Active
On Hold
Completed
Closed

There is also another bit of information and I don't know exactly where it goes right at this min. But it's a visible: hidden. That is in addition to the status above. e.g., a project that is on-hold and hidden would not show up on the website. This is probably on the project table.

@dmartin4820 dmartin4820 moved this from 📋Prioritized Backlog to 🏗In progress-actively working in P: PD: Project Board Nov 9, 2024
@dmartin4820
Copy link
Member

dmartin4820 commented Nov 14, 2024

Progress: Got my branch setup locally and on my remote fork of the main repo. I just need some fairly easy questions answered and I'll be able to move forward.
Blockers:

  • The issue description says that the program_area model should have a relationship with the project_status model. The row in the PD: Table and field explanations Google sheet doesn't list this relationship (the Lucidchart diagram doesn't indicate a relationship either). Which is correct?
  • The issue also requires me to create another issue to update the current_status_id foreign key field to project_status. It should be possible to do this with the PR that I make for this issue by removing the line here. Should I still create an issue, or make the change I suggest in the PR for this issue?

Availability: Should have time this weekend, and potentially time in the evenings (i.e. 7pm to 9pm).
ETA: Early next week or end of this weekend.

@fyliu
Copy link
Member

fyliu commented Nov 17, 2024

I would confirm with @Neecolaa since it has to do with the database design and since she created this issue and made the change I refer to in the next sentence. From the issue history, it looks like the original issue had to do with project and program_area, and then this line was inadvertently left over when the issue was changed to project_status.

  • The issue also requires me to create another issue to update the current_status_id foreign key field to project_status. It should be possible to do this with the PR that I make for this issue by removing the line here. Should I still create an issue, or make the change I suggest in the PR for this issue?

You're right. It's easier to just do that in this issue. Please update that task to do that.

@Neecolaa
Copy link
Member Author

Fang's correct: when I updated the ERD and spreadsheet I neglected to remove the connection from this issue as well. I've done that now. Thank you for double checking that!

@dmartin4820 dmartin4820 linked a pull request Nov 21, 2024 that will close this issue
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 feature: table creation p-feature: program area all projects have a program area. the CoPs's program area is CoP role: back end s: hackforla.org stakeholder: hackforla.org website s: org stakeholder: the org (includes stats) size: 2pt Can be done in 7-12 hours
Projects
Status: 🏗In progress-actively working
4 participants