Contents 1 Introduction 2 Web Server 3 Error Logs 4 Database 5 Interface and Logic 6 Important People Involved 7 STS version 3 and beyond

Introduction

STS aka the Student Tracking System, is a web based application for teachers and guidance leaders to make reports on students, and produce statements for UCAS applications.

Web Server

STS runs in side it's own vertual host on ares, the configuration file is /etc/apache2/vhosts/ssl/sts.ssl.conf. There isn't anything particularly exciting in there except custom php, log, and authn config.

Error Logs

The error logs (from the interface's point of view) are in /var/log/php_sts_errors on ares. (not that you'd ever, ever have a reason to look in them ;-)

Database

The database lives on Zeus in MSSQL Server, the database name is STS, connections can be made directly via Active Directory authentication, or through the web interface which uses user account "sts" with password ************ oops ;-).

An access front end for direct access to the database is available on Zeus in \\Zeus\Siapp\IQ Knowledge Base\STS\, this will require an ODBC connection on your workstion.

Interface and Logic

The application lives on ares (at last!)

The data lives in an MSSQL server on zeus, So we have to use a large chain of tools to make a connection to it (and that's is why propriety and closed systems are bad kids ;-), it looks a little something like this:

#==========================================#
#                  Ares                    #
# |--------------------------------------| #
# |               Apache2                | #
# | |----------------------------------| | #
# | |               PHP                | | #
# | | |------------------------------| | | #
# | | |*****STS Web Application******| | | #
# | | |------------------------------| | | #
# | |                |                 | | #
# | | |------------------------------| | | #
# | | |           pear::DB           | | | #
# | | | database abstraction objects | | | #
# | | |------------------------------| | | #
# | |                |                 | | #
# | | |------------------------------| | | #
# | | |   php unixODBC extension     | | | #
# | | |------------------------------| | | #
# | |----------------|-----------------| | #
# |------------------|-------------------| #
#                    |                     #
#    |--------------------------------|    #
#    |           unixODBC             |    #
#    ||------------------------------||    #
#    ||          freeTDS             ||    #
#    ||  Tabular Data Stream Driver  ||    #
#    ||------------------------------||    #
#    |--------------------------------|    #
#==========================================#
                      |
                  (network)
                      |
#==========================================#
#                   Zeus                   #
#     |------------------------------|     #
#     |         MSSQL Server         |     #
#     |------------------------------|     #
#==========================================#

For more information see freeTDS and unixODBC

• the code lives in /srv/www/sts/
• sts has it's very own virtual host configured in apache - /etc/apache2/vhosts/ssl/sts.ssl.conf and /etc/apache2/vhosts/clear/sts.clear.conf

Important People Involved

• Registry - MIS Data Manager exports data from MIS in to the STS database on zeus.
• Guidance leaders - Coordinate the teachers and approve reports. They are the main customer and will make decisions about required features and when it's acceptable to perform maintenance, etc. Barbara Cummins, Sarah Cullen, Celia Green and Marion Bennett are the main stakeholders (at least they have taken the most active interest in the development of STS).
• Web/Intranet Coordinator = interface & Logic developement.

STS version 3 and beyond

Plans for the future:

1. Spell checking against the aspell binary (no pspell module available for php on OES/Linux unless you want to roll your own.)
2. Authentication and access control (i.e. only personal tutors can fill in PT reports and only guidance leaders can approve reports).
3. Secure authenticated student access to reports (requires a method for teachers/PTs/GLs to mark reports as 'ready-for-student')