Create list of tasks that we can turn into Initial stories

[ExperimentsInHonesty]

Overview

We need to surface tasks to make initial stories, in order to create issues.

Action Items

• Add comments to this issue with the tasks you think will need to be turned into stories/issues
• List out the titles of the issues the team agrees to create under resources.
• Create the issues
• Copy the template under resources to the new issue and fill out.
  -`

Resources/Instructions

Issue template

### Dependencies
ANY ISSUE NUMBERS THAT ARE BLOCKERS OR OTHER REASONS WHY THIS WOULD LIVE IN THE ICEBOX

### Overview
WE NEED TO DO X FOR Y REASON

### Action Items
A STEP BY STEP LIST OF ALL THE TASK ITEMS THAT YOU CAN THINK OF NOW EXAMPLES INCLUDE: Research, reporting, etc.

### Resources/Instructions
REPLACE THIS TEXT -If there is a website which has documentation that helps with this issue provide the link(s) here.

Issues team agrees to create

Revisit:

• Add topic area table #14

• Add Asset Type (many to many) table and field (google spreadsheet, HTML, PDF, etc) #15

• Rename

• Rename Gdoc to AssetGroup #21

API

• Table: Create Topic Area, including API and tests, but not many to many #22
• API: Make API schema dynamic #23
• Table: Create Usability table, APIs, and tests #24
• API: Add APIs for Practice Area, Tool, Status / Phase, Program Area, Tool #25

Assets

• Table: Create Asset Table and move fields from Asset Group #26
• 1-M: Create One to Many for Asset to AssetGroup #27
• Field: Add Primary Tool for Asset Group #28
• Asset: Create Asset table #29
• Asset: Create One to Many for Assets to Asset Type #30

Many to Many

• M-M: Asset Group to Practice Area and create script #35
• M-M: Create Python script to dynamically add Many to Many, using Practice Area #36
• M-M: Asset to Tool #37

Data

• Data: Populate data for PracticeArea, either from local file or URL #31
• Data: Populate data for Practice Area and finalize script template #32
• Data: Populate initial data for Asset Groups, Assets, and Topic Area #33
• Data: Populate Users (requires token) #34

[ethanstrominger]

Knowledgebase MVP

• Authentication
  • Auth: Implement single sign on in Django Admim using AllAuth
  • Auth: Create Admin guide which explains how to add roles and what they do. Use existing proposal as draft. Needs to be modified to take approver into account
• PD: Write up strategy to make PD integration configurable, even after application implemented
• PD: Decide on strategy for syncing PD and KB data and implement - possibly WebHooks or queues. Decide on strategy. Must take into account that KB app could potentially be down
• PD: Create PD user when signing up first time through. Decide on strategy. Consider AWS Lambda triggers or queues
• Auth: Change documentation from user roles to user groups
• Enh: Hide google id (and any future generation screens) for role catalog-maintain and catalog-view
  • See https://stackoverflow.com/questions/70709775/how-to-hide-specific-field-by-user-group-on-a-django-admin
  • Enh: Add catalog-maintain and catalog-view to Admin guide

[pwalia1]

Reviewing the Figma Design here under 'Designs by page name', here are the technical tasks for the MVP:

Development:

• Review the data model in Django (model.py or use UI) and compare to Figma design
• Setup Development & Production Databases.
• We will need a database for CI/CD and when we deploy to the web. HackForLA does not use AWS for databases accessible through the web, they use another tool/service - I used it once, but forget the details. When I was doing it for another project, the process was WIP, I had several meetings with them, and then it became de-prioritized.
  Single sign on requires an account in AWS.
• Setup the WebAPI using Django with a project structure that accounts for Controller (middle layer), Data Model & View. Add connection strings to the PostGres DB in AWS in a config file that can later be provided as a secret in the build pipeline.
• Provide Read endpoints in the Web API using Django. The website probably only needs the Read operation & admin portal does not need APIs.
• For each page in the Figma design, create an implementation story. For each page, figure out tables need.
• Add Unit test project to test the APIs as we develop.

CI/CD

• <Build & Deploy tasks: To Be Defined for Dev & Prod>

Testing

• <Testing/Certification tasks: To Be Defined>

Release