spencercornish / esof-423-belgrade-senior-center Goto Github PK

Right now, we don't actually retrieve any of the database data for our logged in user. Retrieve the data, and populate the model file.

AC: We know the name, etc. of our user :)

We need a basic form layout for data entry. Make it so.

AC: A page with form elements exists, maybe for user entry, or something.

There is a search box. Add em.

We should trigger a firebase function to compress and resize photos nicely for userprofiles, since we don't want to have to store a massive jpeg for everyone!

We need to have an understanding of what different kinds of data we need to store. Collate a list of all atrributes we need to store in the database

AC: A data.md file exists in the repo, listing all the neat things we need to store.

a volunteer should be able to log in and out and have the time they were at work saved so it can be referenced later (probably in another report)

User Story

As a user, I would like to have a photo of each volunteer, staff member, and member to remember who is who. I would like to be able to easily change this as well.

AC: A user can add a photo to their account, and we properly store it.

When you attempt to add a member to the list that will be attending an activity, you are freely able to add a single person as many times as you want.

We should make it possible to print reports. From the view pages, have an export button which opens a modal with the following options:

• Sort By
• Fields to show on report
• Search criteria (per field)
• Options for portrait vs landscape
• print and save as PDF/CSV options

when a user has a form that is incomplete they should be prompted to fill out the form

a user should be recommended activities based on ones they participated in in the past.

We need to have Continuous Integration. Make it so.

roles stored need to be lower-case but the dropdown checks for capitalized letters

We need to understand what data each type of user can access such as how much a member can see, and how much the administrator can see at any given time.

there needs to be an option to create a printable report of everyone that took a specific class during a given time frame

create an initial README for how to open the project and its (possible) upcoming feature list

create a burn down chart for the project to track our goals

Add more functional testing to ensure that the site is as bug-free as possible.

We need to pick a databse engine. Cost of hosting and ease of use should be considered. Some potential options:

• Hosted MySQL
• Amazon Aurora
• Firebase Firestore
• And more

Having duplicate stream subscriptions is extremely bad for performance because every time we update data we render twice.

As a user, if I navigate to a page while unauthenticated, I want to be redirected to the correct page after I authenticate.

We don't want admins to input invalid data so that at later dates when they try to retrieve information, it is actually usable.

We need to understand the technical level of our consumers. Study the user stories, and design a ruleset to keep UI accessibility in mind.

The edit pages files need to have input validation put onto them for the next release.

The UID for a logged in user conflicts with the data document UID. The solution is to probably define two UIDs, and store the login one on the user. This way, when the user logs in for the first time (after their account is created) we do not duplicate their user state.

The admins need to be able to create meals that they plan on serving for members. A new form page needs to be created that will allow this to happen.

the center will likely want to be able to get a full report on all hours worked by a specific volunteer and hours worked by all volunteers over a specific time frame.

Once we have selected a database engine, we can map out a concrete schema, using the respective database engine we select.

AC: A schema file exists, and accurately portrays our v1 schema.

Validate input and output of the model files.

We need a way to display data to the admins and volunteers, make it happen!

AC: A page exists that can list datapoints to some capacity. This page should be general in style enough to work for other datapoints in the future.

EDIT: Users only for this ticket

need to know who is signed up for what activity and meal

expand the logic of the view members page to two new pages for viewing meals and activities

The admin should be able to create new activities that members can participate in. A new form needs to be made so that this can be done.

Hydrate forms.

there needs to be a way to create a printable report of everyone with a certain need (like disability or medical issue) for grant purposes

when the screen is small enough to be phone sized the data in the table goes off the screen and is no longer visible or reachable

Learn selenium and make some functional tests for our use cases. Primarily,

• Incorrect password
• Incorrect Email
• unknown user
• successful login

The user needs a way to see a detail view of a specific member. This view should allow all attributes to be seen, and transition to an editable state when the user wants to edit the form.

puppeteering test run failed upon a push while creating functional tests. A rerun passed all puppeteering tests.

The add button within the modal is too close to the names. Spread them out so that the modal looks better.

when a user signs up for a meal there needs to be the option to have it delivered to their home

then the window is not full sized but also not small enough to be considered a phone screen the reset password button goes out of the login box on the home screen for chrome

Begin adding tests to our internal systems

We need to create immutable files for each different stored datatypes. We need them for at least

• Users
• Classes
• Meals

Update documentation, create diagrams, and document anything required for the submission.

This should refetch all the datas