Latest revision as of 03:52, 29 August 2016

Locker Registration has been added to CrossRoad Online Services for Students. The first registered locker for each student is also displayed on the address tab of the Current Students window.

Process

There are two modes in which students may register a locker:

1. QR Code Scanning. A QR code sticker has been placed on each locker that directs the scanning device to the web process for locker registration. If the locker is available, the student is asked for his/her student ID and PIN.

2. Online Services. In online services, students may choose the locker registration item, and then select the locker from the drop down list.

In both modes registering a locker releases any other locker registration. In the second a student can simply release his/her locker.

Viewer

For a number of staff, a viewer application has been created. This url should not generally be advertised or linked, although it is protected by active directory userids and passwords.

Support Tables

There are three support tables that are used in the Locker Registration Process.

Lockers.dbf (index lockers.ntx) - this is the list of lockers. The in_service field could be used to remove a locker from the active inventory. For example, if a locker is out of service for repairs, this field would remove it from being able to be registered.

LockReg.dbf (indexes lockr1.ntx, lockr2.ntx, lockr3.ntx, lockr4.ntx) - this is the list of locker registrations. The entcode links this to a student, or in some cases employee. The locker id matches that from Lockers.dbf. Reg_on and Reg_at record the date and time the student registered the locker. Rel_on and Rel_at record the date and time the locker was released.

LockVUsr.dbf (index lockvusr.ntx) - this records the active directory userids of those permitted to access the viewer. This should all be uppercase. Note that password testing is done against AD.

Troubleshooting

The support tables can be directly viewed and edited, although that should be done with caution. Some examples of issues that have arisen so far are:

• duplicate registrations. Due to a couple of bugs from out of scope use-cases, duplicate registrations were possible. This was due to a) inadvertant lowercasing of locker codes and b) a fix for a that made lockreg entries appear to be out of order for individual students, giving access to lockers that were actually registered. In both cases, the cgi was fixed to repair.

• allocating lockers to departments. Lockers are allocated to the cafeteria and to the library. The registrations for those were done by adding records to lockreg using the departmental file number.

• deallocating lockers from departments. When a locker is to be deallocated from a department, simply fill in the REL_ON and REL_AT fields for that departments locker entry in lockreg.dbf

Further Processes to be developed

A process in CrossRoad, Students > Global Processes > Address Related, exists to clear all locker registrations.

Main Page