Drive Audit: CoP: Engineering

[BCHEN222]

Overview

We need to audit the drive so that we can know what files to move and if the receiving end is ready.

Prerequisite

• access to the 1Password vault for Google Drive Migration
• know your GitHub username and password so that you can use it in a new browser

Action Items

• [ ] Log into the hfla-email-all@hackforla.org email and open it in a new chrome profile, so that all your access is through that Chrome window

Prep

For each of the following items, there are instructions in the wiki. Copy the instruction for next item to be checked off (must do them in order), to a comment below and then complete the item, and hide the comment.

• [x] Find Program Area
• [x] Get Old Drive link
• [x] Identify if there are files in the old folder
• [x] Check that drivemigration@ has access to New Google Drive for this project
• [ ] Get Project Roster link

Audit

• [x] Create Audit Template
• [ ] Perform Drive Migration Audit

File Moving

• [ ] Invite file owners to our next file moving party
• [ ] Once file moving party is completed, add a comment about what is outstanding and move to Questions and Review Column

Resources/Instructions

Project specific links

2.1 Program Area: Communities of Practice 2.2 CoP: Engineering old GDrive 2.3 CoP: Engineering new GDrive 2.4 [CoP: Engineering Roster] 2.5 CoP: Engineering Drive Migration Audit 2.6 [older migration template - audit and move info into new template]

[ExperimentsInHonesty]

added drivemigration email to new drive

[ExperimentsInHonesty]

Check that drivemigration@ has access to New Google Drive for this project

• [x] Go to 1. HfLA Shared Drive Portal
• [x] If the Program Area is a Community of Practice, Go into the folder for the Communities of Practice
• [x] else, Go into the folder Projects by Program Area
  • [ ] Go into the folder for the Program Area
• [x] Find the folder shortcut for the project or CoP
• [x] open the folder shortcut
• [x] go up a level by choosing the name of the project or CoP
• [x] Copy the URL (it should be shorter than the usual google link)
• [x] Add the link to the drive to resource 2.3
• [x] remove the status: needs new drive link label
• [x] check the box for Check that drivemigration@ has access to New Google Drive for this project in the Action items of this issue
• [x] Close the tabs you just opened (wiki and drive)
• [x] Hide this comment as RESOLVED, you are finished with this step

If drivemigration@ does not have access

• [ ] add status: needs shared drive access label
• [ ] unassign yourself from the issue
• [ ] put issue back into the prioritized backlog column
• [ ] Close the tabs you just opened (wiki and drive)