Difference between revisions of "SAM V2"

From CIDI Wiki
Jump to navigation Jump to search
 
(90 intermediate revisions by 10 users not shown)
Line 1: Line 1:
='''Student Accommodations Manager Version 2 (SAM V2)'''=
{| style="width: 100%; background: #FDF8D6; border: 1px solid #cccccc; text-align: left;"
 
The Student Accommodations Manager Version 2 (SAM V2) is an easy-to-use database software that helps postsecondary Disability Service Providers manage student data, accommodaitons, exams, forms, letters, reports, and more.
 
 
[https://www.uga.edu/amac/samv2 Log in to the SAM V2 Demo]
 
 
SAM V2 allows disability service providers to manage and report on:
 
{| width="100%"
|-
|-
|
| style="text-align: left; vertical-align: top; padding: 0.2em 0.4em;"|
* [[SAM V2:Disabilities|Disabilities]]
[[Image:SAM.png|80px|SAM Logo]]&nbsp;&nbsp;<font size="+1">'''*** NO LONGER AVAILABLE*** THIS IS A REFERENCE PAGE ONLY'''</font>
* [[SAM V2:Accommodations|Accommodations]]
* [[SAM V2:Consent Types|Consent Types]]
* [[SAM V2:Referrals|Referrals]]
* [[SAM V2:Case Notes|Case Notes]]
|
* [[SAM V2:Tasks|Tasks]]
* [[SAM V2:Tests|Tests]]
* [[SAM V2:Orders|Alternate Media Orders]]
* [[SAM V2:Class Schedules|Class Schedules]]
* [[SAM V2:Documentation|Documentation]]
|}
 
==='''Getting Started'''===
 
*The Disability Service Provider needs to identify a campus Information Technology (IT) Professional who will oversee the installation of SAM V2 and manage persmissions and implementation
 
*Installation of SAM V2 is performed by the institution
** SAM V2 requires the institution to have a web server with PHP and MySQL
** The IT Professional can access [[SAM V2:Installation|SAM V2 installation specifics]] and [[SAM V2:Architecture and Features|SAM V2 architecture here]]


==Architecture and Features==
This version of The Student Accommodations Manager (SAM V2) is no longer sold nor supported. Please contact doug.neal@amac.gatech.edu to learn more about The Student Accommodation Manager.


SAM V2 is functionally similar to [[SAM V1]] in terms of data tracking, but differs in terms of architecture, user interface, and reporting.  While [[SAM V1]] follows a [[Wikipedia:Software_as_a_Service|software as a service]] model, SAM V2 requires that the software be installed on computers owned and managed by the user.  Please review the [[Media:SAMV1vsSAMV2.doc|SAM descriptions and pricing document]] for a comparison between SAM V1 and SAM V2.
==Features==


SAM V2 was developed using the leading open source solutions of [http://www.php.net PHP] and [http://www.mysql.com MySQL].  For an overview of [http://www.php.net PHP] and [http://www.mysql.com MySQL] and why these products where used, see [http://media.wiley.com/product_data/excerpt/67/07645574/0764557467.pdf Why PHP and MySQL].
* Totally web-based
 
Other features of SAM V2 include:
 
* Web-based
* Accessible
* Accessible
* Custom, printable reporting
* Custom, printable reporting
* Access control via logins
* Access control via logins and permissions
* Data encryption
* Hardware maintenance and availability are the responsibility of the institution
* Data export
* Software installation and configuration are the responsibility of the institution
* Database backup and availability are the responsibility of the institution


Knowledge of [[Wikipedia:SQL|SQL]] is required to create custom reports using the SAM V2 interfaceAdditionally, [[Wikipedia:SQL|SQL]] can be used to import or manipulate data.
[[Image:Alert.gif|Alert Icon]] For institutions considering SAM V2, it is important to remember:
* The institution must have a web server with [http://www.php.net PHP] and [http://www.mysql.com MySQL] installed. 
*The Disability Service Provider needs to identify a campus [[Portal:IT_Unit|Information Technology]] (IT) Professional who will perform the installation of SAM V2 and manage permissions and implementation.   
*The [[Portal:IT_Unit|IT]] Professional should review the [[SAM V2:Installation|installation specifics]] as well as the architecture and features prior to purchasing SAM V2.


==Terminology==
==Terminology==


SAM V2 is a relational database application, and as such, an understanding of the following database terms and concepts is essential:
SAM V2 is a relational database application.  An understanding of the following terms and concepts is essential to understanding the [[SAM_V1|SAM V1]] design:


* [[Wikipedia:Application_software|Application]]
* [[Wikipedia:Application_software|What is an application?]]
* [[Wikipedia:Database|Database]]
* [[Wikipedia:Database|What is a database?]]
* [[Wikipedia:Record_%28database%29|Record]]
* [[Wikipedia:Record_%28database%29|What is a record?]]
* [[Wikipedia:Field_%28computer_science%29|Field]]
* [[Wikipedia:Field_%28computer_science%29|What is a field?]]
* [[Wikipedia:View_%28database%29|Report or View]]
* [[Wikipedia:View_%28database%29|What is a report or view?]]


==Access==
==Tables==


===Demo===
SAM V2 organizes data into different [[SAM V2:Tables |tables]] that allow you to instantly access, sort, and find information for an individual student or related data sets.


[https://www.uga.edu/amac/samv2 Log in to the SAM V2 Demo].
At the core is the [[SAM V2:Students|Student]] table, however, SAM V2 allows users to manage data for and report on:
 
===Login and Password===
 
Access to SAM V2 requires a login and password. Users are provided with their own login and password that are maintained by the application administrator within the SAM V2 application.
 
Multiple logins with the same login are allowed.
 
Passwords are case sensitive.
 
===Permissions===
 
Within SAM V2, permissions are setup per user for each table.  It is possible to control if the user can add, edit, delete, or view records within the table.  There is no field or record level permission in SAM V2, so if a user can view a table, they can view all records and all fields within the table.
 
==Tables==
 
SAM V2 is comprised of the following tables:


{| width="100%"
{| width="100%"
|-
|-
|
|
* [[SAM V2:Students|Students]]
* [[SAM V2:Disabilities|Disabilities]]
* [[SAM V2:Disabilities|Disabilities]]
* [[SAM V2:Accommodations|Accommodations]]
* [[SAM V2:Accommodations|Accommodations]]
Line 92: Line 46:
* [[SAM V2:Case Notes|Case Notes]]
* [[SAM V2:Case Notes|Case Notes]]
* [[SAM V2:Tasks|Tasks]]
* [[SAM V2:Tasks|Tasks]]
|
* [[SAM V2:Tests|Tests]]
* [[SAM V2:Tests|Tests]]
* [[SAM V2:Orders|Orders]]
* [[SAM V2:Orders|Alternate Media Orders]]
|
* [[SAM V2:Components|Components]]
* [[SAM V2:Components|Components]]
* [[SAM V2:Class Schedules|Class Schedules]]
* [[SAM V2:Class Schedules|Class Schedules]]
* [[SAM V2:Documentation|Documentation]]
* [[SAM V2:Documentation|Documentation]]
|}
In addition, SAM V2 allows for easy application setup and customization by adding or editing records in the following tables:
* [[SAM V2:Accommodation Masters|Accommodation Masters]]
* [[SAM V2:Accommodation Masters|Accommodation Masters]]
* [[SAM V2:Multiple Choice Fields|Multiple Choice Fields]]
* [[SAM V2:Multiple Choice Fields|Multiple Choice Fields]]
Line 103: Line 62:
* [[SAM V2:Users|Users]]
* [[SAM V2:Users|Users]]
* [[SAM V2:Permissions|Permissions]]
* [[SAM V2:Permissions|Permissions]]
|}


For each table, records can be added, edited, deleted, or viewed, depending on the user’s permission. To view table descriptions, relationships, process flows, and detailed field information, click on a table name listed above.
==Access==
 
Access to SAM V2 requires a login and password.  Each user is provided with their own login and password.  It is up to the institution to manage [[SAM V2:Users|user]] accounts.
 
==Security==
 
* Internet transmission can be either unencrypted or employ 128-bit Secure Socket Layer (SSL) encryption.  As the web server is owned and managed by the institution, it depends on the institution to determine the configuration.
* The physical security of the web and database server(s) is the responsibility of the institution.
 
==Permissions==
 
SAM V2 users can access the same data simultaneously. However, using permissions, you can determine what data users can see and what functions users can perform.
 
Functions include adding, editing, viewing or deleting data. For example, a user can be setup so that they can view records in a table but not add records to the table.


==Installation==
Table level permissions can be configured for users.  For example, a user can be setup to access student records but not disability records.  SAM V2 does not support field level permissions.  If a user can view student records, the user can view all fields on the student record.


The installation of SAM V2 is peformed by the customer.
==Reporting==


SAM V2 requires the customer to have a [[Wikipedia:Web Server|web server]] with [http://www.php.net PHP] installed.  The [http://www.php.net PHP] installation must also have the [http://www.mysql.com MySQL] extension installed.  [http://www.mysql.com MySQL] should also be installed, either on the web server or another computer that can communicate with the web server.  For information on installing [http://www.apache.org Apache], [http://www.php.net PHP], and [http://www.mysql.com MySQL], read this recommended [http://www.php-mysql-tutorial.com/index.php PHP MySQL Tutorial].
With SAM V2, you can quickly and easily find and view your data the way you want. Reporting is simple, with:  


Once the above software is installed and configured, SAM V2 is installed as follows:
* A host of pre-defined reports to help you get started quickly.
* A built-in report writer that allows you to create, print, or export tabular and summary reports.
* A powerful Find feature that allows you to filter data by multiple fields.


# Create the MySQL sam database using the sam_shema.sql script.  Typically this database is created by running the following MySQL command: mysql -u root -p[root password] < sam_schema.sql.
A good knowledge of [http://www.w3schools.com/SQL/sql_intro.asp SQL] is required to create custom reports using the SAM V2 [[SAM V2:Reports|report]] interface.
# Create a MySQL user and grant all schema privleges for the sam database to this user. Typically, the easiest way to do this is to use the MySQL Administrator logged in as root.
# Install the SAM V2 PHP source code onto the web server by unzipping and extracting the samv2.zip file.  Be sure to extract the files to the location you intend to use as the URL.  If your web server address is 128.192.60.163 and you extract samv2.zip to the projects directory, then your SAM V2 software URL will be 128.192.60.163/projects/samv2.
# Modify the following programs:
#*dbconnect.php - Change the MySQL connection parameters to be IP address of the machine running your MySQL database, the port number (typically 3306), and the username and password you setup in step 2.
#*header.php - Change the $institution variable to be the name of your institution.
#*index.php - Change the $institution variable to be the name of your institution.
#*notification.php and notification2.php - Change the name of the institution and address lines to be accurate for your institution.
#Place a JPEG image file of your institution logo in the samv2 directory on the web server.  The file name should be logo.jpg.  The logo image should be approximately 180 by 180 pixels.
#Log into the SAM V2 application as the administrator.  Before any users can access the application, you must define users and permissions.  Tools to create users and configure permissions are located under the Administration menu.


==Implementation==
==Implementation==


The customer is reponsible for configuring the SAM V2 application once it is installed. Configuration is peformed by adding or modifying records in the database located under the Administration menu.
The institution is responsible for installing and configuring the SAM V2 software. Most setup customizations are easily performed by adding or modifying records in the database located under the administration menu.


To help with implementation, AMAC has provided a [[Media:SAM_V2_Implementation_Guide.doc|SAM V2 implementation guide]].  This Microsoft Word document helps the customer identify:
To help with implementation, it is important to consider:


* The users who will have access
* The users who will have access
Line 137: Line 101:
* The list of available accommodations
* The list of available accommodations


==Licensing==
Use the [[Media:SAM_V2_Implementation_Guide.doc|SAM V2 Implementation Guide]] to organize necessary information and assist developers with building the application.
 
*[[Media:SAMV2_Services_Agreement.doc|SAM V2 Services Agreement]]
 
==Pricing, Services, and Technical Support==


{| border="1" cellspacing="1" cellpadding="1"
==Customization==
|Initial Application Fee and Training
|
One Payment of $950, AMAC Members $750 (Reduced)
*Source code for the SAM V2 application and database.
*Access to the SAM V2 online application documentation.
*One phone training and one follow-up phone training within 14 days of the purchase.  Training may be conducted via web conferencing based on the user(s) needs.
|-
|Hosting/User Fees
|
None
*PHP and SAM V2 PHP source code are installed on web server owned and managed by institution.
*MySQL and SAM V2 MySQL database are installed on server owned and managed by institution.
*PHP and MySQL are open source.
|-
|Support Fee
|
$500/year
*Estimated ten hours of support per month.
*Covers application questions and assistance with report creation.
|-
|Customization Fee
|
$125/hour
*Covers application customization, import of legacy data, and integration with external systems (i.e. Banner).
|-
|On-Site Customer Training
|
$1,200/day plus travel costs
|}


[[Category:Disability Service Provider]]
* [[SAM V2:customization|Customization Developer Guide]]
[[Category:Software]]

Latest revision as of 10:49, 19 May 2015

SAM Logo  *** NO LONGER AVAILABLE*** THIS IS A REFERENCE PAGE ONLY

This version of The Student Accommodations Manager (SAM V2) is no longer sold nor supported. Please contact doug.neal@amac.gatech.edu to learn more about The Student Accommodation Manager.

Features

  • Totally web-based
  • Accessible
  • Custom, printable reporting
  • Access control via logins and permissions
  • Hardware maintenance and availability are the responsibility of the institution
  • Software installation and configuration are the responsibility of the institution
  • Database backup and availability are the responsibility of the institution

Alert Icon For institutions considering SAM V2, it is important to remember:

  • The institution must have a web server with PHP and MySQL installed.
  • The Disability Service Provider needs to identify a campus Information Technology (IT) Professional who will perform the installation of SAM V2 and manage permissions and implementation.
  • The IT Professional should review the installation specifics as well as the architecture and features prior to purchasing SAM V2.

Terminology

SAM V2 is a relational database application. An understanding of the following terms and concepts is essential to understanding the SAM V1 design:

Tables

SAM V2 organizes data into different tables that allow you to instantly access, sort, and find information for an individual student or related data sets.

At the core is the Student table, however, SAM V2 allows users to manage data for and report on:

In addition, SAM V2 allows for easy application setup and customization by adding or editing records in the following tables:

Access

Access to SAM V2 requires a login and password. Each user is provided with their own login and password. It is up to the institution to manage user accounts.

Security

  • Internet transmission can be either unencrypted or employ 128-bit Secure Socket Layer (SSL) encryption. As the web server is owned and managed by the institution, it depends on the institution to determine the configuration.
  • The physical security of the web and database server(s) is the responsibility of the institution.

Permissions

SAM V2 users can access the same data simultaneously. However, using permissions, you can determine what data users can see and what functions users can perform.

Functions include adding, editing, viewing or deleting data. For example, a user can be setup so that they can view records in a table but not add records to the table.

Table level permissions can be configured for users. For example, a user can be setup to access student records but not disability records. SAM V2 does not support field level permissions. If a user can view student records, the user can view all fields on the student record.

Reporting

With SAM V2, you can quickly and easily find and view your data the way you want. Reporting is simple, with:

  • A host of pre-defined reports to help you get started quickly.
  • A built-in report writer that allows you to create, print, or export tabular and summary reports.
  • A powerful Find feature that allows you to filter data by multiple fields.

A good knowledge of SQL is required to create custom reports using the SAM V2 report interface.

Implementation

The institution is responsible for installing and configuring the SAM V2 software. Most setup customizations are easily performed by adding or modifying records in the database located under the administration menu.

To help with implementation, it is important to consider:

  • The users who will have access
  • The user permissions
  • The multiple-choice field values
  • The list of available accommodations

Use the SAM V2 Implementation Guide to organize necessary information and assist developers with building the application.

Customization