TA should be able to see a summary of total hours worked. Hours worked this week, etc.

General summary of how is the TA doing so far into the semester.

This is also where the TA will submit timesheets and will be able to see how many hours were approved and submitted.

Timesheets table is as follows:
id : integer
ta_id : integer (Reference to TA)
week : date (Saturday at the end of the week)
monday: float (amount of hours worked)
tuesday: float (amount of hours worked)
wednesday: float (amount of hours worked)
thursday: float (amount of hours worked)
friday: float (amount of hours worked)
saturday: float (amount of hours worked)
sunday: float (amount of hours worked)
additional: float (amount of hours worked)
total : float (total hours)
memo : text (Any extra information )
approved: boolean (approved by admin)

The admin should be able to add and remove TAs from the learning centre.
Admin should be able to provide an email.
Then an email will be sent to the TA with a one time link to set up his account.

TA should be able to activate or deactivate their account.
TAs sometimes don't work for a semester due to class load or co-op work term and then come back.

Instead of being deleted from the system they can just activate their account.
It is easier to keep them in the system, so we don't forget about them for next semester when they might be back.

The TA can still set his availability to unavailable, when the admin sets the availability changes to locked. The changes are not saved, but the TA should not be able to do any changes when it is locked.

Add glyphs where appropriate to make the website more appealing.
Glyphs instructions

For example:
add floppy-disk glyph next to all the save changes buttons
add floppy-saved glyph next to successful save.
add time glyph next to availability menu
etc.

It would be nice to have a conformation message popup before a deletion is submitted.
A simple confirm message is not good enough though.

I was looking for something more like bootbox.js

Admin should be able to download all CSVs in one click.

Making files on the fly
Download Multiple File

I am not sure if there is a way to do this without actually generating the files on the server. I would prefer doing it the same way each CSV is done.

Missing successful save message on TA profile page.

Create a main page for the application

Admin should be able to set up a list of courses.
TAs should be able to rate the level of knowledge they have of each course.

The list of courses can be stored a single comma separated string in the settings table.
While the rating will be stored in a separate table with ta_id and an integer (1-5)

The link to the list of courses for each TA should be through their profile page.

Some pages do not start with a div col-md-12, so some pages are shifted a bit to the left.

Need to go over all the views and make sure all match the format.

Admin should be able to keep track of hours worked this week and in total.

Admin needs to import availability from the old system.
Admin will provide CSV which will contain the TAs names and their availability.
The format is as follow:
,TA1,TA2,TA3,
10:00,1,0,1,
10:30,1,1,0,
...

The deployment server requires that all field in a table to have a value when inserting a new record.

Need to check each table column and make sure it has a a default value or that it is nullable.

The Admin should be able to view which TAs have updated their availability and when.

Requirements:

• TA can modify his availability
• TA can modify his profile
• Admin can view TAs availability

Admin should be able to download the TAs availability in a csv (Comma separated values) format.

Example for a CSV (TA # is the name of the TA):
,TA 1,TA 2,TA 3,TA 4,TA 5,TA 6,TA 7,TA 8,TA 9,TA 10,TA 11,TA 12,TA 13,TA 14,
9:00,0,0,0,0,0,0,0,0,1,1,0,0,0,1,
9:30,0,0,0,0,0,0,0,0,1,1,0,1,0,1,
10:00,0,0,0,0,2,2,0,0,1,1,0,1,0,1,
10:30,0,0,0,0,2,2,0,0,1,1,0,1,0,1,
11:00,0,0,0,0,2,2,0,0,1,1,0,1,0,1,
11:30,1,0,0,0,2,2,0,0,1,1,0,0,0,1,
12:00,1,0,0,0,2,2,0,0,1,1,0,1,0,1,
12:30,1,0,2,0,2,2,0,0,1,1,0,2,0,1,
13:00,1,0,2,0,2,0,0,0,1,1,0,2,0,1,
13:30,1,0,2,0,2,0,0,0,1,1,0,2,0,1,
14:00,1,0,0,0,2,0,0,0,1,1,0,2,0,1,
14:30,1,2,0,0,2,0,0,1,1,1,0,2,0,1,
15:00,1,2,0,1,0,0,1,1,1,2,0,1,0,1,
15:30,0,2,0,1,0,0,1,1,1,2,0,0,0,1,
16:00,0,2,0,1,0,1,1,0,1,2,0,0,2,1,
16:30,0,2,0,1,0,1,1,0,1,2,0,0,2,1,
17:00,0,2,0,1,0,1,1,0,2,2,0,0,2,1,
17:30,0,2,0,1,0,1,1,0,2,2,0,0,2,1,
18:00,0,2,0,1,0,1,0,0,2,2,0,0,2,1,
18:30,0,2,0,1,0,1,0,0,2,2,0,0,2,1,
19:00,0,2,0,1,0,1,0,0,2,2,0,0,0,1,
19:30,0,2,0,1,0,1,0,0,2,2,0,0,0,1,
20:00,0,2,0,0,0,0,0,0,2,2,0,0,0,0,
20:30,0,2,0,0,0,0,0,0,2,2,0,0,0,0,
21:00,0,2,0,0,0,0,0,0,2,0,0,0,0,0,
21:30,0,2,0,0,0,0,0,0,2,0,0,0,0,0,
22:00,0,2,0,0,0,0,0,0,2,0,0,0,0,0,
22:30,0,0,0,0,0,0,0,0,0,0,0,0,0,0,

Simple login using username and password login on the main page. Users do not have to login to view basic content. There is no need to make registration. Only the admin can create new accounts for TAs.

TA shifts should be done before the creation of the schedule to create a end result for the schedule to aim for.

TA is able to view his own shifts, in a week by week manner.
Shifts will be displayed the same as the availability table, but will include only the shifts assigned to the TA. The TA is able to Drop a shift, which will then be available to other TAs..

On the same table available shifts will be displayed, in other words shifts that some other TA was not able to do. another TA can take the shift if he is able to take the whole shift. Otherwise a TA is able to bid to take part of the shift. If another TA is able to take the rest of the shift, then both TA will be added a portion of the shift. But if another TA can take the whole shift the bid is discarded.

Therefore the structure of the shifts table is as follows:

• id : integer (shift ID)
• ta_id : integer (ID of TA to whom the shift belongs)
• date : date ( day/month/year )
• start : integer (At what time the shift starts)
• end : integer (At what time the shift ends)
• schedule_id : integer (ID of the schedule the shifts are based on)

We will need another table for the the bidding on shifts.
The structure of the shift_bids table is as follows:

• id : integer (bid ID)
• ta_id : integer (ID of TA who bid the shift)
• shift_id ( The ID of the shift the bid is for)
• start : integer (From what time the TA is able to take the shit)
• end : integer (Until what time the TA is able to take the shift)

If there is not another TA to cover the second part of a shift one hour before the shift. Then the TA with the best bid, covers most time, will get the shift his bid. The rest of the shift will be posted as available, until the shift starts. When the shift starts and nobody has taken it, the shift will be discarded.

The Admin should be able to approve or disapprove timesheets submitted.
Once the a timesheet is approved, an email should be sent to payroll.
Email address for payroll should be stored as a setting.

on TA hours page the link to future semester should no be displayed since it does no make sense to look into future semester when you talk about TA hours or time sheets.

Create two interfaces based on TA and Admin role. For start can be as simple as welcome TA or welcome Admin.

TA routing is incorrect should be the same like admin.
The main work is in changing the routes.php file and then the names of the functions in the controllers.

The Admin should be able to generate a schedule by hand.

The Admin will be presented with a table similar to the availability table.

The table will be colour coded with red, yellow and green showing how many TAs are available at each time.

The Admin will start with the days that have the most red, in other words the fewest amount of people available at that day.

The Admin will assign shifts by selecting a day. Once a day is selected a modal will appear with a list of TAs. The list will include TA that are available that day. It will include their availability, preference, total hours assigned to them and start and end of shift assigned to them that day, if any.

The schedule will be stored in the schedule table.

The structure of the schedule table is as follows:

• id : integer (Schedule ID)
• ta_id : integer (The ID of the TA assigned)
• start : integer (At what time the shift starts)
• end : integer (At what time the shift ends)

Steps:

• Create a view of the email.
• Generate a link to the correct week.
• Email all active TAs. (Use the built in Laravel Email system)

Currently a TA is able to select the time column as available. This has no meaning and creates a bug in the javascript.

Visitors of the application who are not logged in should be able to see a list of all the TAs in the learning centre.

Admin should be able to remind a TA to fill his/her availability.

Button has been added on the availability page, but it does not work yet.

Admin should be able to click the Remind button, which will send an automated message.

There should be also a Remind all button, which will send an automated message to all the TAs.

The Admin should be able to post announcements just for TAs and in general on the main page.

A table to store the announcements is needed.
The following can serve as the table:
id : integer (Primary key)
title : string (Title for the announcement)
text : text (Actual text of the announcement)
all : boolean (Post to all or just TAs)