Database Overview

(User Table)
 
(25 intermediate revisions not shown)
Line 1: Line 1:
-
For the prototype, we will focus on s small number tables.
+
AppTrac uses a MySQL relational database.  For the prototype, we will focus on s small number tables.
====User Tables====
====User Tables====
 +
<table>
 +
<tr>
 +
<td>
<table border=1>
<table border=1>
<caption>User Table</caption>
<caption>User Table</caption>
Line 8: Line 11:
<td>student<br>volunteer<br>etc</td><td>active<br>etc</td></tr>
<td>student<br>volunteer<br>etc</td><td>active<br>etc</td></tr>
</table>
</table>
 +
</td>
 +
<td>
 +
<table border=1>
 +
<caption>User Types</caption>
 +
<tr><th>Type</th><th>Description</th><th>Access Code</th></tr>
 +
<tr><td>student</td><td>A student has access to<br>applications.</td><td>code</td></tr>
 +
<tr><td>admin</td><td>An admin has access to reports<br>and add/edit students.</td><td>code</td></tr>
 +
<tr><td>...</td><td>...</td><td>...</td></tr>
 +
</table>
 +
</td>
 +
</tr>
 +
</table>
 +
 +
 +
<table border=1>
 +
<caption>User Details</caption>
 +
<tr><th>UserID</th><th>Photo</th><th>Address</th><th>...</th></tr>
 +
</table>
 +
This and related tables should store some subset of the data shown in the following screen capture:
 +
[[Image:hfossLacesKeyInfo.jpg|thumb|left]]
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +
<br>
 +
====Activity Tables====
 +
 +
<table>
 +
<tr>
 +
<td>
 +
<table border=1>
 +
<caption>Activity Log</caption>
 +
<tr><th>Timestamp</th><th>UserId</th><th>Activity Code</th></tr>
 +
<tr><td>3/8/2008 09:00:23</td><td>rsmith</td><td>sys_in</td></tr>
 +
<tr><td>3/8/2008 09:00:33</td><td>rsmith</td><td>lexia_in</td></tr>
 +
<tr><td>3/8/2008 09:14:30</td><td>rsmith</td><td>lexia_out</td></tr>
 +
<tr><td>3/8/2008 09:15:30</td><td>rsmith</td><td>sys_out</td></tr>
 +
<tr><td>...</td><td>...</td><td>...</td></tr>
 +
</table>
 +
</td>
 +
<td>
 +
 +
<table border=1>
 +
<caption>Activity Codes</caption>
 +
<tr><th>Activity Code</th><th>Description</th></tr>
 +
<tr><td>sys_in</td><td>User logged into AppTrac</td></tr>
 +
<tr><td>sys_out</td><td>User logged out of AppTrac</td></tr>
 +
<tr><td>lexia_in</td><td>User started Lexia Application</td></tr>
 +
<tr><td>...</td><td>...</td></tr>
 +
</table>
 +
</td>
 +
</tr>
 +
</table>
 +
 +
 +
 +
[[Category:AppTrac]]

Current revision as of 20:53, 5 October 2008

AppTrac uses a MySQL relational database. For the prototype, we will focus on s small number tables.

User Tables

User Table
UserIDNamePasswordTypeStatus
Unique
autogenerated
Stringencrypted student
volunteer
etc
active
etc
User Types
TypeDescriptionAccess Code
studentA student has access to
applications.
code
adminAn admin has access to reports
and add/edit students.
code
.........


User Details
UserIDPhotoAddress...

This and related tables should store some subset of the data shown in the following screen capture:







Activity Tables

Activity Log
TimestampUserIdActivity Code
3/8/2008 09:00:23rsmithsys_in
3/8/2008 09:00:33rsmithlexia_in
3/8/2008 09:14:30rsmithlexia_out
3/8/2008 09:15:30rsmithsys_out
.........
Activity Codes
Activity CodeDescription
sys_inUser logged into AppTrac
sys_outUser logged out of AppTrac
lexia_inUser started Lexia Application
......