Backlog considerations

[MCatherine1994]

Sprint 5: Pipeline:

• Add deployment to test namespace: when pull request merge to dev, run deployment to dev and test namespace

Database:

• Data model:
  • Update existing tables: update based on the latest form design, add submission status, assignment
  • Add new table: spatial file table

Backend:

• Write APIs to post form data into tables
  • format regular form data and store in correspond tables
  • format spatial file (geojson) and store in correspond tables
  • return confirmation id to frontend

Frontend:

• Login (pre-request: better to have a stable deployment in test namespace, so could provide the app url to FOM's authentication system; better to have a user role table to identify if the login user is a reviewer, otherwise will be a submitter)
• User interface design:
  • Update the form to match latest in CHEFS
  • Create tabs to manage submitter, reviewer interface: "Create a New Submission", "Submissions"
  • Create a submission list interface

Backlogs: Pipeline

• when pull request merge to main, run production deployment, only do this when ready to make it public. If the following development is completely different than the first version, could consider create a new deployment, so could keep both version
• restart the db backup container every time when there is a new deployment
• update pipeline to auto create tables, install postgis to openshift database
• maybe want to update the production database to use a fixed password

Frontend

• Add data validation for each form field, check if all required are entered, if in correct format
• Check file type for uploaded files, show file size in a human readable format, check duplicate files, show a loading icon while uploading
• Disable submission if not pass data validation
• Add feedback interface after submit a form
• Send email confirmation to submitter
• Send email notification to reviewer
• Create a view submission interface
• Enable viewing a submission
• Enable editing a submission
• Enable updating a submission status
• Consider spatial data validation

Backend

• Write apis to export spatial data
• Explore pdf files storage

Database

• Data model
• Postgis for shape file
• Data migration, keep records of db schema for each version of our application

Others

• Create a new branch on top of main branch call it template, delete all custom components, and it will be the template for onboarding future vue3-nestjs-postgres applications

Old backlog:

• compare with ESF, to see the difference using xml format and GeoJSON format
• consider track web traffic data and access log
• check how FOM submit spatial data

[MCatherine1994]

No need after switch to CHEFS