Drive Audit: Engage

[CharityLai6]

Dependency

• [ ] Waiting on the instructions to be completed in the wiki page: perform drive migration audit

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

• [x] 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
• [x] Get Project Roster link

Audit

• [x] Create Audit Template
• [x] 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: Citizen Engagement 2.2 Engage old GDrive 2.3 Engage new GDrive 2.4 Engage Roster 2.5 Engage Drive Migration Audit 2.6 [older migration template - audit and move info into new template]

[ExperimentsInHonesty]

Identify if there are files in the old folder

• [x] Open the resource 2.2
• [x] are there files in it?
  • [x] yes
  • [x] Remove the status: check if files to move label
  • [x] Hide this comment, you are finished with this step
  • [ ] if no, continue below

If there are no files to move

• [ ] add a comment with this text

  there are no files in the old folder to be moved, and it:
  - [ ] has folders
  - [ ] does not have folders or files (entirely empty)

• [ ] Remove the status: check if files to move label
• [ ] close issue

[Rabia2219]

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

• [x] open Google Shared Drive
• [x] look for project name
• [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] 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

[Rabia2219]

Get Project Roster link

• [x] Search inside their new drive (resource 2.3) for their project roster
• [x] Add a link to the project roster to resource 2.4
• [x] Remove the status: needs project roster label
• [x] check the box for Get Project Roster link in the Action items of this issue
• [x] Hide this comment as RESOLVED, you are finished with this step

If Project Roster not found in new drive

• [ ] add this comment to your issue

  I could not find a project roster in the project's new drive

• [ ] Check old drive (resource 2.2) to see if there is a roster there
  • [ ] If you find one, add a link to it in the resources section with the text OLD DRIVE ROSTER
• [ ] Move the issue to the Questions/Review column of the project board