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

Connect and populate Projects and Team Members #124

Closed
3 tasks
rachelwhaley opened this issue Apr 14, 2020 · 10 comments
Closed
3 tasks

Connect and populate Projects and Team Members #124

rachelwhaley opened this issue Apr 14, 2020 · 10 comments
Labels
pbv: 0.3 Issues that were on VRMS v0.3 Development role: Back End

Comments

@rachelwhaley
Copy link
Member

rachelwhaley commented Apr 14, 2020

Overview

We recently added Projects and Project Team Members to the data model - need to connect them to the live database and populate with real data.

Action Items

  • @ExperimentsInHonesty to get us the spreadsheet of projects and project leaders
  • @MasterBirdy and @rachelwhaley to connect on creating the routes and uploading the project data to MongoDB
  • Upload spreadsheet to MongoDB and ensure that everything populates correctly - need to make sure project leaders have user records and are linked to their projects

Resources/Instructions

  • List of project data that Bonnie will get us in spreadsheet form is located here
  • Do all project leaders have user records?
@sarL3y
Copy link
Member

sarL3y commented May 19, 2020

Progress: @sarL3y is populating the project collection in the DB and testing the .populate() functionality.
ETA: ASAP/tomorrow 5/19
Blocks: n/a
Availability: Yes

@sarL3y sarL3y self-assigned this May 19, 2020
@sarL3y sarL3y mentioned this issue May 19, 2020
7 tasks
@switchzer0 switchzer0 added this to the MVP Release milestone May 19, 2020
@sarL3y
Copy link
Member

sarL3y commented Jun 9, 2020

Progress: Projects collection has been populated. Next step is to "join" the various collections using ".populate()"

@ExperimentsInHonesty
Copy link
Member

@rachelwhaley

  1. Progress - partial ready
  2. Blockers - needs time with Matt
  3. Availability - time this week
  4. ETA - a couple of hours after blocker resolved.

@ExperimentsInHonesty
Copy link
Member

@rachelwhaley

  1. Progress - partial ready
  2. Blockers - needs @sarL3y to make @rachelwhaley @ExperimentsInHonesty have admin access to Mongo DB
  3. Availability - time this week
  4. ETA - a couple of hours after blocker resolved.

@sarL3y
Copy link
Member

sarL3y commented Jul 9, 2020

Admin access granted

@ExperimentsInHonesty
Copy link
Member

  1. Progress: none this week
  2. blocks - no avail
  3. availability - some this week
  4. ETA, a couple of hours

@rachelwhaley
Copy link
Member Author

  1. Progress: Completed test load of 11 users/project team members for the TDM project, for demo purposes.
  2. Blocks: Waiting for feedback from devs - before I do a real load, want to make sure the data in the testdb is working as expected.
  3. Availability: weekend
  4. ETA: once the test load looks good, will probably take a few hours to clean data to do the full real load, connect to existing users, etc., so we'll need to schedule that when we're ready.

@ExperimentsInHonesty
Copy link
Member

Let's go live with HomeUniteUs and HfLA website team. - @ExperimentsInHonesty will clean the roster.

@ExperimentsInHonesty
Copy link
Member

  1. Progress: None
  2. Blocks: time
  3. Availability : Monday night after meeting
  4. ETA: By end of monday night.

@switchzer0 switchzer0 removed this from the MVP Release milestone Oct 14, 2020
@alex-anakin
Copy link
Member

This task is obsolete now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pbv: 0.3 Issues that were on VRMS v0.3 Development role: Back End
Projects
Development

No branches or pull requests

6 participants