[CoEN & Future Work] -- Comprehensive Issue List

[njirwin]

Things To Be Done By College of Engineering Innovation Day (CoEN), May 3rd

1. Cleanup Front-End - Issue #178
2. Implement Initial Version of Document Generator - Issue #180
3. Finish Initial Component Versions for Admin Portal - Issue # 179
4. Update Google Calendar - Issue #181
5. Update PayPal's BrainTree Drop-In UI - Issue #183
6. Dealing With Failed Payments - Issue # 185
7. Manual Entry for Add a Teacher - Issue # 186
8. Participants Name Spelling Alerts - Issue #187
9. Update Project Website - Issue #192
10. Fix Theme On Non Portal Pages - Issue #233

What Will Work By College of Engineering Innovation Day (CoEN), May 3rd

1. Three Portals: Customer, Teacher, Admin
   • Customer Portal Done
2. Infrastructure Complete (Will Be Modified Later by NNMTA)
3. Database Complete (New Tables Will Be Added Over Summer)
4. Authentication Complete: Standard Login, Facebook Login, Google Login
5. Role-Based Access Control (RBAC): Customer, Teacher, Admin (With Sample Accounts of Each Type)
6. Payment Processing (via PayPal's BrainTree API & Drop-In UI)
7. OAuth

Things To Be Done Over Summer, May - August 2019

1. Progressive Web App (Mobile Ready) - Issue #114
2. Implement Event Scheduler/Manager - Issue #171
3. Song List Processing - Issue #173
4. Add SMS & Email Notifications - Issue #174
5. Update/Notify Customer When Admin Completes Newly Scheduled Event - Issue #[Not Created Yet]
6. Update/Notify Teacher When Admin Completes Newly Scheduled Event - Issue #[Not Created Yet]
7. Teacher Song Selection For Registered Students - Issue #[Not Created Yet]
8. Customer/Teacher Daily Update & Update For Changes To Portal - Issue #[Not Created Yet]
9. Allow Teachers To View Pending/Complete Student Registration Statuses - Issue #[Not Created Yet]
   • In Addition To Pending/Complete Statuses, Teachers Need To See Song Details Per Student
10. Finish The Create An Event Workflow For Administrators - Issue #[Not Created Yet]
    • Create Table Mapping For Level Names To Integers For Database Management Purposes
    • Collect Names From .CSV and Have Them Sort Levels On Front End During Event Creation
    • Create Table Mapping For Levels to Prices During Event Registration In Customer Portal
11. Create A Judges Portal - Issue #[Not Created Yet]
12. Implement Judge Scoring - Issue #[Not Created Yet]
    • Send/Generate Link To Judges Portal
13. Create New Admin Portal Dashboard Card For Checking Incomplete Registrations - Issue #[Not Created Yet]
    • This Component Should Show All Teachers With Outstanding 'Pending' Student Registrations
14. Document Generator - Issue #[Not Created Yet]
    • Finish Building Initial Templates For All Document Types
    • Update Document Generator As Needed For Documents Which Need Event-Scheduler Information
    • Handle .CSV Files And Generate Documents In Excel
15. Begin Work On Archiving/Data Collection - Issue #[Not Created Yet]
    • This Is An Open Ended Feature
      • Archiving Can Include: Event Data, Customer Data, Student Data, Payment Data, Etc.
16. Update The Volunteer Tasks Component In The Teacher Portal - Issue #[Not Created Yet]
    • This Task Requires Feedback From Mrs. Harris First
17. Show Warning When User Attempts To Create An Already Existing Account - Issue #[Not Created Yet]

Other/Misc

1. Fix Copyright (Update Dynamically) - Issue #[Not Created Yet]
2. Update Register For An Event Component - Issue #[Not Created Yet]
   • Remove Dates As Currently Implemented, Add Date Range
     • Have Customers Select Day (Typically Friday, Saturday, Sunday) As Radio Button
     • Then Select Times, Level,...Etc. From A Drop Down List
   • Fix Performance Options Stepper
     • Should Be Two Separate Steps...
       1. Competition Options
       2. Command Performance Options

For Those Tasks Labeled 'Issue [Not Created Yet]'

• The intended purpose is to have these issues added over summer when development for that issue begins.
• They have been intentionally not added to the current task list as of 04/26/2019.

About This Issue #226

• It is meant to be a 'living issue', do not close it.
• It is meant to act as a roadmap primarily for summer development.
• It should be updated with issue numbers for those issues not currently tagged.