Timeshare UserGuide Admin

From PeacockWiki

Jump to: navigation, search
Overview Students Managers Supervisors Administrators

This document details the instalation, configuration, and maintanence of the Timeshare System.

Contents

Installation Quick Start

Introduction

Timeshare is a database system designed for managing student time sheets and status reports, and providing feedback on these.

Requirements

  • HTTP server
  • PHP 5.0.4
  • MySQL PHP Extensions
  • MySQL

Acquiring

Timeshare is available from CVS or from a published archive.

CVS Details

  • Server: itc307.peacocktech.com
  • User: Anonymous
  • Path: /cvs/itc307
  • Module: sys
cvs -d :pserver:Anonymous@itc307.peacocktech.com:/cvs/itc307 login
# creates a "timeshare" folder in the current directory
cvs -d :pserver:Anonymous@itc307.peacocktech.com:/cvs/itc307 co -d timeshare/ sys

Archive

Contained within the archive will be a directory (usually root) containing source extracted from the sys module of the CVS repository. Once located and extracted, installation is the same regardless of weather you are using an archive or CVS.

Installation

Provided the requirements are satisfied, the only installation required is to place a copy of the system in your HTTP servers public directory. After installation you should be able to see a login form by pointing a browser at your server.

Configuration

The default configuration assumes you have MySQL installed on localhost, connect with user name 'root', and no password, and have created a database called 'timeshare'.

If this is your configuration, you should disable the setup wizard, by removing the line in config.php.

$CONFIG['allow_setup']=1;

Most likely you will want to use your own settings, which can be done by running the setup wizard. This is initiated by pointing a web browser at setup/ under the root of your timeshare installation. A setup link is also provided on the navigation bar of the main login page.

The wizard will step you through and ask for the following details

  • Server, Port and and Schema to use
  • If you want the wizard to create the database
  • The user name and password of the user to access the database
  • Administrative user name and password (if required) (to create database, and associated user)

The wizard asks for details required to run timeshare, and gives you the option to automatically create the database, and a non-administrative user to access that database.

Upon completion, the wizard will overwrite config.php, and in doing so disable itself. It is recommended you backup config.php in a secure location.

If you should ever need to run the wizard again, it may be re-enabled by adding the following line to config.php

$CONFIG['allow_setup']=1;

It should be noted however, that the setup wizard requires no login, and is accessible to any user who has HTTP access to the server. The setup wizard should only be enabled while the server is unavailable to any untrusted network.

Clinton 17/10/2005 Quick and simple. There is nothing too complicated about the admin's role yet. May get a little more complicated with the addition of the setup of project ts and sr schedule.

TimeShare Administration

Before using TimeShare, information about the subject participants should have been collected. This information includes; student??s details (name, e-mail, password, and team role), project groups, and session starting date. This information will be used later in the administration process After logging in using your assigned username and password you will be forwarded to the following administrator home page.

The first step should be to add a session (semester) that you will be administering the system. TimeShare allows for groups and students to start, stop, or defer after any session so the system has to be able to record projects on a per-session basis. Clicking the add a new session link will bring up the next form.

Session code is created by the year eg 2006, and semester; autumn = 40, spring = 70. Therefore the code for first session 2006 will be 200640.

The start of session date is used to calculate the due dates of the timesheets and status reports. It is important that this is accurate so timesheets end at midnight Sunday night. Timesheet periods are currently set at 14 days (2 weeks) and Status Reports at 56 days (8 weeks). When the details are correct, chose the add button.

The next step is to enter all User Details. From the Admin home page, select ??add a user??.

The ??user?? includes administrators, supervisors, team managers and students, therefore the role list selection should reflect this. From the details about each user collected earlier, fill out the form then press save. There is error checking on this form to ensure invalid details are not added to the database. Continue adding until all users are in the database, then return to the home page.

The next step is to add project group names to the session previously added.

Group names will relate to the type of project assigned or made up by the project teams. Add all the session??s group names, one at a time, to the same session code added earlier. Return to the admin home page.

The next task is to set the relations of the last 3 tasks by adding a user to a group. Select ??add user to group??, the following screen will appear.

Choose the correct session to get a list of groups just entered for that session. In a similar fashion, select the name of the user, and the group they are assigned to. Once all 3 of the selections match, press the add button. This process should be repeated until all of the users are assigned to their groups, then return to the home page.

To edit or delete the details of a user, select the ??Edit/Delete a user?? link. You have to type the name or email address of the user you are changing into the test box, press the ??Get User? button to bring up that user??s details.

You can then make changes, or delete the entire record. This feature may be used if a student has left the subject, if they want a new password, or their e-mail address needs updating.

Overview Students Managers Supervisors Administrators
Personal tools