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

Team Roster Migration from Google Docs #159

Closed
4 of 7 tasks
rachelwhaley opened this issue May 13, 2020 · 8 comments
Closed
4 of 7 tasks

Team Roster Migration from Google Docs #159

rachelwhaley opened this issue May 13, 2020 · 8 comments
Labels
non-essential p-feature: Roster product Product tasks for the next release MVP v0.4 role: Back End size: 2pt Can be done in 7-12 hours

Comments

@rachelwhaley
Copy link
Member

rachelwhaley commented May 13, 2020

Overview

Team rosters are currently maintained in Google Docs, and will soon be managed in VRMS via the Project Team Member collection in our database.

Action Items

  • Bonnie to collect all roster columns into a single doc for analysis
  • Rachel to check that all columns are represented in the User and Project Team Member schemas
  • Need to decide what date to put as the "joined date" since none of the Google Doc records have that. @ExperimentsInHonesty can we pull a join date from when we added them to our Github maybe? Or should we just default it to whatever date we export from the Google Doc?
  • Build a single master roster document for that purpose (we can add people to this roster document during any lag time in the cutover period, until we can add people directly in VRMS)
  • Identify the "cut-over" period (when we'll export the Google Docs and upload them into our DB)
  • Upload data to Project Team Member collection in MongoDB
  • QA the data and make sure the queries bring expected results (e.g., query for all VRMS team members, etc.)

Resources/Instructions

  • Research best way to combine sheets & export (one idea here)
  • Research best way to go from spreadsheet to MongoDB (data formatted correctly, fields labeled clearly, etc.)
@rachelwhaley
Copy link
Member Author

Created data mapping, several questions to resolve before migrating data.

@ExperimentsInHonesty
Copy link
Member

@rachelwhaley

  1. Progress - has speed up the process a bit
  2. Blocks - having difficulty getting the google api for sheets working to combine the rosters, could use help
  3. Availability - have time, just blocked
  4. ETA - can do it manually within a day (45 min of processing time)

New member Nick is going to take a look.

@nickbeaird
Copy link
Contributor

I think that I am starting to get a handle on what I am looking at here now. I see that @rachelwhaley created a document, which is great. I am not yet able to see it. I guess my first question would be will this data be used in Google Sheets continually, or is this a one time migration? Well regardless, feel free to ping me Rachel and I can take a look as well.

@ExperimentsInHonesty
Copy link
Member

  1. Progress: Script done, just finishing
  2. Blockers: none
  3. Availability: evenings only
  4. ETA: Thursday

@rachelwhaley
Copy link
Member Author

Progress: no update from last week. Will address this week.

@rachelwhaley
Copy link
Member Author

  1. Progress: completed python script that combines rosters from all Google docs into a single doc. Can post it to the repo if anyone else needs to use it.
    Blockers, availability, ETA: See Connect and populate Projects and Team Members #124

@jbubar
Copy link
Member

jbubar commented Nov 7, 2023

This will be managed by P Depot in the future. I advise to close, but would like to have the rest of the team take a look first

@jbubar jbubar closed this as not planned Won't fix, can't repro, duplicate, stale Nov 7, 2023
@jbubar
Copy link
Member

jbubar commented Nov 7, 2023

@JackHaeg will bring this up with bonnie if he gets the chance. otherwise we have other issues that are already tracking team roster features

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
non-essential p-feature: Roster product Product tasks for the next release MVP v0.4 role: Back End size: 2pt Can be done in 7-12 hours
Projects
Development

No branches or pull requests