LCS version 2 - multiple enhancements

[jdalbey]

Login Page
[x] Username field on login page is a drop down box populated from a file (student_names.txt).

Request Form
[x] Request page allows for entering which lanes are affected.
When Facility = Mainline or Off/On Ramp and Type of Closure = Lane
THEN a new row appears in the form, with lane checkboxes.
(Note: IRL, the user must enter how many lanes, and then which are closed.)
The number of lanes depends on Route and display the corresponding number of checkboxes.
(If Route hasn't been chosen, issue a warning and don't display any checkboxes)
Code it for the average number of lanes per route. 4 of the 5 incidents are on distinct freeways, so using the "average" number of lanes would work fine. Luckily, the two incidents that occur on I-5 both happen at places with the same number of lanes (five).
Implemented to use default of 4 lanes, with these other specific routes and their assigned lane count.

const lanedict = { "5": 5, "73": 3, "405": 4, "55" : 4 };

On a search results page the lanes is shown under Facility.

[x] After Request is submitted, return to Search page.
[x] Supervisor names should have region number, e.g. 22 Joe Doe
[x] Field Rep drop down show all crew (if no supervisor is selected)
[x] Field Rep is populated after Supervisor is chosen to show LeadWorker and Crew for the selected Supervisor.
e.g.,
32-1 Michelle Utica
32-2 Fred Dial
(Note: Currently Field rep is entered into the database but is not displayed in any field of search results. Maybe it's for future use?)

[x] Auto increment closure id's. Have a separate prompt "Is this part of an existing incident?" with No Yes radio buttons, default to Yes, and a drop down box "Select Closure ID" showing existing closures, first slot blank. We can set the default to Yes with the drop down box present and a blank item in the first slot. If they click No, then the drop down disappears. If they leave the default Yes and submit it we can give them an error message to either click No or select a closure number. When the user selects an item the system creates a closure with the same ID but a new Log number. If the checkbox is NOT checked, no drop down box appears, and the system assigns a new Closure ID (using the prescribed scheme of alphabetical ID's. )

Status Form
[x] Use radio buttons instead of checkboxes.
[x] Disable an item that has already been used.
[x] Align submit button with right edge of table

Search Form
[x] Be sure to trim() closure id and make Upper Case before submitting to search.

[x] Search on route must be EXACT search. so '5' should not return any '55'.
Fixed ... error in DB, the logic is fine.
[x] Fix similar defect in calcNextClosureID

# Retrieve any existing closures on this route
#item = db(db.closures.closureid.startswith('T'+routeNum)).select().last() # Might need to sort these
item = db(db.closures.route == routeNum).select().last()

[x] Consider having List function available only for special usernames. Decision: Remove the List function as it is defective, and the same function is Search with no constraints.

Help Page
[x] Add revision date. (Must be manually updated with each release).

Database
[x] Be able to reset the database after each TMC session (to remove entries students created during sesssion) but leave the pre-populated ones.
Implement with a hidden admin page ("resetdb") in the LCS with reset function.

[ ] The database should have some pre-entered M or C type closures. During TMC academy there will be some requests called in from the field to update a closure with a new status. Note: All requests from TMC are T (temporary closures). In real life, they are subsequently updated to M or C if needed. IRL, a supervisor might enter a closure and they can specify M or C.

[jdalbey]

Completed, except for pre-entered M or C type closures.  

Code is not in the repository at the moment since it's a Web2Py application.

[jdalbey]

Code is in branches/LCSv2 of repository.