hackforla / hackforla/tdm-calculator

Research: Document PII in RP010 Drive Folder

Open
#2,989 0 comments 0 reactions 0 assignees View on GitHub
deck: staging not for stakeholder dependency documentation feature: Audience Documentation level: easy priority: MUST HAVE research Research: RP010 role: ui/ux research size: 0.25pt
Dominant language
JavaScript
Stars
68
Forks
47
Avg merge
3d 9h
Merged PRs (30d)
25

Description

### Dependency
- #1666

### Overview
We need to identify any content in the Research folder with personal identifiable information (PII) so we can move them to a restricted location.

### Action Items
- [ ] Go through each item in the RP010 folder 1.04
- [ ] Locate any files with PII
- [ ] Open the PII list spreadsheet in Resources 1.03
- [ ] Fill out the content of the spreadsheet by adding the filename, Research plan #, link to document, and year research was completed
- [ ] If there is no PII content, please leave a comment below

### Resources/Instructions
#### Resources for creating this issue
1.01 [Research by participant type folder](https://drive.google.com/drive/folders/1zeAVBuwZRXfV0kwVgFC2fsNioEcIqo34)
1.02 [Research by plan # and name folder](https://drive.google.com/drive/folders/1st19M-g1J7FKkIZ7l-F66lYy5-6SY7tq)
1.03 [PII list](https://docs.google.com/spreadsheets/d/1G52WkGIbnWsJctOqUFZYFifNSam7gcELECO0eaqSh40/edit?gid=1329582060#gid=1329582060)
1.04 [RP010 Drive folder](https://drive.google.com/drive/folders/11NxBgwgpJc2WtAeMNJ8EYIYDpGRX7BSQ)

#### Resources gathered during the completion of this issue
2.01 [RP010 Drive folder](https://drive.google.com/drive/folders/11NxBgwgpJc2WtAeMNJ8EYIYDpGRX7BSQ)

Contributor guide

Open the contributing guide

Research direction

Start with the RP010 Drive folder linked as resource 1.04 and review each item for personally identifiable information. Record the filename, research plan number, document link, and completion year in the PII list spreadsheet linked as resource 1.03; if no PII is found, leave a comment stating that.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.