https://www.amacusg.gatech.edu/wiki/api.php?action=feedcontributions&user=Ben&feedformat=atomCIDI Wiki - User contributions [en]2024-03-28T20:12:42ZUser contributionsMediaWiki 1.36.0https://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:import&diff=4988SAM V1:import2009-06-29T19:27:00Z<p>Ben: </p>
<hr />
<div>=='''Banner Data'''==<br />
<br />
In order to import data into SAM a Banner data extract/script will have to be created. There are two SAM tables that need to be submitted to the Banner IT professional '''student and class schedules'''. The Banner data extract format can be either a [[Wikipedia:Comma-separated_values|CSV]] file or a Tab-Delimited text file. Ideally the DSP should be able to run the Banner extract (created by the Banner IT professional) on demand and save the data to a local file. This local file would then be [https://www.quickbase.com/help/default.html#importing_data.html imported] by the end-user into SAM. <br />
<br />
'''THE DSP SHOULD SUBMIT A COPY OF THE '''[[Student]]''' AND '''[[Class Schedules]]''' DATA TO THEIR BANNER IT REPRESENTATIVE.''' From that point the Banner It representative can assemble a script containing all students receiving disability services. Now the DSP has a list from Banner that contains all of the required fields for SAM. The Banner IT representative should make the script into a process that the DSP can use weekly to update SAM.<br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:import&diff=4987SAM V1:import2009-06-29T19:24:57Z<p>Ben: </p>
<hr />
<div>=='''Banner Data'''==<br />
<br />
In order to import data into SAM a Banner data extract/script will have to be created. There are two SAM tables that need to be submitted to the Banner IT professional '''student and class schedules'''. The Banner data extract format can be either a [[Wikipedia:Comma-separated_values|CSV]] file or a [[Wikipedia:Tab-Delimited|Tab-Delimited]] text file. Ideally the DSP should be able to run the Banner extract (created by the Banner IT professional) on demand and save the data to a local file. This local file would then be [https://www.quickbase.com/help/default.html#importing_data.html imported] by the end-user into SAM. <br />
<br />
'''THE DSP SHOULD SUBMIT A COPY OF THE '''[[Student]]''' AND '''[[Class Schedules]]''' DATA TO THEIR BANNER IT REPRESENTATIVE.''' From that point the Banner It representative can assemble a script containing all students receiving disability services. Now the DSP has a list from Banner that contains all of the required fields for SAM. The Banner IT representative should make the script into a process that the DSP can use weekly to update SAM.<br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:import&diff=4986SAM V1:import2009-06-29T19:24:45Z<p>Ben: </p>
<hr />
<div>=='''Banner Data'''==<br />
<br />
In order to import data into SAM a Banner data extract/script will have to be created. There are two SAM tables that need to be submitted to the Banner IT professional '''student and class schedules'''. The Banner data extract format can be either a [[Wikipedia:Comma-separated_values|CSV]] file or a [[Wikipedia:Tab-Delimited|Tab-Delimited] text file. Ideally the DSP should be able to run the Banner extract (created by the Banner IT professional) on demand and save the data to a local file. This local file would then be [https://www.quickbase.com/help/default.html#importing_data.html imported] by the end-user into SAM. <br />
<br />
'''THE DSP SHOULD SUBMIT A COPY OF THE '''[[Student]]''' AND '''[[Class Schedules]]''' DATA TO THEIR BANNER IT REPRESENTATIVE.''' From that point the Banner It representative can assemble a script containing all students receiving disability services. Now the DSP has a list from Banner that contains all of the required fields for SAM. The Banner IT representative should make the script into a process that the DSP can use weekly to update SAM.<br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:import&diff=4985SAM V1:import2009-06-29T19:22:41Z<p>Ben: </p>
<hr />
<div>=='''Banner Data'''==<br />
<br />
In order to import data into SAM a Banner data extract/script will have to be created. There are two SAM tables that need to be submitted to the Banner IT professional '''student and class schedules'''. The Banner data extract format can be either a [[Wikipedia:Comma-separated_values|CSV]] file or a [[http://en.wikipedia.org/wiki/Delimiter-separated_values|tab-delimited] text file. Ideally the DSP should be able to run the Banner extract (created by the Banner IT professional) on demand and save the data to a local file. This local file would then be [https://www.quickbase.com/help/default.html#importing_data.html imported] by the end-user into SAM. <br />
<br />
'''THE DSP SHOULD SUBMIT A COPY OF THE '''[[Student]]''' AND '''[[Class Schedules]]''' DATA TO THEIR BANNER IT REPRESENTATIVE.''' From that point the Banner It representative can assemble a script containing all students receiving disability services. Now the DSP has a list from Banner that contains all of the required fields for SAM. The Banner IT representative should make the script into a process that the DSP can use weekly to update SAM.<br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:import&diff=4984SAM V1:import2009-06-29T19:21:52Z<p>Ben: </p>
<hr />
<div>=='''Banner Data'''==<br />
<br />
In order to import data into SAM a Banner data extract/script will have to be created. There are two SAM tables that need to be submitted to the Banner IT professional '''student and class schedules'''. The Banner data extract format can be either a [[Wikipedia:Comma-separated_values|CSV]] file or a [http://en.wikipedia.org/wiki/Delimiter-separated_values | tab-delimited] text file. Ideally the DSP should be able to run the Banner extract (created by the Banner IT professional) on demand and save the data to a local file. This local file would then be [https://www.quickbase.com/help/default.html#importing_data.html imported] by the end-user into SAM. <br />
<br />
'''THE DSP SHOULD SUBMIT A COPY OF THE '''[[Student]]''' AND '''[[Class Schedules]]''' DATA TO THEIR BANNER IT REPRESENTATIVE.''' From that point the Banner It representative can assemble a script containing all students receiving disability services. Now the DSP has a list from Banner that contains all of the required fields for SAM. The Banner IT representative should make the script into a process that the DSP can use weekly to update SAM.<br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:import&diff=4983SAM V1:import2009-06-29T19:21:39Z<p>Ben: </p>
<hr />
<div>=='''Banner Data'''==<br />
<br />
In order to import data into SAM a Banner data extract/script will have to be created. There are two SAM tables that need to be submitted to the Banner IT professional '''student and class schedules'''. The Banner data extract format can be either a [[Wikipedia:Comma-separated_values|CSV]] file or a [[http://en.wikipedia.org/wiki/Delimiter-separated_values | tab-delimited]] text file. Ideally the DSP should be able to run the Banner extract (created by the Banner IT professional) on demand and save the data to a local file. This local file would then be [https://www.quickbase.com/help/default.html#importing_data.html imported] by the end-user into SAM. <br />
<br />
'''THE DSP SHOULD SUBMIT A COPY OF THE '''[[Student]]''' AND '''[[Class Schedules]]''' DATA TO THEIR BANNER IT REPRESENTATIVE.''' From that point the Banner It representative can assemble a script containing all students receiving disability services. Now the DSP has a list from Banner that contains all of the required fields for SAM. The Banner IT representative should make the script into a process that the DSP can use weekly to update SAM.<br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:import&diff=4982SAM V1:import2009-06-29T19:21:18Z<p>Ben: </p>
<hr />
<div>=='''Banner Data'''==<br />
<br />
In order to import data into SAM a Banner data extract/script will have to be created. There are two SAM tables that need to be submitted to the Banner IT professional '''student and class schedules'''. The Banner data extract format can be either a [[Wikipedia:Comma-separated_values|CSV]] file or a [[http://en.wikipedia.org/wiki/Delimiter-separated_values|tab-delimited]] text file. Ideally the DSP should be able to run the Banner extract (created by the Banner IT professional) on demand and save the data to a local file. This local file would then be [https://www.quickbase.com/help/default.html#importing_data.html imported] by the end-user into SAM. <br />
<br />
'''THE DSP SHOULD SUBMIT A COPY OF THE '''[[Student]]''' AND '''[[Class Schedules]]''' DATA TO THEIR BANNER IT REPRESENTATIVE.''' From that point the Banner It representative can assemble a script containing all students receiving disability services. Now the DSP has a list from Banner that contains all of the required fields for SAM. The Banner IT representative should make the script into a process that the DSP can use weekly to update SAM.<br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:import&diff=4981SAM V1:import2009-06-29T19:20:57Z<p>Ben: </p>
<hr />
<div>=='''Banner Data'''==<br />
<br />
In order to import data into SAM a Banner data extract/script will have to be created. There are two SAM tables that need to be submitted to the Banner IT professional '''student and class schedules'''. The Banner data extract format can be either a [[Wikipedia:Comma-separated_values|CSV]] file or a [http://en.wikipedia.org/wiki/Delimiter-separated_values|tab-delimited] text file. Ideally the DSP should be able to run the Banner extract (created by the Banner IT professional) on demand and save the data to a local file. This local file would then be [https://www.quickbase.com/help/default.html#importing_data.html imported] by the end-user into SAM. <br />
<br />
'''THE DSP SHOULD SUBMIT A COPY OF THE '''[[Student]]''' AND '''[[Class Schedules]]''' DATA TO THEIR BANNER IT REPRESENTATIVE.''' From that point the Banner It representative can assemble a script containing all students receiving disability services. Now the DSP has a list from Banner that contains all of the required fields for SAM. The Banner IT representative should make the script into a process that the DSP can use weekly to update SAM.<br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:import&diff=4980SAM V1:import2009-06-29T19:20:43Z<p>Ben: </p>
<hr />
<div>=='''Banner Data'''==<br />
<br />
In order to import data into SAM a Banner data extract/script will have to be created. There are two SAM tables that need to be submitted to the Banner IT professional '''student and class schedules'''. The Banner data extract format can be either a [[Wikipedia:Comma-separated_values|CSV]] file or a [[http://en.wikipedia.org/wiki/Delimiter-separated_values|tab-delimited]] text file. Ideally the DSP should be able to run the Banner extract (created by the Banner IT professional) on demand and save the data to a local file. This local file would then be [https://www.quickbase.com/help/default.html#importing_data.html imported] by the end-user into SAM. <br />
<br />
'''THE DSP SHOULD SUBMIT A COPY OF THE '''[[Student]]''' AND '''[[Class Schedules]]''' DATA TO THEIR BANNER IT REPRESENTATIVE.''' From that point the Banner It representative can assemble a script containing all students receiving disability services. Now the DSP has a list from Banner that contains all of the required fields for SAM. The Banner IT representative should make the script into a process that the DSP can use weekly to update SAM.<br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V2:import&diff=4979SAM V2:import2009-06-29T19:16:39Z<p>Ben: </p>
<hr />
<div>=='''Banner Data'''==<br />
<br />
In order to import data into SAMV2 a Banner data extract/script will have to be created. There are two SAM tables that need to be submitted to the Banner IT professional '''student and class schedules'''. The Banner data extract format can be either a [[Wikipedia:Comma-separated_values|CSV]] file or a tab-delimited text file. Ideally the IT professional should be able to run the Banner extract on demand and save the data to a local file. This local file would then be loaded/updated by the IT professional using SQL/MySQL into SAM.<br />
'''THE IT PROFESSIONAL SHOULD SUBMIT A COPY OF THE '''[[Student]]''' AND '''[[Class Schedules]]''' DATA TO THEIR BANNER IT REPRESENTATIVE.''' <br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:import&diff=4978SAM V1:import2009-06-29T19:14:45Z<p>Ben: </p>
<hr />
<div>=='''Banner Data'''==<br />
<br />
In order to import data into SAM a Banner data extract/script will have to be created. There are two SAM tables that need to be submitted to the Banner IT professional '''student and class schedules'''. The Banner data extract format can be either a [[Wikipedia:Comma-separated_values|CSV]] file or a tab-delimited text file. Ideally the DSP should be able to run the Banner extract (created by the Banner IT professional) on demand and save the data to a local file. This local file would then be [https://www.quickbase.com/help/default.html#importing_data.html imported] by the end-user into SAM. <br />
<br />
'''THE DSP SHOULD SUBMIT A COPY OF THE '''[[Student]]''' AND '''[[Class Schedules]]''' DATA TO THEIR BANNER IT REPRESENTATIVE.''' From that point the Banner It representative can assemble a script containing all students receiving disability services. Now the DSP has a list from Banner that contains all of the required fields for SAM. The Banner IT representative should make the script into a process that the DSP can use weekly to update SAM.<br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V2&diff=4977SAM V22009-06-26T19:23:58Z<p>Ben: </p>
<hr />
<div>{| style="width: 100%; background: #FDF8D6; border: 1px solid #cccccc; text-align: left;"<br />
|-<br />
| style="text-align: left; vertical-align: top; padding: 0.2em 0.4em;"|<br />
[[Image:Database.gif|Database Icon]]&nbsp;&nbsp;<font size="+1">'''Student Accommodation Manager Version 2 (SAM V2)'''</font><br />
<br />
The Student Accommodations Manager Version 2 (SAM V2) is a secure, web-based database application designed to help postsecondary Disability Service Providers manage student data, disabilities, accommodations, case notes, and much more. SAM V1 was developed using the leading open source solutions of [http://www.php.net PHP] and [http://www.mysql.com MySQL]. SAM V2 follows a traditional purchased software model where the SAM V2 software and database, along with PHP and MySQL, are installed on a server owned and managed by the institution. Essential functions such as installation, system availability and backups are the responsibility of the institution. Predefined reports as well as a report writer allow you to quickly find, filter, and transform data; however, knowledge of [http://www.w3schools.com/SQL/sql_intro.asp SQL] is required. For institutions with solid IT support, SAM V2 offers an affordable multi-user, web-based solution. <br />
<br />
<br />
[[Image:help.gif|Help Icon]]&nbsp;'''Learn More:'''<br />
<br />
*SAM V2 Fact Sheet<br />
*[https://www.uga.edu/amac/samv2/ SAM V2 Demo Application], for access please contact Joe Davis at 866-279-2964 or davisj@uga.edu <br />
*[[Media:SAMV1vsSAMV2.pdf|Comparison of SAM V1 and SAM V2]]<br />
*[http://media.wiley.com/product_data/excerpt/67/07645574/0764557467.pdf Why PHP and MySQL]<br />
| align="center" style="width: 20%;"|<br />
__TOC__<br />
|}<br />
<br />
==Features==<br />
<br />
* Totally web-based<br />
* Accessible<br />
* Custom, printable reporting<br />
* Access control via logins and permissions<br />
* Hardware maintenance and availability are the responsibility of the institution<br />
* Software installation and configuration are the responsibility of the institution<br />
* Database backup and availability are the responsibility of the institution<br />
<br />
[[Image:Alert.gif|Alert Icon]] For institutions considering SAM V2, it is important to remember:<br />
* The institution must have a web server with [http://www.php.net PHP] and [http://www.mysql.com MySQL] installed. <br />
*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. <br />
*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.<br />
<br />
==Terminology==<br />
<br />
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:<br />
<br />
* [[Wikipedia:Application_software|What is an application?]]<br />
* [[Wikipedia:Database|What is a database?]]<br />
* [[Wikipedia:Record_%28database%29|What is a record?]]<br />
* [[Wikipedia:Field_%28computer_science%29|What is a field?]]<br />
* [[Wikipedia:View_%28database%29|What is a report or view?]]<br />
<br />
==Tables==<br />
<br />
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.<br />
<br />
At the core is the [[SAM V2:Students|Student]] table, however, SAM V2 allows users to manage data for and report on:<br />
<br />
{| width="100%"<br />
|-<br />
|<br />
* [[SAM V2:Disabilities|Disabilities]]<br />
* [[SAM V2:Accommodations|Accommodations]]<br />
* [[SAM V2:Consent Types|Consent Types]]<br />
* [[SAM V2:Referrals|Referrals]]<br />
* [[SAM V2:Case Notes|Case Notes]]<br />
* [[SAM V2:Tasks|Tasks]]<br />
|<br />
<br />
* [[SAM V2:Tests|Tests]]<br />
* [[SAM V2:Orders|Alternate Media Orders]]<br />
* [[SAM V2:Components|Components]]<br />
* [[SAM V2:Class Schedules|Class Schedules]]<br />
* [[SAM V2:Documentation|Documentation]]<br />
|}<br />
<br />
In addition, SAM V2 allows for easy application setup and customization by adding or editing records in the following tables:<br />
<br />
* [[SAM V2:Accommodation Masters|Accommodation Masters]]<br />
* [[SAM V2:Multiple Choice Fields|Multiple Choice Fields]]<br />
* [[SAM V2:Reports|Reports]]<br />
* [[SAM V2:Users|Users]]<br />
* [[SAM V2:Permissions|Permissions]]<br />
<br />
==Access==<br />
<br />
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.<br />
<br />
==Security==<br />
<br />
* 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.<br />
* The physical security of the web and database server(s) is the responsibility of the institution.<br />
<br />
==Permissions==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
==Reporting==<br />
<br />
With SAM V2, you can quickly and easily find and view your data the way you want. Reporting is simple, with: <br />
<br />
* A host of pre-defined reports to help you get started quickly. <br />
* A built-in report writer that allows you to create, print, or export tabular and summary reports. <br />
* A powerful Find feature that allows you to filter data by multiple fields. <br />
<br />
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.<br />
<br />
==Implementation==<br />
<br />
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.<br />
<br />
To help with implementation, [http://www.amac.uga.edu/ AMAC] has developed a [[Media:SAMV1 Implementation Guide w instructions.doc|SAMV1 Implementation Guide w instructions]]. This document helps the disability service provider identify:<br />
<br />
* The users who will have access<br />
* The user permissions<br />
* The multiple-choice field values<br />
* The list of available accommodations<br />
<br />
==Licensing Agreement==<br />
<br />
*[[Media:SAMV2_Services_Agreement.doc|SAM V2 Services Agreement]]<br />
<br />
==Pricing==<br />
<br />
{|width="100%" border="0" cellspacing="0" cellpadding="0" valign="top" <br />
|-<br />
| colspan="2" style="border: 1px solid #cccccc; text-align: left; background: #cedff2; font-weight: bold; color: #000000; padding: 0.2em 0.4em;"|<br />
===Required Costs===<br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Initial Application Fee and Training<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
One Payment of $950, [[Disability_Professional_Member_Guide|AMAC Members]] $750 (Reduced) <br />
*Source code for the SAM V2 application and database.<br />
*Access to the SAM V2 online application documentation. <br />
*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.<br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Hosting/User Fees<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
None<br />
*PHP and SAM V2 PHP source code are installed on web server owned and managed by institution.<br />
*MySQL and SAM V2 MySQL database are installed by the institution on server owned and managed by institution.<br />
*PHP and MySQL are open source.<br />
|-<br />
| style="border-left: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Support Fee<br />
| style="border-left: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$500/year <br />
*Required the first year of purchase.<br />
*Estimated ten hours of support per month.<br />
*Covers application questions and assistance with report creation.<br />
|-<br />
| colspan="2" style="border: 1px solid #cccccc; text-align: left; background: #cedff2; font-weight: bold; color: #000000; padding: 0.2em 0.4em;"|<br />
<br />
===Optional Costs===<br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Support Fee<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$500/year <br />
*Optional after the first year of purchase.<br />
*Estimated ten hours of support per month.<br />
*Covers application questions and assistance with report creation.<br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Customization Fee<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$125/hour <br />
*Covers application customization, import of legacy data, and integration with external systems (i.e. Banner).<br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
On-Site Customer Training<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$1,200/day plus travel costs <br />
|}<br />
<br />
[[Category:Disability Service Provider]]<br />
[[Category:Information Technology]]<br />
[[Category:Software]]<br />
[[Category:Reference]]</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1&diff=4976SAM V12009-06-26T19:22:55Z<p>Ben: </p>
<hr />
<div>{| style="width: 100%; background: #FDF8D6; border: 1px solid #cccccc; text-align: left;"<br />
|-<br />
| style="text-align: left; vertical-align: top; padding: 0.2em 0.4em;"|<br />
[[Image:Database.gif|Database Icon]]&nbsp;&nbsp;<font size="+1">'''Student Accommodation Manager Version 1 (SAM V1)'''</font><br />
<br />
The Student Accommodations Manager Version 1 (SAM V1) is a secure, web-based database application designed to help postsecondary Disability Service Providers manage student data, disabilities, accommodations, case notes, and much more. SAM V1 is developed and hosted using Intuit's [http://www.quickbase.com QuickBase] and follows a [[Wikipedia:Software_as_a_service|software-as-a-service]] model where there is no software to install or server to manage or own. Essential functions such as system availability and backups are provided for you. Predefined reports as well as a powerful report writer allow you to quickly and easily find, filter, and transform data. SAM V1 can also serve as a forms repository and auto-generate accommodation notification letters. For institutions lacking strong IT support, SAM V1 offers a viable multi-user, web-based solution.<br />
<br />
<br />
[[Image:help.gif|Help Icon]]&nbsp;'''Learn More:'''<br />
<br />
*SAM V1 Fact Sheet<br />
*[https://www.quickbase.com/db/bcsnjrd97 SAM V1 Demo Application], for access please contact Joe Davis at 866-279-2964 or [mailto:davisj@uga.edu davisj@uga.edu]<br />
*[[Media:SAMV1vsSAMV2.pdf|Comparison of SAM V1 and SAM V2]]<br />
| align="center" style="width: 20%;"|<br />
__TOC__<br />
|}<br />
<br />
<!-- Do not remove this next line as it inserts spacing between the introduction and the contents --><br />
<div style="height: 5px;">&nbsp;</div><br />
<br />
==Features==<br />
<br />
SAM V1 was developed using Intuit's [http://www.quickbase.com QuickBase] and utilizes standard QuickBase features and [http://quickbase.intuit.com/overview/security/ security], including:<br />
<br />
* Totally web-based<br />
* 24-hour, 365-day availability<br />
* No special software or installations required<br />
* Operational with a screen reader [http://www.amac.uga.edu/samvpat.php VPAT] Voluntary Product Accessibility Template<br />
* Accessible<br />
* Custom, printable reporting<br />
* Email integration<br />
* Searchable on-line help<br />
* Advanced access control via logins, users and roles<br />
* Data encryption<br />
* Daily backups<br />
* Redundant data storage<br />
<br />
==Terminology==<br />
<br />
SAM V1 is a relational database application. An understanding of the following terms and concepts is essential to understanding the SAM V1 design:<br />
<br />
* [[Wikipedia:Application_software|What is an application?]]<br />
* [[Wikipedia:Database|What is a database?]]<br />
* [http://www.quickbase.com/help/default.html#what_is_a_table.html What is a QuickBase table and record?]<br />
* [http://www.quickbase.com/help/default.html#what_is_a_field.html What is a QuickBase field?]<br />
* [http://www.quickbase.com/help/default.html#what_is_a_view.html What is a QuickBase report?]<br />
<br />
==Tables==<br />
<br />
SAM V1 organizes data into different [[SAM V1:Tables |tables]] that allow you to instantly access, sort, and find information for an individual student or related data sets.<br />
<br />
At the core is the [[SAM V1:Students|Student]] table, however, SAM V1 allows users to manage data for and report on:<br />
<br />
{| width="100%"<br />
|-<br />
|<br />
* [[SAM V1:Disabilities|Disabilities]]<br />
* [[SAM V1:Accommodations|Accommodations]]<br />
* [[SAM V1:Consent Types|Consent Types]]<br />
* [[SAM V1:Referrals|Referrals]]<br />
* [[SAM V1:Case Notes|Case Notes]]<br />
|<br />
* [[SAM V1:Tasks|Tasks]]<br />
* [[SAM V1:Tests|Tests]]<br />
* [[SAM V1:Orders|Alternate Media Orders]]<br />
* [[SAM V1:Class Schedules|Class Schedules]]<br />
* [[SAM V1:Documentation|Documentation]]<br />
|}<br />
<br />
==Access==<br />
<br />
Access to SAM V1 requires a login and password. Each user is provided with their own login and password. A user’s login is their email address. Passwords are case sensitive.<br />
<br />
[https://www.quickbase.com/db/main?a=signin Login to SAM V1]<br />
<br />
==Security==<br />
<br />
Users of SAM V1 benefit from the following [http://quickbase.intuit.com/overview/security/ security] measures provided for all [http://www.quickbase.com QuickBase] applications:<br />
<br />
* An industry-standard, 128-bit Secure Socket Layers (SSL) protocol is employed to ensure information is neither intercepted nor corrupted during transmission over the Internet.<br />
* Encryption technology is used to help protect data stored on disk.<br />
* A state-of-the-art data center provides intrusion detection software and hardware, advanced firewall software, daily back-ups to prevent data loss, video surveillance, and uninterruptible power supplies.<br />
<br />
==Permissions==<br />
<br />
SAM V1 users can access the same data simultaneously. However, using [[SAM_V1:Permissions|roles and permissions]], you can determine what data users can see and what actions users can perform.<br />
<br />
==Reporting==<br />
<br />
With SAM V1, you can quickly and easily find and view your data the way you want. Reporting is simple, with:<br />
<br />
* A host of pre-defined reports to help you get started quickly.<br />
* An easy to use [https://www.quickbase.com/help/default.html#what_is_a_view.html report writer] that allows you to create tabular reports, summary reports, and even graphs and charts.<br />
* A powerful '''Find''' feature that allows you to filter data by multiple fields.<br />
<br />
==Implementation==<br />
<br />
The SAM V1 customer application is created by copying the master SAM QuickBase application. SAM con [[NEON]] is used as the source master when the customer will also be an [[Disability_Professional_Member_Guide|AMAC Member]] and have students in [[NEON]]. SAM sin [[NEON]] is used as the source master when the customer will not have related students in [[NEON]].<br />
<br />
Prior to creating the SAM V1 application for the customer, the customer should complete the [[Media:SAMV1 Implementation Guide w instructions.doc|SAMV1 Implementation Guide w instructions]]. This Microsoft Word document helps the customer identify:<br />
<br />
* How many users will have access<br />
* The name and email address of all users (this information will be used to create the QuickBase logins for users)<br />
* If any new roles and permissions are required in addition to the service provider and administrator roles<br />
* What role to assign to each user<br />
* The multiple-choice field values<br />
* The list of available accommodations<br />
<br />
Completed documents and questions can be emailed to Joe Davis [mailto:davisj@uga.edu davisj@uga.edu]. <br />
<br />
When the SAM V1 customer application is created, [http://www.amac.uga.edu/ AMAC] will use the information provided in the implementation guide to provision users, create any new roles and permissions, and customize the values for multiple-choice fields.<br />
<br />
==Licensing Agreement==<br />
<br />
*[[Media:SAMV1_Services_Agreement.doc|SAM V1 Services Agreement]]<br />
<br />
==Pricing==<br />
<br />
{|width="100%" border="0" cellspacing="0" cellpadding="0" valign="top" <br />
|-<br />
| colspan="2" style="border: 1px solid #cccccc; text-align: left; background: #cedff2; font-weight: bold; color: #000000; padding: 0.2em 0.4em;"|<br />
===Required Costs===<br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Initial Application Fee and Training<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
One Payment of $950, [[Disability_Professional_Member_Guide|AMAC Members]] $750 (Reduced)<br />
*Access to the SAM V1 application.<br />
*Access to the SAM V1 online application documentation. <br />
*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.<br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Hosting/User Fees<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$180/month ($2,160/annually) <br />
*Maximum database size of 5MB <br />
*Maximum file attachment storage of 100MB <br />
*Maximum 10 users <br />
*Users can optionally pay QuickBase for an account and not pay hosting/user fees. QuickBase lowest plan of 5MB database, 100MB file attachment, and 10 users priced at $249/month. See [http://www.quickbase.com www.quickbase.com] for an overview and additional features of having a QuickBase account. <br />
*Covers application hosting, server maintenance, application backup and security, and user maintenance.<br />
|-<br />
| style="border-left: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Support Fee<br />
| style="border-left: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$250/year<br />
*Required the first year of purchase.<br />
*Estimated six hours of support per month.<br />
*Covers application questions and assistance with report creation. <br />
|-<br />
<br />
| colspan="2" style="border: 1px solid #cccccc; text-align: left; background: #cedff2; font-weight: bold; color: #000000; padding: 0.2em 0.4em;"|<br />
<br />
===Optional Costs===<br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Support Fee<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$250/year<br />
*Optional after the first year of purchase.<br />
*Estimated six hours of support per month.<br />
*Covers application questions and assistance with report creation. <br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Customization Fee<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$125/hour <br />
*Covers application customization, import of legacy data, and integration with external systems (i.e. Banner, PeopleSoft).<br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
On-Site Customer Training<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$1,200/day plus travel costs <br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Additional Fees<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
*$50/month per 5MB database storage (if database size exceeds 5MB) <br />
*$100/month per 100MB file attachment storage (if file attachment storage exceeds 100MB) <br />
*$3/month per user (if exceed 10 users)<br />
|}<br />
<br />
==Training==<br />
<br />
*[http://www.amac.uga.edu/presentations/SAM/index.html SAM V1 Training Presentation]<br />
<br />
==Frequently Asked Questions==<br />
<br />
Since SAM V1 is developed using Intuit's [http://www.quickbase.com QuickBase], the application layout, navigation, and functions are controlled by [http://www.quickbase.com QuickBase]. To learn more about a particular topic, choose from the list below:<br />
<br />
* [http://www.quickbase.com/help/default.html#myquickbase.html What is My Quickbase?]<br />
* [http://www.quickbase.com/help/default.html#about_dashboard_page.html What is the application dashboard?]<br />
* [http://www.quickbase.com/help/default.html#adding_or_editing_a_record.html How do I add or edit a record?]<br />
* [http://www.quickbase.com/help/default.html#what_is_a_view.html How do I view records?]<br />
* [http://www.quickbase.com/help/default.html#quick_find.html How do I find records?]<br />
* [http://www.quickbase.com/help/default.html#e-mail_a_record.html How do I email a record?]<br />
* [http://www.quickbase.com/help/default.html#e-mail_a_view.html How do I email a view?]<br />
* [http://www.quickbase.com/help/default.html#importing_data.html How do I import data?]<br />
<br />
[[Category:Disability Service Provider]]<br />
[[Category:Information Technology]]<br />
[[Category:Services]]<br />
[[Category:Software]]<br />
[[Category:Reference]]</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1&diff=4975SAM V12009-06-26T19:22:23Z<p>Ben: </p>
<hr />
<div>{| style="width: 100%; background: #FDF8D6; border: 1px solid #cccccc; text-align: left;"<br />
|-<br />
| style="text-align: left; vertical-align: top; padding: 0.2em 0.4em;"|<br />
[[Image:Database.gif|Database Icon]]&nbsp;&nbsp;<font size="+1">'''Student Accommodation Manager Version 1 (SAM V1)'''</font><br />
<br />
The Student Accommodations Manager Version 1 (SAM V1) is a secure, web-based database application designed to help postsecondary Disability Service Providers manage student data, disabilities, accommodations, case notes, and much more. SAM V1 is developed and hosted using Intuit's [http://www.quickbase.com QuickBase] and follows a [[Wikipedia:Software_as_a_service|software-as-a-service]] model where there is no software to install or server to manage or own. Essential functions such as system availability and backups are provided for you. Predefined reports as well as a powerful report writer allow you to quickly and easily find, filter, and transform data. SAM V1 can also serve as a forms repository and auto-generate accommodation notification letters. For institutions lacking strong IT support, SAM V1 offers a viable multi-user, web-based solution.<br />
<br />
<br />
[[Image:help.gif|Help Icon]]&nbsp;'''Learn More:'''<br />
<br />
*SAM V1 Fact Sheet<br />
*[https://www.quickbase.com/db/bcsnjrd97 SAM V1 Demo Application], for access please contact Joe Davis at 866-279-2964 or [mailto:davisj@uga.edu davisj@uga.edu]<br />
*[[Media:SAMV1vsSAMV2.pdf|Comparison of SAM V1 and SAM V2]]<br />
| align="center" style="width: 20%;"|<br />
__TOC__<br />
|}<br />
<br />
<!-- Do not remove this next line as it inserts spacing between the introduction and the contents --><br />
<div style="height: 5px;">&nbsp;</div><br />
<br />
==Features==<br />
<br />
SAM V1 was developed using Intuit's [http://www.quickbase.com QuickBase] and utilizes standard QuickBase features and [http://quickbase.intuit.com/overview/security/ security], including:<br />
<br />
* Totally web-based<br />
* 24-hour, 365-day availability<br />
* No special software or installations required<br />
* Operational with a screen reader [http://www.amac.uga.edu/samvpat.php VPAT] Voluntary Product Accessibility Template<br />
* Accessible<br />
* Custom, printable reporting<br />
* Email integration<br />
* Searchable on-line help<br />
* Advanced access control via logins, users and roles<br />
* Data encryption<br />
* Daily backups<br />
* Redundant data storage<br />
<br />
==Terminology==<br />
<br />
SAM V1 is a relational database application. An understanding of the following terms and concepts is essential to understanding the SAM V1 design:<br />
<br />
* [[Wikipedia:Application_software|What is an application?]]<br />
* [[Wikipedia:Database|What is a database?]]<br />
* [http://www.quickbase.com/help/default.html#what_is_a_table.html What is a QuickBase table and record?]<br />
* [http://www.quickbase.com/help/default.html#what_is_a_field.html What is a QuickBase field?]<br />
* [http://www.quickbase.com/help/default.html#what_is_a_view.html What is a QuickBase report?]<br />
<br />
==Tables==<br />
<br />
SAM V1 organizes data into different [[SAM V1:Tables |tables]] that allow you to instantly access, sort, and find information for an individual student or related data sets.<br />
<br />
At the core is the [[SAM V1:Students|Student]] table, however, SAM V1 allows users to manage data for and report on:<br />
<br />
{| width="100%"<br />
|-<br />
|<br />
* [[SAM V1:Disabilities|Disabilities]]<br />
* [[SAM V1:Accommodations|Accommodations]]<br />
* [[SAM V1:Consent Types|Consent Types]]<br />
* [[SAM V1:Referrals|Referrals]]<br />
* [[SAM V1:Case Notes|Case Notes]]<br />
|<br />
* [[SAM V1:Tasks|Tasks]]<br />
* [[SAM V1:Tests|Tests]]<br />
* [[SAM V1:Orders|Alternate Media Orders]]<br />
* [[SAM V1:Class Schedules|Class Schedules]]<br />
* [[SAM V1:Documentation|Documentation]]<br />
|}<br />
<br />
==Access==<br />
<br />
Access to SAM V1 requires a login and password. Each user is provided with their own login and password. A user’s login is their email address. Passwords are case sensitive.<br />
<br />
[https://www.quickbase.com/db/main?a=signin Login to SAM V1]<br />
<br />
==Security==<br />
<br />
Users of SAM V1 benefit from the following [http://quickbase.intuit.com/overview/security/ security] measures provided for all [http://www.quickbase.com QuickBase] applications:<br />
<br />
* An industry-standard, 128-bit Secure Socket Layers (SSL) protocol is employed to ensure information is neither intercepted nor corrupted during transmission over the Internet.<br />
* Encryption technology is used to help protect data stored on disk.<br />
* A state-of-the-art data center provides intrusion detection software and hardware, advanced firewall software, daily back-ups to prevent data loss, video surveillance, and uninterruptible power supplies.<br />
<br />
==Permissions==<br />
<br />
SAM V1 users can access the same data simultaneously. However, using [[SAM_V1:Permissions|roles and permissions]], you can determine what data users can see and what actions users can perform.<br />
<br />
==Reporting==<br />
<br />
With SAM V1, you can quickly and easily find and view your data the way you want. Reporting is simple, with:<br />
<br />
* A host of pre-defined reports to help you get started quickly.<br />
* An easy to use [https://www.quickbase.com/help/default.html#what_is_a_view.html report writer] that allows you to create tabular reports, summary reports, and even graphs and charts.<br />
* A powerful '''Find''' feature that allows you to filter data by multiple fields.<br />
<br />
==Implementation==<br />
<br />
The SAM V1 customer application is created by copying the master SAM QuickBase application. SAM con [[NEON]] is used as the source master when the customer will also be an [[Disability_Professional_Member_Guide|AMAC Member]] and have students in [[NEON]]. SAM sin [[NEON]] is used as the source master when the customer will not have related students in [[NEON]].<br />
<br />
Prior to creating the SAM V1 application for the customer, the customer should complete the [[MediaSAMV1 Implementation Guide w instructions.doc|SAMV1 Implementation Guide w instructions]]. This Microsoft Word document helps the customer identify:<br />
<br />
* How many users will have access<br />
* The name and email address of all users (this information will be used to create the QuickBase logins for users)<br />
* If any new roles and permissions are required in addition to the service provider and administrator roles<br />
* What role to assign to each user<br />
* The multiple-choice field values<br />
* The list of available accommodations<br />
<br />
Completed documents and questions can be emailed to Joe Davis [mailto:davisj@uga.edu davisj@uga.edu]. <br />
<br />
When the SAM V1 customer application is created, [http://www.amac.uga.edu/ AMAC] will use the information provided in the implementation guide to provision users, create any new roles and permissions, and customize the values for multiple-choice fields.<br />
<br />
==Licensing Agreement==<br />
<br />
*[[Media:SAMV1_Services_Agreement.doc|SAM V1 Services Agreement]]<br />
<br />
==Pricing==<br />
<br />
{|width="100%" border="0" cellspacing="0" cellpadding="0" valign="top" <br />
|-<br />
| colspan="2" style="border: 1px solid #cccccc; text-align: left; background: #cedff2; font-weight: bold; color: #000000; padding: 0.2em 0.4em;"|<br />
===Required Costs===<br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Initial Application Fee and Training<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
One Payment of $950, [[Disability_Professional_Member_Guide|AMAC Members]] $750 (Reduced)<br />
*Access to the SAM V1 application.<br />
*Access to the SAM V1 online application documentation. <br />
*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.<br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Hosting/User Fees<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$180/month ($2,160/annually) <br />
*Maximum database size of 5MB <br />
*Maximum file attachment storage of 100MB <br />
*Maximum 10 users <br />
*Users can optionally pay QuickBase for an account and not pay hosting/user fees. QuickBase lowest plan of 5MB database, 100MB file attachment, and 10 users priced at $249/month. See [http://www.quickbase.com www.quickbase.com] for an overview and additional features of having a QuickBase account. <br />
*Covers application hosting, server maintenance, application backup and security, and user maintenance.<br />
|-<br />
| style="border-left: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Support Fee<br />
| style="border-left: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$250/year<br />
*Required the first year of purchase.<br />
*Estimated six hours of support per month.<br />
*Covers application questions and assistance with report creation. <br />
|-<br />
<br />
| colspan="2" style="border: 1px solid #cccccc; text-align: left; background: #cedff2; font-weight: bold; color: #000000; padding: 0.2em 0.4em;"|<br />
<br />
===Optional Costs===<br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Support Fee<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$250/year<br />
*Optional after the first year of purchase.<br />
*Estimated six hours of support per month.<br />
*Covers application questions and assistance with report creation. <br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Customization Fee<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$125/hour <br />
*Covers application customization, import of legacy data, and integration with external systems (i.e. Banner, PeopleSoft).<br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
On-Site Customer Training<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$1,200/day plus travel costs <br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Additional Fees<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
*$50/month per 5MB database storage (if database size exceeds 5MB) <br />
*$100/month per 100MB file attachment storage (if file attachment storage exceeds 100MB) <br />
*$3/month per user (if exceed 10 users)<br />
|}<br />
<br />
==Training==<br />
<br />
*[http://www.amac.uga.edu/presentations/SAM/index.html SAM V1 Training Presentation]<br />
<br />
==Frequently Asked Questions==<br />
<br />
Since SAM V1 is developed using Intuit's [http://www.quickbase.com QuickBase], the application layout, navigation, and functions are controlled by [http://www.quickbase.com QuickBase]. To learn more about a particular topic, choose from the list below:<br />
<br />
* [http://www.quickbase.com/help/default.html#myquickbase.html What is My Quickbase?]<br />
* [http://www.quickbase.com/help/default.html#about_dashboard_page.html What is the application dashboard?]<br />
* [http://www.quickbase.com/help/default.html#adding_or_editing_a_record.html How do I add or edit a record?]<br />
* [http://www.quickbase.com/help/default.html#what_is_a_view.html How do I view records?]<br />
* [http://www.quickbase.com/help/default.html#quick_find.html How do I find records?]<br />
* [http://www.quickbase.com/help/default.html#e-mail_a_record.html How do I email a record?]<br />
* [http://www.quickbase.com/help/default.html#e-mail_a_view.html How do I email a view?]<br />
* [http://www.quickbase.com/help/default.html#importing_data.html How do I import data?]<br />
<br />
[[Category:Disability Service Provider]]<br />
[[Category:Information Technology]]<br />
[[Category:Services]]<br />
[[Category:Software]]<br />
[[Category:Reference]]</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=File:SAMV1_Implementation_Guide_w_instructions.doc.doc&diff=4974File:SAMV1 Implementation Guide w instructions.doc.doc2009-06-26T19:20:56Z<p>Ben: </p>
<hr />
<div></div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1&diff=4973SAM V12009-06-26T19:19:40Z<p>Ben: </p>
<hr />
<div>{| style="width: 100%; background: #FDF8D6; border: 1px solid #cccccc; text-align: left;"<br />
|-<br />
| style="text-align: left; vertical-align: top; padding: 0.2em 0.4em;"|<br />
[[Image:Database.gif|Database Icon]]&nbsp;&nbsp;<font size="+1">'''Student Accommodation Manager Version 1 (SAM V1)'''</font><br />
<br />
The Student Accommodations Manager Version 1 (SAM V1) is a secure, web-based database application designed to help postsecondary Disability Service Providers manage student data, disabilities, accommodations, case notes, and much more. SAM V1 is developed and hosted using Intuit's [http://www.quickbase.com QuickBase] and follows a [[Wikipedia:Software_as_a_service|software-as-a-service]] model where there is no software to install or server to manage or own. Essential functions such as system availability and backups are provided for you. Predefined reports as well as a powerful report writer allow you to quickly and easily find, filter, and transform data. SAM V1 can also serve as a forms repository and auto-generate accommodation notification letters. For institutions lacking strong IT support, SAM V1 offers a viable multi-user, web-based solution.<br />
<br />
<br />
[[Image:help.gif|Help Icon]]&nbsp;'''Learn More:'''<br />
<br />
*SAM V1 Fact Sheet<br />
*[https://www.quickbase.com/db/bcsnjrd97 SAM V1 Demo Application], for access please contact Joe Davis at 866-279-2964 or [mailto:davisj@uga.edu davisj@uga.edu]<br />
*[[Media:SAMV1vsSAMV2.pdf|Comparison of SAM V1 and SAM V2]]<br />
| align="center" style="width: 20%;"|<br />
__TOC__<br />
|}<br />
<br />
<!-- Do not remove this next line as it inserts spacing between the introduction and the contents --><br />
<div style="height: 5px;">&nbsp;</div><br />
<br />
==Features==<br />
<br />
SAM V1 was developed using Intuit's [http://www.quickbase.com QuickBase] and utilizes standard QuickBase features and [http://quickbase.intuit.com/overview/security/ security], including:<br />
<br />
* Totally web-based<br />
* 24-hour, 365-day availability<br />
* No special software or installations required<br />
* Operational with a screen reader [http://www.amac.uga.edu/samvpat.php VPAT] Voluntary Product Accessibility Template<br />
* Accessible<br />
* Custom, printable reporting<br />
* Email integration<br />
* Searchable on-line help<br />
* Advanced access control via logins, users and roles<br />
* Data encryption<br />
* Daily backups<br />
* Redundant data storage<br />
<br />
==Terminology==<br />
<br />
SAM V1 is a relational database application. An understanding of the following terms and concepts is essential to understanding the SAM V1 design:<br />
<br />
* [[Wikipedia:Application_software|What is an application?]]<br />
* [[Wikipedia:Database|What is a database?]]<br />
* [http://www.quickbase.com/help/default.html#what_is_a_table.html What is a QuickBase table and record?]<br />
* [http://www.quickbase.com/help/default.html#what_is_a_field.html What is a QuickBase field?]<br />
* [http://www.quickbase.com/help/default.html#what_is_a_view.html What is a QuickBase report?]<br />
<br />
==Tables==<br />
<br />
SAM V1 organizes data into different [[SAM V1:Tables |tables]] that allow you to instantly access, sort, and find information for an individual student or related data sets.<br />
<br />
At the core is the [[SAM V1:Students|Student]] table, however, SAM V1 allows users to manage data for and report on:<br />
<br />
{| width="100%"<br />
|-<br />
|<br />
* [[SAM V1:Disabilities|Disabilities]]<br />
* [[SAM V1:Accommodations|Accommodations]]<br />
* [[SAM V1:Consent Types|Consent Types]]<br />
* [[SAM V1:Referrals|Referrals]]<br />
* [[SAM V1:Case Notes|Case Notes]]<br />
|<br />
* [[SAM V1:Tasks|Tasks]]<br />
* [[SAM V1:Tests|Tests]]<br />
* [[SAM V1:Orders|Alternate Media Orders]]<br />
* [[SAM V1:Class Schedules|Class Schedules]]<br />
* [[SAM V1:Documentation|Documentation]]<br />
|}<br />
<br />
==Access==<br />
<br />
Access to SAM V1 requires a login and password. Each user is provided with their own login and password. A user’s login is their email address. Passwords are case sensitive.<br />
<br />
[https://www.quickbase.com/db/main?a=signin Login to SAM V1]<br />
<br />
==Security==<br />
<br />
Users of SAM V1 benefit from the following [http://quickbase.intuit.com/overview/security/ security] measures provided for all [http://www.quickbase.com QuickBase] applications:<br />
<br />
* An industry-standard, 128-bit Secure Socket Layers (SSL) protocol is employed to ensure information is neither intercepted nor corrupted during transmission over the Internet.<br />
* Encryption technology is used to help protect data stored on disk.<br />
* A state-of-the-art data center provides intrusion detection software and hardware, advanced firewall software, daily back-ups to prevent data loss, video surveillance, and uninterruptible power supplies.<br />
<br />
==Permissions==<br />
<br />
SAM V1 users can access the same data simultaneously. However, using [[SAM_V1:Permissions|roles and permissions]], you can determine what data users can see and what actions users can perform.<br />
<br />
==Reporting==<br />
<br />
With SAM V1, you can quickly and easily find and view your data the way you want. Reporting is simple, with:<br />
<br />
* A host of pre-defined reports to help you get started quickly.<br />
* An easy to use [https://www.quickbase.com/help/default.html#what_is_a_view.html report writer] that allows you to create tabular reports, summary reports, and even graphs and charts.<br />
* A powerful '''Find''' feature that allows you to filter data by multiple fields.<br />
<br />
==Implementation==<br />
<br />
The SAM V1 customer application is created by copying the master SAM QuickBase application. SAM con [[NEON]] is used as the source master when the customer will also be an [[Disability_Professional_Member_Guide|AMAC Member]] and have students in [[NEON]]. SAM sin [[NEON]] is used as the source master when the customer will not have related students in [[NEON]].<br />
<br />
Prior to creating the SAM V1 application for the customer, the customer should complete the [[Media:.doc|SAM V1 implementation guide]]. This Microsoft Word document helps the customer identify:<br />
<br />
* How many users will have access<br />
* The name and email address of all users (this information will be used to create the QuickBase logins for users)<br />
* If any new roles and permissions are required in addition to the service provider and administrator roles<br />
* What role to assign to each user<br />
* The multiple-choice field values<br />
* The list of available accommodations<br />
<br />
Completed documents and questions can be emailed to Joe Davis [mailto:davisj@uga.edu davisj@uga.edu]. <br />
<br />
When the SAM V1 customer application is created, [http://www.amac.uga.edu/ AMAC] will use the information provided in the implementation guide to provision users, create any new roles and permissions, and customize the values for multiple-choice fields.<br />
<br />
==Licensing Agreement==<br />
<br />
*[[Media:SAMV1_Services_Agreement.doc|SAM V1 Services Agreement]]<br />
<br />
==Pricing==<br />
<br />
{|width="100%" border="0" cellspacing="0" cellpadding="0" valign="top" <br />
|-<br />
| colspan="2" style="border: 1px solid #cccccc; text-align: left; background: #cedff2; font-weight: bold; color: #000000; padding: 0.2em 0.4em;"|<br />
===Required Costs===<br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Initial Application Fee and Training<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
One Payment of $950, [[Disability_Professional_Member_Guide|AMAC Members]] $750 (Reduced)<br />
*Access to the SAM V1 application.<br />
*Access to the SAM V1 online application documentation. <br />
*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.<br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Hosting/User Fees<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$180/month ($2,160/annually) <br />
*Maximum database size of 5MB <br />
*Maximum file attachment storage of 100MB <br />
*Maximum 10 users <br />
*Users can optionally pay QuickBase for an account and not pay hosting/user fees. QuickBase lowest plan of 5MB database, 100MB file attachment, and 10 users priced at $249/month. See [http://www.quickbase.com www.quickbase.com] for an overview and additional features of having a QuickBase account. <br />
*Covers application hosting, server maintenance, application backup and security, and user maintenance.<br />
|-<br />
| style="border-left: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Support Fee<br />
| style="border-left: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$250/year<br />
*Required the first year of purchase.<br />
*Estimated six hours of support per month.<br />
*Covers application questions and assistance with report creation. <br />
|-<br />
<br />
| colspan="2" style="border: 1px solid #cccccc; text-align: left; background: #cedff2; font-weight: bold; color: #000000; padding: 0.2em 0.4em;"|<br />
<br />
===Optional Costs===<br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Support Fee<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$250/year<br />
*Optional after the first year of purchase.<br />
*Estimated six hours of support per month.<br />
*Covers application questions and assistance with report creation. <br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Customization Fee<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$125/hour <br />
*Covers application customization, import of legacy data, and integration with external systems (i.e. Banner, PeopleSoft).<br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
On-Site Customer Training<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$1,200/day plus travel costs <br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Additional Fees<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
*$50/month per 5MB database storage (if database size exceeds 5MB) <br />
*$100/month per 100MB file attachment storage (if file attachment storage exceeds 100MB) <br />
*$3/month per user (if exceed 10 users)<br />
|}<br />
<br />
==Training==<br />
<br />
*[http://www.amac.uga.edu/presentations/SAM/index.html SAM V1 Training Presentation]<br />
<br />
==Frequently Asked Questions==<br />
<br />
Since SAM V1 is developed using Intuit's [http://www.quickbase.com QuickBase], the application layout, navigation, and functions are controlled by [http://www.quickbase.com QuickBase]. To learn more about a particular topic, choose from the list below:<br />
<br />
* [http://www.quickbase.com/help/default.html#myquickbase.html What is My Quickbase?]<br />
* [http://www.quickbase.com/help/default.html#about_dashboard_page.html What is the application dashboard?]<br />
* [http://www.quickbase.com/help/default.html#adding_or_editing_a_record.html How do I add or edit a record?]<br />
* [http://www.quickbase.com/help/default.html#what_is_a_view.html How do I view records?]<br />
* [http://www.quickbase.com/help/default.html#quick_find.html How do I find records?]<br />
* [http://www.quickbase.com/help/default.html#e-mail_a_record.html How do I email a record?]<br />
* [http://www.quickbase.com/help/default.html#e-mail_a_view.html How do I email a view?]<br />
* [http://www.quickbase.com/help/default.html#importing_data.html How do I import data?]<br />
<br />
[[Category:Disability Service Provider]]<br />
[[Category:Information Technology]]<br />
[[Category:Services]]<br />
[[Category:Software]]<br />
[[Category:Reference]]</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=File:SAMV1_Implementation_Guide_w_instructions.doc&diff=4972File:SAMV1 Implementation Guide w instructions.doc2009-06-26T19:18:14Z<p>Ben: </p>
<hr />
<div></div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1&diff=4971SAM V12009-06-26T19:08:07Z<p>Ben: </p>
<hr />
<div>{| style="width: 100%; background: #FDF8D6; border: 1px solid #cccccc; text-align: left;"<br />
|-<br />
| style="text-align: left; vertical-align: top; padding: 0.2em 0.4em;"|<br />
[[Image:Database.gif|Database Icon]]&nbsp;&nbsp;<font size="+1">'''Student Accommodation Manager Version 1 (SAM V1)'''</font><br />
<br />
The Student Accommodations Manager Version 1 (SAM V1) is a secure, web-based database application designed to help postsecondary Disability Service Providers manage student data, disabilities, accommodations, case notes, and much more. SAM V1 is developed and hosted using Intuit's [http://www.quickbase.com QuickBase] and follows a [[Wikipedia:Software_as_a_service|software-as-a-service]] model where there is no software to install or server to manage or own. Essential functions such as system availability and backups are provided for you. Predefined reports as well as a powerful report writer allow you to quickly and easily find, filter, and transform data. SAM V1 can also serve as a forms repository and auto-generate accommodation notification letters. For institutions lacking strong IT support, SAM V1 offers a viable multi-user, web-based solution.<br />
<br />
<br />
[[Image:help.gif|Help Icon]]&nbsp;'''Learn More:'''<br />
<br />
*SAM V1 Fact Sheet<br />
*[https://www.quickbase.com/db/bcsnjrd97 SAM V1 Demo Application], for access please contact Joe Davis at 866-279-2964 or [mailto:davisj@uga.edu davisj@uga.edu]<br />
*[[Media:SAMV1vsSAMV2.pdf|Comparison of SAM V1 and SAM V2]]<br />
| align="center" style="width: 20%;"|<br />
__TOC__<br />
|}<br />
<br />
<!-- Do not remove this next line as it inserts spacing between the introduction and the contents --><br />
<div style="height: 5px;">&nbsp;</div><br />
<br />
==Features==<br />
<br />
SAM V1 was developed using Intuit's [http://www.quickbase.com QuickBase] and utilizes standard QuickBase features and [http://quickbase.intuit.com/overview/security/ security], including:<br />
<br />
* Totally web-based<br />
* 24-hour, 365-day availability<br />
* No special software or installations required<br />
* Operational with a screen reader [http://www.amac.uga.edu/samvpat.php VPAT] Voluntary Product Accessibility Template<br />
* Accessible<br />
* Custom, printable reporting<br />
* Email integration<br />
* Searchable on-line help<br />
* Advanced access control via logins, users and roles<br />
* Data encryption<br />
* Daily backups<br />
* Redundant data storage<br />
<br />
==Terminology==<br />
<br />
SAM V1 is a relational database application. An understanding of the following terms and concepts is essential to understanding the SAM V1 design:<br />
<br />
* [[Wikipedia:Application_software|What is an application?]]<br />
* [[Wikipedia:Database|What is a database?]]<br />
* [http://www.quickbase.com/help/default.html#what_is_a_table.html What is a QuickBase table and record?]<br />
* [http://www.quickbase.com/help/default.html#what_is_a_field.html What is a QuickBase field?]<br />
* [http://www.quickbase.com/help/default.html#what_is_a_view.html What is a QuickBase report?]<br />
<br />
==Tables==<br />
<br />
SAM V1 organizes data into different [[SAM V1:Tables |tables]] that allow you to instantly access, sort, and find information for an individual student or related data sets.<br />
<br />
At the core is the [[SAM V1:Students|Student]] table, however, SAM V1 allows users to manage data for and report on:<br />
<br />
{| width="100%"<br />
|-<br />
|<br />
* [[SAM V1:Disabilities|Disabilities]]<br />
* [[SAM V1:Accommodations|Accommodations]]<br />
* [[SAM V1:Consent Types|Consent Types]]<br />
* [[SAM V1:Referrals|Referrals]]<br />
* [[SAM V1:Case Notes|Case Notes]]<br />
|<br />
* [[SAM V1:Tasks|Tasks]]<br />
* [[SAM V1:Tests|Tests]]<br />
* [[SAM V1:Orders|Alternate Media Orders]]<br />
* [[SAM V1:Class Schedules|Class Schedules]]<br />
* [[SAM V1:Documentation|Documentation]]<br />
|}<br />
<br />
==Access==<br />
<br />
Access to SAM V1 requires a login and password. Each user is provided with their own login and password. A user’s login is their email address. Passwords are case sensitive.<br />
<br />
[https://www.quickbase.com/db/main?a=signin Login to SAM V1]<br />
<br />
==Security==<br />
<br />
Users of SAM V1 benefit from the following [http://quickbase.intuit.com/overview/security/ security] measures provided for all [http://www.quickbase.com QuickBase] applications:<br />
<br />
* An industry-standard, 128-bit Secure Socket Layers (SSL) protocol is employed to ensure information is neither intercepted nor corrupted during transmission over the Internet.<br />
* Encryption technology is used to help protect data stored on disk.<br />
* A state-of-the-art data center provides intrusion detection software and hardware, advanced firewall software, daily back-ups to prevent data loss, video surveillance, and uninterruptible power supplies.<br />
<br />
==Permissions==<br />
<br />
SAM V1 users can access the same data simultaneously. However, using [[SAM_V1:Permissions|roles and permissions]], you can determine what data users can see and what actions users can perform.<br />
<br />
==Reporting==<br />
<br />
With SAM V1, you can quickly and easily find and view your data the way you want. Reporting is simple, with:<br />
<br />
* A host of pre-defined reports to help you get started quickly.<br />
* An easy to use [https://www.quickbase.com/help/default.html#what_is_a_view.html report writer] that allows you to create tabular reports, summary reports, and even graphs and charts.<br />
* A powerful '''Find''' feature that allows you to filter data by multiple fields.<br />
<br />
==Implementation==<br />
<br />
The SAM V1 customer application is created by copying the master SAM QuickBase application. SAM con [[NEON]] is used as the source master when the customer will also be an [[Disability_Professional_Member_Guide|AMAC Member]] and have students in [[NEON]]. SAM sin [[NEON]] is used as the source master when the customer will not have related students in [[NEON]].<br />
<br />
Prior to creating the SAM V1 application for the customer, the customer should complete the [[Media:SAMV1 Implementation Guide w instructions.doc|SAM V1 implementation guide]]. This Microsoft Word document helps the customer identify:<br />
<br />
* How many users will have access<br />
* The name and email address of all users (this information will be used to create the QuickBase logins for users)<br />
* If any new roles and permissions are required in addition to the service provider and administrator roles<br />
* What role to assign to each user<br />
* The multiple-choice field values<br />
* The list of available accommodations<br />
<br />
Completed documents and questions can be emailed to Joe Davis [mailto:davisj@uga.edu davisj@uga.edu]. <br />
<br />
When the SAM V1 customer application is created, [http://www.amac.uga.edu/ AMAC] will use the information provided in the implementation guide to provision users, create any new roles and permissions, and customize the values for multiple-choice fields.<br />
<br />
==Licensing Agreement==<br />
<br />
*[[Media:SAMV1_Services_Agreement.doc|SAM V1 Services Agreement]]<br />
<br />
==Pricing==<br />
<br />
{|width="100%" border="0" cellspacing="0" cellpadding="0" valign="top" <br />
|-<br />
| colspan="2" style="border: 1px solid #cccccc; text-align: left; background: #cedff2; font-weight: bold; color: #000000; padding: 0.2em 0.4em;"|<br />
===Required Costs===<br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Initial Application Fee and Training<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
One Payment of $950, [[Disability_Professional_Member_Guide|AMAC Members]] $750 (Reduced)<br />
*Access to the SAM V1 application.<br />
*Access to the SAM V1 online application documentation. <br />
*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.<br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Hosting/User Fees<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$180/month ($2,160/annually) <br />
*Maximum database size of 5MB <br />
*Maximum file attachment storage of 100MB <br />
*Maximum 10 users <br />
*Users can optionally pay QuickBase for an account and not pay hosting/user fees. QuickBase lowest plan of 5MB database, 100MB file attachment, and 10 users priced at $249/month. See [http://www.quickbase.com www.quickbase.com] for an overview and additional features of having a QuickBase account. <br />
*Covers application hosting, server maintenance, application backup and security, and user maintenance.<br />
|-<br />
| style="border-left: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Support Fee<br />
| style="border-left: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$250/year<br />
*Required the first year of purchase.<br />
*Estimated six hours of support per month.<br />
*Covers application questions and assistance with report creation. <br />
|-<br />
<br />
| colspan="2" style="border: 1px solid #cccccc; text-align: left; background: #cedff2; font-weight: bold; color: #000000; padding: 0.2em 0.4em;"|<br />
<br />
===Optional Costs===<br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Support Fee<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$250/year<br />
*Optional after the first year of purchase.<br />
*Estimated six hours of support per month.<br />
*Covers application questions and assistance with report creation. <br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Customization Fee<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$125/hour <br />
*Covers application customization, import of legacy data, and integration with external systems (i.e. Banner, PeopleSoft).<br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
On-Site Customer Training<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$1,200/day plus travel costs <br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Additional Fees<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
*$50/month per 5MB database storage (if database size exceeds 5MB) <br />
*$100/month per 100MB file attachment storage (if file attachment storage exceeds 100MB) <br />
*$3/month per user (if exceed 10 users)<br />
|}<br />
<br />
==Training==<br />
<br />
*[http://www.amac.uga.edu/presentations/SAM/index.html SAM V1 Training Presentation]<br />
<br />
==Frequently Asked Questions==<br />
<br />
Since SAM V1 is developed using Intuit's [http://www.quickbase.com QuickBase], the application layout, navigation, and functions are controlled by [http://www.quickbase.com QuickBase]. To learn more about a particular topic, choose from the list below:<br />
<br />
* [http://www.quickbase.com/help/default.html#myquickbase.html What is My Quickbase?]<br />
* [http://www.quickbase.com/help/default.html#about_dashboard_page.html What is the application dashboard?]<br />
* [http://www.quickbase.com/help/default.html#adding_or_editing_a_record.html How do I add or edit a record?]<br />
* [http://www.quickbase.com/help/default.html#what_is_a_view.html How do I view records?]<br />
* [http://www.quickbase.com/help/default.html#quick_find.html How do I find records?]<br />
* [http://www.quickbase.com/help/default.html#e-mail_a_record.html How do I email a record?]<br />
* [http://www.quickbase.com/help/default.html#e-mail_a_view.html How do I email a view?]<br />
* [http://www.quickbase.com/help/default.html#importing_data.html How do I import data?]<br />
<br />
[[Category:Disability Service Provider]]<br />
[[Category:Information Technology]]<br />
[[Category:Services]]<br />
[[Category:Software]]<br />
[[Category:Reference]]</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:Students&diff=4967SAM V1:Students2009-06-25T18:12:45Z<p>Ben: </p>
<hr />
<div>The student table contains information about the students that receive disability services. A student record is created one time only. The student record is considered the master or parent record. The disabilities, accommodations, consent types, referrals, case notes, tasks, test scores, and class schedules are sub-tables or child records of the student record. The relationship is many children to one parent. In other words, the student record has many disabilities, accommodations, or case notes records related to it.<br />
<br />
The student record should not be deleted without first deleting all the child records related to it. Otherwise, the child records would be orphaned. <br />
<br />
[[SAM V1#Tables|Back to SAM V1 Tables]]<br />
<br />
==Status==<br />
<br />
The status field can be the value active, inactive, or prospective. It is used to determine if the student is using disability services.<br />
<br />
The status field can be reset to inactive for all students at the beginning of each term. Then, as service providers work with students, the status field would be changed to active. By doing so, it would be possible to determine which students are active for the current term. <br />
<br />
==Fields==<br />
<br />
The fields of the students table are:<br />
<br />
{| border="1" cellspacing="1" cellpadding="1"<br />
!Field<br />
!Description<br />
|-<br />
|Date Created <br />
|Date record was created.<br />
|-<br />
|Date Modified <br />
|Date record was last updated.<br />
|-<br />
|Student ID# <br />
|Unique ID# of the record.<br />
|-<br />
|Record Owner <br />
|User who owns the record.<br />
|-<br />
|Last Modified By <br />
|User who last modified the record.<br />
|-<br />
|Academic Level <br />
|Academic Level of student: Freshman, Sophomore, Junior, Senior, Graduate, etc.<br />
|-<br />
|Address <br />
|Address of student. Format is address, city, state and zip code.<br />
|-<br />
|Alternate Address <br />
|Alternate address of student. Format is address, city, state and zip code.<br />
|-<br />
|Alternate Email <br />
|Alternative email address of student.<br />
|-<br />
|Alternate Phone <br />
|Alternate phone number of student.<br />
|-<br />
|Alternate Phone Type <br />
|Type of alternative phone number: Home, Cell, Fax, etc.<br />
|-<br />
|Campus <br />
|The primary campus the student attends.<br />
|-<br />
|Date of Birth <br />
|Date of birth of student.<br />
|-<br />
|Email <br />
|Email address of student.<br />
|-<br />
|Enrollment <br />
|Enrollment status of the student: Enrolled, Graduated, Transferred, Withdrawn, etc.<br />
|-<br />
|Ethnicity <br />
|Ethnicity of student: Caucasian, African American, Hispanic, etc.<br />
|-<br />
|First Name <br />
|First name of student. First Name is required.<br />
|-<br />
|Gender <br />
|Gender of student: Male, Female, etc.<br />
|-<br />
|ID <br />
|Unique student identifier. This field could contain university identification number, social security number, or something similar. ID is required.<br />
|-<br />
|Last Name <br />
|Last name of student. Last Name is required.<br />
|-<br />
|Middle Name <br />
|Middle name of student.<br />
|-<br />
|Name <br />
|Formula field that is the concatenation of Last Name, First Name and Middle Name.<br />
|-<br />
|NEON Student <br />
|The NEON student that corresponds to the SAM student. A SAM student is created in NEON if the SAM student receives AMAC services.<br />
|-<br />
|NEON Student Data Out of Synch <br />
|Checkbox that is checked if the student data in NEON does not match the student data in SAM. SAM is considered the authoritative source. SAM and NEON student data must be kept in synch manually.<br />
|-<br />
|Notes <br />
|Notes regarding the student. The notes field is a cumulative field and date stamped with the date, time and user adding the notes.<br />
|-<br />
|Phone <br />
|Phone number of student.<br />
|-<br />
|Phone Type <br />
|Type of phone number: Home, Cell, Fax, etc.<br />
|-<br />
|Preferred Name <br />
|The name the student prefers to go by.<br />
|-<br />
|Print Accommodation Notification <br />
|Use this link to print the general accommodation notification letter for the student. The general accommodation notification letter does not include the instructor and course name.<br />
|-<br />
|Service Provider <br />
|The service provider assigned to the student.<br />
|-<br />
|Status <br />
|Student status: Active, Inactive, Prospective. Status is required. The default value is Active.<br />
|-<br />
|US Citizen <br />
|Checkbox to be checked if student is a citizen of the USA.<br />
|-<br />
|Why NEON Student Data Out of Synch <br />
|A list of fields where the SAM student data does not match the NEON student data. Identifies which fields needs to be addressed in order for SAM and NEON student data to match.<br />
|}<br />
<br />
=='''Banner'''== <br />
<br />
How to [[SAM V1:import|import]] information into SAMV1.<br />
<br />
=='''PeopleSoft'''==<br />
<br />
To synchronize PeopleSoft data with SAM data, you will perform an [http://www.quickbase.com/help/default.html#importing_data.html import data] of a flat .txt or .csv file into SAM. The flat file is essentially the data file provided by PeopleSoft, but with an additional column pre-pended to each row that uniquely identifies the student record in SAM. The additional column is the unique SAM key field Student ID#. <br />
<br />
Either the Microsoft Access application ps2sam.mdb or the PeopleSoft to SAM Web Conversion Utility can be used to append the Student ID# to the PeopleSoft data file. <br />
<br />
With the addition of the Student ID# column, the import of data into SAM then becomes an update import and updates records in SAM rather than creating new records. If the Student ID# value in the data file row exists within SAM, then the imported row of data updates the existing record in SAM. If the Student ID# value in the data file row does not exist within SAM, then the imported row of data creates a new student record in SAM during the import.<br />
Source Data<br />
<br />
===Source Data===<br />
<br />
====<u>PeopleSoft</u>====<br />
<br />
The data file received from PeopleSoft is a Microsoft Excel file consisting of a row for each student.<br />
<br />
====<u>SAM</u>====<br />
<br />
In SAM, the structure of the student table contains most of the fields referenced in the PeopleSoft file, plus many more. There are fields for Student ID, First Name, Last Name, Address1, Address2, City, State, Zip Code, Email, Phone Number, Academic Level, and Business Plan. However, Student ID is not the key field in SAM. Instead, SAM contains a unique key field on each student record called Student ID#. It is an auto-assigned integer value that is meaningless other than uniquely identifying the student record. To locate or update a student record in SAM, you use the Student ID#.<br />
<br />
====<u>Mapping</u>====<br />
<br />
{| class="wikitable" border="1"<br />
|- <br />
! PeopleSoft File Column !! SAM Student Table field !! Notes<br />
|-<br />
| Student Group Effective Date || &nbsp; || &nbsp;<br />
|-<br />
| Student Group Status || Status || A = ACTIVE, I = INACTIVE<br />
|-<br />
| PeopleSoft ID || Student ID || &nbsp;<br />
|-<br />
| Last Name || Last Name || &nbsp;<br />
|-<br />
| First Name || First Name || &nbsp;<br />
|-<br />
| Middle Name || Middle Name || &nbsp;<br />
|-<br />
| Address || Address1 || &nbsp;<br />
|-<br />
| City || City || &nbsp;<br />
|-<br />
| State || State || &nbsp;<br />
|-<br />
| Postal Code || Zip || &nbsp; <br />
|-<br />
| Preferred Phone Number || Phone || Formatting removed<br />
|-<br />
| Alternate Phone Number || Alternate Phone || Formatting removed<br />
|-<br />
| Alternate Phone Type || Alternate Phone Type || &nbsp;<br />
|-<br />
| Email || Email || &nbsp;<br />
|-<br />
| Ethnic Grp || Ethnicity || &nbsp;<br />
|-<br />
| Gender || Gender || M = MALE, F = FEMALE<br />
|-<br />
| DOB || Date of Birth || &nbsp; <br />
|-<br />
| Cum GPA || &nbsp; || &nbsp;<br />
|-<br />
| Academic Level || Academic Level || &nbsp;<br />
|-<br />
| Plan Code || Business Plan || &nbsp;<br />
|-<br />
| ERRS DSSVD Code || ERSS – D Code || &nbsp;<br />
|-<br />
| ERRS DSSPS Code || ERSS – A Code || &nbsp;<br />
|}<br />
<br />
===Building the SAM Import File using Microsoft Access===<br />
<br />
A Microsoft Access application can be used to compare the PeopleSoft and SAM Student files and generate a flat .txt file that can be imported into SAM.<br />
<br />
Using the Microsoft Access application assumes the following:<br />
<br />
# The PeopleSoft data file will not contain the SAM Student ID#.<br />
# You are manually maintaining the Student ID in SAM.<br />
# If there is not a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will be inserted to SAM.<br />
# If there is a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will update the SAM row.<br />
<br />
The Access application contains the following objects:<br />
<br />
Tables:<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
| PeopleSoft || A link table to the PeopleSoft flat file.<br />
|-<br />
| Students || A link table to the SAM export student table flat file.<br />
|}<br />
<br />
You want your tables to be link tables so that all you need to do is replace the underlying files to refresh the table data.<br />
<br />
Queries:<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
|Matched Query || A query that joins PeopleSoft to SAM using Student ID that selects all PeopleSoft rows and only the SAM rows where there is a match. The output columns are the SAM Student ID# and the columns from the PeopleSoft file that map to the columns in the SAM student table. The status column is changed from A or I to ACTIVE or INACTIVE. The phone number columns have formatting removed. The gender column is changed from M or F to MALE or FEMALE. These are the rows that need to be updated or imported in SAM using the PeopleSoft data.<br />
|}<br />
<br />
Macros:<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
| Matched Query Export || A macro that runs and exports the match query.<br />
|}<br />
<br />
====<u>Process</u>====<br />
<br />
The following process assumes the following:<br />
<br />
* The PeopleSoft file is called peoplesoft.xls.<br />
* The SAM student export is called Students.txt.<br />
* The Microsoft Access application is called ps2sam.mdb.<br />
* The match query output file is called Matched Query.xls.<br />
* The files and Microsoft Access application reside in folder called peoplesoft.<br />
<br />
=====<u>Step 1</u>=====<br />
<br />
# Open the PeopleSoft file peoplesoft.xls in the folder peoplesoft.<br />
# In SAM application, use Customize, Import/Export, and export the student table as a tab-delimited file called Students.txt in the folder peoplesoft. Note that you must change the file extension from tsv to txt.<br />
<br />
=====<u>Step 2</u>=====<br />
<br />
# Open ps2sam.mdb<br />
# Run macro Matched Query Export<br />
# Save file in folder peoplesoft and call file Matched Query.xls.<br />
# Quit ps2sam.mdb<br />
<br />
=====<u>Step 3</u>=====<br />
<br />
# Open the file Matched Query.xls.<br />
# Review the file and ensure that a pending student does not already exist in SAM with a blank or different Student ID. Perhaps the student is listed in SAM with the student ID of lastname + firstname but in the PeopleSoft file their 9 digit ID number is listed. <br />
# If the student is already in SAM, you need to update the SAM Student ID and start over at step 1. If not, a duplicate SAM student record will be created if you import the query file.<br />
# Save the Matched Query.xls file as a tab delimited .txt format file. This is necessary because QuickBase cannot import an Excel file but can import a tab delimited text file.<br />
<br />
=====<u>Step 4</u>=====<br />
<br />
# In SAM application, use Customize, Import/Export, and import into the student table the Matched Query.txt file. Check the box that states the first row is a list of field names. The import should state that the import is an update import. Be careful to review the fields that the data will import into and ensure that the columns are in the correct order. Student ID# should be the first columns followed by the columns in this order: Status, Student ID, Last Name, First Name, Middle Name, Address1, City, State, Zip, Phone, Alternate Phone, Alternate Phone Type, Email, Ethnicity, Gender, Date of Birth, Academic Level, Business Plan, ERRS – D Code, ERRS – A Code.<br />
# You are not required to import all columns, but you must select to import the Student ID#. This import will update SAM student records with the PeopleSoft data.<br />
<br />
===Building the SAM Import File using the Web Utility===<br />
<br />
A web utility can be used to compare the PeopleSoft and SAM Student files and generate a flat .csv file that can be imported into SAM.<br />
<br />
The web utility assumes the following:<br />
<br />
# The PeopleSoft data file will not contain the SAM Student ID#.<br />
# You are manually maintaining the Student ID in SAM.<br />
# If there is not a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will be inserted to SAM.<br />
# If there is a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will update the SAM row.<br />
<br />
====<u>Process</u>====<br />
<br />
The following process assumes the following:<br />
<br />
* The PeopleSoft file is called peoplesoft.xls.<br />
<br />
=====<u>Step 1</u>=====<br />
<br />
# Save the PeopleSoft file peoplesoft.xls as a CSV file named peoplesoft.csv.<br />
<br />
=====<u>Step 2</u>=====<br />
<br />
# Log into the SAM application.<br />
# On the dashboard, in the toolbox, click on the PeopleSoft to SAM Conversion Utility link.<br />
<br />
=====<u>Step 3</u>=====<br />
<br />
# Attach the peoplesoft.csv file.<br />
# Select the option that you want to create a file to be imported into SAM that will update existing SAM student data as well as create new students not currently in SAM but listed in PeopleSoft.<br />
# Click the submit button. <br />
# Save the file studentimport.csv to your computer.<br />
<br />
=====<u>Step 4</u>=====<br />
<br />
# In SAM application, use Customize, Import/Export, and import into the student table the studentimport.csv file. Check the box that states the first row is a list of field names. The import should state that the import is an update import. Be careful to review the fields that the data will import into and ensure that the columns are in the correct order. Student ID# should be the first columns followed by the columns in this order: Status, Student ID, Last Name, First Name, Middle Name, Address1, City, State, Zip, Phone, Alternate Phone, Alternate Phone Type, Email, Ethnicity, Gender, Date of Birth, Academic Level, Business Plan, ERRS – D Code, ERRS – A Code.<br />
# You are not required to import all columns, but you must select to import the Student ID#. This import will update SAM student records with the PeopleSoft data.<br />
<br />
===Further Reading===<br />
<br />
[http://www.quickbase.com/help/default.html#importing_data.html Import Data from Outside QuickBase]</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:Students&diff=4966SAM V1:Students2009-06-25T18:11:04Z<p>Ben: </p>
<hr />
<div>The student table contains information about the students that receive disability services. A student record is created one time only. The student record is considered the master or parent record. The disabilities, accommodations, consent types, referrals, case notes, tasks, test scores, and class schedules are sub-tables or child records of the student record. The relationship is many children to one parent. In other words, the student record has many disabilities, accommodations, or case notes records related to it.<br />
<br />
The student record should not be deleted without first deleting all the child records related to it. Otherwise, the child records would be orphaned. <br />
<br />
[[SAM V1#Tables|Back to SAM V1 Tables]]<br />
<br />
==Status==<br />
<br />
The status field can be the value active, inactive, or prospective. It is used to determine if the student is using disability services.<br />
<br />
The status field can be reset to inactive for all students at the beginning of each term. Then, as service providers work with students, the status field would be changed to active. By doing so, it would be possible to determine which students are active for the current term. <br />
<br />
==Fields==<br />
<br />
The fields of the students table are:<br />
<br />
{| border="1" cellspacing="1" cellpadding="1"<br />
!Field<br />
!Description<br />
|-<br />
|Date Created <br />
|Date record was created.<br />
|-<br />
|Date Modified <br />
|Date record was last updated.<br />
|-<br />
|Student ID# <br />
|Unique ID# of the record.<br />
|-<br />
|Record Owner <br />
|User who owns the record.<br />
|-<br />
|Last Modified By <br />
|User who last modified the record.<br />
|-<br />
|Academic Level <br />
|Academic Level of student: Freshman, Sophomore, Junior, Senior, Graduate, etc.<br />
|-<br />
|Address <br />
|Address of student. Format is address, city, state and zip code.<br />
|-<br />
|Alternate Address <br />
|Alternate address of student. Format is address, city, state and zip code.<br />
|-<br />
|Alternate Email <br />
|Alternative email address of student.<br />
|-<br />
|Alternate Phone <br />
|Alternate phone number of student.<br />
|-<br />
|Alternate Phone Type <br />
|Type of alternative phone number: Home, Cell, Fax, etc.<br />
|-<br />
|Campus <br />
|The primary campus the student attends.<br />
|-<br />
|Date of Birth <br />
|Date of birth of student.<br />
|-<br />
|Email <br />
|Email address of student.<br />
|-<br />
|Enrollment <br />
|Enrollment status of the student: Enrolled, Graduated, Transferred, Withdrawn, etc.<br />
|-<br />
|Ethnicity <br />
|Ethnicity of student: Caucasian, African American, Hispanic, etc.<br />
|-<br />
|First Name <br />
|First name of student. First Name is required.<br />
|-<br />
|Gender <br />
|Gender of student: Male, Female, etc.<br />
|-<br />
|ID <br />
|Unique student identifier. This field could contain university identification number, social security number, or something similar. ID is required.<br />
|-<br />
|Last Name <br />
|Last name of student. Last Name is required.<br />
|-<br />
|Middle Name <br />
|Middle name of student.<br />
|-<br />
|Name <br />
|Formula field that is the concatenation of Last Name, First Name and Middle Name.<br />
|-<br />
|NEON Student <br />
|The NEON student that corresponds to the SAM student. A SAM student is created in NEON if the SAM student receives AMAC services.<br />
|-<br />
|NEON Student Data Out of Synch <br />
|Checkbox that is checked if the student data in NEON does not match the student data in SAM. SAM is considered the authoritative source. SAM and NEON student data must be kept in synch manually.<br />
|-<br />
|Notes <br />
|Notes regarding the student. The notes field is a cumulative field and date stamped with the date, time and user adding the notes.<br />
|-<br />
|Phone <br />
|Phone number of student.<br />
|-<br />
|Phone Type <br />
|Type of phone number: Home, Cell, Fax, etc.<br />
|-<br />
|Preferred Name <br />
|The name the student prefers to go by.<br />
|-<br />
|Print Accommodation Notification <br />
|Use this link to print the general accommodation notification letter for the student. The general accommodation notification letter does not include the instructor and course name.<br />
|-<br />
|Service Provider <br />
|The service provider assigned to the student.<br />
|-<br />
|Status <br />
|Student status: Active, Inactive, Prospective. Status is required. The default value is Active.<br />
|-<br />
|US Citizen <br />
|Checkbox to be checked if student is a citizen of the USA.<br />
|-<br />
|Why NEON Student Data Out of Synch <br />
|A list of fields where the SAM student data does not match the NEON student data. Identifies which fields needs to be addressed in order for SAM and NEON student data to match.<br />
|}<br />
<br />
=='''Banner'''== <br />
<br />
How to [[SAM V1:import|import]] information into SAMV1.<br />
<br />
=='''PeopleSoft'''==<br />
<br />
To synchronize PeopleSoft data with SAM data, you will perform an [http://www.quickbase.com/help/default.html#importing_data.html import data] of a flat .txt or .csv file into SAM. The flat file is essentially the data file provided by PeopleSoft, but with an additional column pre-pended to each row that uniquely identifies the student record in SAM. The additional column is the unique SAM key field Student ID#. <br />
<br />
Either the Microsoft Access application ps2sam.mdb or the PeopleSoft to SAM Web Conversion Utility can be used to append the Student ID# to the PeopleSoft data file. <br />
<br />
With the addition of the Student ID# column, the import of data into SAM then becomes an update import and updates records in SAM rather than creating new records. If the Student ID# value in the data file row exists within SAM, then the imported row of data updates the existing record in SAM. If the Student ID# value in the data file row does not exist within SAM, then the imported row of data creates a new student record in SAM during the import.<br />
Source Data<br />
<br />
===Source Data===<br />
<br />
====<u>PeopleSoft</u>====<br />
<br />
The data file received from PeopleSoft is a Microsoft Excel file consisting of a row for each student.<br />
<br />
====<u>SAM</u>====<br />
<br />
In SAM, the structure of the student table contains most of the fields referenced in the PeopleSoft file, plus many more. There are fields for Student ID, First Name, Last Name, Address1, Address2, City, State, Zip Code, Email, Phone Number, Academic Level, and Business Plan. However, Student ID is not the key field in SAM. Instead, SAM contains a unique key field on each student record called Student ID#. It is an auto-assigned integer value that is meaningless other than uniquely identifying the student record. To locate or update a student record in SAM, you use the Student ID#.<br />
<br />
====<u>Mapping</u>====<br />
<br />
{| class="wikitable" border="1"<br />
|- <br />
! PeopleSoft File Column !! SAM Student Table field !! Notes<br />
|-<br />
| Student Group Effective Date || &nbsp; || &nbsp;<br />
|-<br />
| Student Group Status || Status || A = ACTIVE, I = INACTIVE<br />
|-<br />
| PeopleSoft ID || Student ID || &nbsp;<br />
|-<br />
| Last Name || Last Name || &nbsp;<br />
|-<br />
| First Name || First Name || &nbsp;<br />
|-<br />
| Middle Name || Middle Name || &nbsp;<br />
|-<br />
| Address || Address1 || &nbsp;<br />
|-<br />
| City || City || &nbsp;<br />
|-<br />
| State || State || &nbsp;<br />
|-<br />
| Postal Code || Zip || &nbsp; <br />
|-<br />
| Preferred Phone Number || Phone || Formatting removed<br />
|-<br />
| Alternate Phone Number || Alternate Phone || Formatting removed<br />
|-<br />
| Alternate Phone Type || Alternate Phone Type || &nbsp;<br />
|-<br />
| Email || Email || &nbsp;<br />
|-<br />
| Ethnic Grp || Ethnicity || &nbsp;<br />
|-<br />
| Gender || Gender || M = MALE, F = FEMALE<br />
|-<br />
| DOB || Date of Birth || &nbsp; <br />
|-<br />
| Cum GPA || &nbsp; || &nbsp;<br />
|-<br />
| Academic Level || Academic Level || &nbsp;<br />
|-<br />
| Plan Code || Business Plan || &nbsp;<br />
|-<br />
| ERRS DSSVD Code || ERSS – D Code || &nbsp;<br />
|-<br />
| ERRS DSSPS Code || ERSS – A Code || &nbsp;<br />
|}<br />
<br />
===Building the SAM Import File using Microsoft Access===<br />
<br />
A Microsoft Access application can be used to compare the PeopleSoft and SAM Student files and generate a flat .txt file that can be imported into SAM.<br />
<br />
Using the Microsoft Access application assumes the following:<br />
<br />
# The PeopleSoft data file will not contain the SAM Student ID#.<br />
# You are manually maintaining the Student ID in SAM.<br />
# If there is not a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will be inserted to SAM.<br />
# If there is a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will update the SAM row.<br />
<br />
The Access application contains the following objects:<br />
<br />
Tables:<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
| PeopleSoft || A link table to the PeopleSoft flat file.<br />
|-<br />
| Students || A link table to the SAM export student table flat file.<br />
|}<br />
<br />
You want your tables to be link tables so that all you need to do is replace the underlying files to refresh the table data.<br />
<br />
Queries:<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
|Matched Query || A query that joins PeopleSoft to SAM using Student ID that selects all PeopleSoft rows and only the SAM rows where there is a match. The output columns are the SAM Student ID# and the columns from the PeopleSoft file that map to the columns in the SAM student table. The status column is changed from A or I to ACTIVE or INACTIVE. The phone number columns have formatting removed. The gender column is changed from M or F to MALE or FEMALE. These are the rows that need to be updated or imported in SAM using the PeopleSoft data.<br />
|}<br />
<br />
Macros:<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
| Matched Query Export || A macro that runs and exports the match query.<br />
|}<br />
<br />
====<u>Process</u>====<br />
<br />
The following process assumes the following:<br />
<br />
* The PeopleSoft file is called peoplesoft.xls.<br />
* The SAM student export is called Students.txt.<br />
* The Microsoft Access application is called ps2sam.mdb.<br />
* The match query output file is called Matched Query.xls.<br />
* The files and Microsoft Access application reside in folder called peoplesoft.<br />
<br />
=====<u>Step 1</u>=====<br />
<br />
# Open the PeopleSoft file peoplesoft.xls in the folder peoplesoft.<br />
# In SAM application, use Customize, Import/Export, and export the student table as a tab-delimited file called Students.txt in the folder peoplesoft. Note that you must change the file extension from tsv to txt.<br />
<br />
=====<u>Step 2</u>=====<br />
<br />
# Open ps2sam.mdb<br />
# Run macro Matched Query Export<br />
# Save file in folder peoplesoft and call file Matched Query.xls.<br />
# Quit ps2sam.mdb<br />
<br />
=====<u>Step 3</u>=====<br />
<br />
# Open the file Matched Query.xls.<br />
# Review the file and ensure that a pending student does not already exist in SAM with a blank or different Student ID. Perhaps the student is listed in SAM with the student ID of lastname + firstname but in the PeopleSoft file their 9 digit ID number is listed. <br />
# If the student is already in SAM, you need to update the SAM Student ID and start over at step 1. If not, a duplicate SAM student record will be created if you import the query file.<br />
# Save the Matched Query.xls file as a tab delimited .txt format file. This is necessary because QuickBase cannot import an Excel file but can import a tab delimited text file.<br />
<br />
=====<u>Step 4</u>=====<br />
<br />
# In SAM application, use Customize, Import/Export, and import into the student table the Matched Query.txt file. Check the box that states the first row is a list of field names. The import should state that the import is an update import. Be careful to review the fields that the data will import into and ensure that the columns are in the correct order. Student ID# should be the first columns followed by the columns in this order: Status, Student ID, Last Name, First Name, Middle Name, Address1, City, State, Zip, Phone, Alternate Phone, Alternate Phone Type, Email, Ethnicity, Gender, Date of Birth, Academic Level, Business Plan, ERRS – D Code, ERRS – A Code.<br />
# You are not required to import all columns, but you must select to import the Student ID#. This import will update SAM student records with the PeopleSoft data.<br />
<br />
===Building the SAM Import File using the Web Utility===<br />
<br />
A web utility can be used to compare the PeopleSoft and SAM Student files and generate a flat .csv file that can be imported into SAM.<br />
<br />
The web utility assumes the following:<br />
<br />
# The PeopleSoft data file will not contain the SAM Student ID#.<br />
# You are manually maintaining the Student ID in SAM.<br />
# If there is not a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will be inserted to SAM.<br />
# If there is a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will update the SAM row.<br />
<br />
====<u>Process</u>====<br />
<br />
The following process assumes the following:<br />
<br />
* The PeopleSoft file is called peoplesoft.xls.<br />
<br />
=====<u>Step 1</u>=====<br />
<br />
# Save the PeopleSoft file peoplesoft.xls as a CSV file named peoplesoft.csv.<br />
<br />
=====<u>Step 2</u>=====<br />
<br />
# Log into the SAM application.<br />
# On the dashboard, in the toolbox, click on the PeopleSoft to SAM Conversion Utility link.<br />
<br />
=====<u>Step 3</u>=====<br />
<br />
# Attach the peoplesoft.csv file.<br />
# Select the option that you want to create a file to be imported into SAM that will update existing SAM student data as well as create new students not currently in SAM but listed in PeopleSoft.<br />
# Click the submit button. <br />
# Save the file studentimport.csv to your computer.<br />
<br />
=====<u>Step 4</u>=====<br />
<br />
# In SAM application, use Customize, Import/Export, and import into the student table the studentimport.csv file. Check the box that states the first row is a list of field names. The import should state that the import is an update import. Be careful to review the fields that the data will import into and ensure that the columns are in the correct order. Student ID# should be the first columns followed by the columns in this order: Status, Student ID, Last Name, First Name, Middle Name, Address1, City, State, Zip, Phone, Alternate Phone, Alternate Phone Type, Email, Ethnicity, Gender, Date of Birth, Academic Level, Business Plan, ERRS – D Code, ERRS – A Code.<br />
# You are not required to import all columns, but you must select to import the Student ID#. This import will update SAM student records with the PeopleSoft data.<br />
<br />
===Further Reading===<br />
<br />
[http://www.quickbase.com/help/default.html#importing_data.html Import Data from Outside QuickBase]<br />
<br />
[[Category:Disability Service Provider]]<br />
[[Category:Information Technology]]<br />
[[Category:Software]]<br />
[[Category:Reference]]</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V2&diff=4965SAM V22009-06-25T18:10:13Z<p>Ben: </p>
<hr />
<div>{| style="width: 100%; background: #FDF8D6; border: 1px solid #cccccc; text-align: left;"<br />
|-<br />
| style="text-align: left; vertical-align: top; padding: 0.2em 0.4em;"|<br />
[[Image:Database.gif|Database Icon]]&nbsp;&nbsp;<font size="+1">'''Student Accommodation Manager Version 2 (SAM V2)'''</font><br />
<br />
The Student Accommodations Manager Version 2 (SAM V2) is a secure, web-based database application designed to help postsecondary Disability Service Providers manage student data, disabilities, accommodations, case notes, and much more. SAM V1 was developed using the leading open source solutions of [http://www.php.net PHP] and [http://www.mysql.com MySQL]. SAM V2 follows a traditional purchased software model where the SAM V2 software and database, along with PHP and MySQL, are installed on a server owned and managed by the institution. Essential functions such as installation, system availability and backups are the responsibility of the institution. Predefined reports as well as a report writer allow you to quickly find, filter, and transform data; however, knowledge of [http://www.w3schools.com/SQL/sql_intro.asp SQL] is required. For institutions with solid IT support, SAM V2 offers an affordable multi-user, web-based solution. <br />
<br />
<br />
[[Image:help.gif|Help Icon]]&nbsp;'''Learn More:'''<br />
<br />
*SAM V2 Fact Sheet<br />
*[https://www.uga.edu/amac/samv2/ SAM V2 Demo Application], for access please contact Joe Davis at 866-279-2964 or davisj@uga.edu <br />
*[[Media:SAMV1vsSAMV2.pdf|Comparison of SAM V1 and SAM V2]]<br />
*[http://media.wiley.com/product_data/excerpt/67/07645574/0764557467.pdf Why PHP and MySQL]<br />
| align="center" style="width: 20%;"|<br />
__TOC__<br />
|}<br />
<br />
==Features==<br />
<br />
* Totally web-based<br />
* Accessible<br />
* Custom, printable reporting<br />
* Access control via logins and permissions<br />
* Hardware maintenance and availability are the responsibility of the institution<br />
* Software installation and configuration are the responsibility of the institution<br />
* Database backup and availability are the responsibility of the institution<br />
<br />
[[Image:Alert.gif|Alert Icon]] For institutions considering SAM V2, it is important to remember:<br />
* The institution must have a web server with [http://www.php.net PHP] and [http://www.mysql.com MySQL] installed. <br />
*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. <br />
*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.<br />
<br />
==Terminology==<br />
<br />
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:<br />
<br />
* [[Wikipedia:Application_software|What is an application?]]<br />
* [[Wikipedia:Database|What is a database?]]<br />
* [[Wikipedia:Record_%28database%29|What is a record?]]<br />
* [[Wikipedia:Field_%28computer_science%29|What is a field?]]<br />
* [[Wikipedia:View_%28database%29|What is a report or view?]]<br />
<br />
==Tables==<br />
<br />
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.<br />
<br />
At the core is the [[SAM V2:Students|Student]] table, however, SAM V2 allows users to manage data for and report on:<br />
<br />
{| width="100%"<br />
|-<br />
|<br />
* [[SAM V2:Disabilities|Disabilities]]<br />
* [[SAM V2:Accommodations|Accommodations]]<br />
* [[SAM V2:Consent Types|Consent Types]]<br />
* [[SAM V2:Referrals|Referrals]]<br />
* [[SAM V2:Case Notes|Case Notes]]<br />
* [[SAM V2:Tasks|Tasks]]<br />
|<br />
<br />
* [[SAM V2:Tests|Tests]]<br />
* [[SAM V2:Orders|Alternate Media Orders]]<br />
* [[SAM V2:Components|Components]]<br />
* [[SAM V2:Class Schedules|Class Schedules]]<br />
* [[SAM V2:Documentation|Documentation]]<br />
|}<br />
<br />
In addition, SAM V2 allows for easy application setup and customization by adding or editing records in the following tables:<br />
<br />
* [[SAM V2:Accommodation Masters|Accommodation Masters]]<br />
* [[SAM V2:Multiple Choice Fields|Multiple Choice Fields]]<br />
* [[SAM V2:Reports|Reports]]<br />
* [[SAM V2:Users|Users]]<br />
* [[SAM V2:Permissions|Permissions]]<br />
<br />
==Access==<br />
<br />
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.<br />
<br />
==Security==<br />
<br />
* 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.<br />
* The physical security of the web and database server(s) is the responsibility of the institution.<br />
<br />
==Permissions==<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
==Reporting==<br />
<br />
With SAM V2, you can quickly and easily find and view your data the way you want. Reporting is simple, with: <br />
<br />
* A host of pre-defined reports to help you get started quickly. <br />
* A built-in report writer that allows you to create, print, or export tabular and summary reports. <br />
* A powerful Find feature that allows you to filter data by multiple fields. <br />
<br />
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.<br />
<br />
==Implementation==<br />
<br />
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.<br />
<br />
To help with implementation, [http://www.amac.uga.edu/ AMAC] has developed a [[Media:SAM_V2_Implementation_Guide.doc|SAM V2 Implementation Guide]]. This document helps the disability service provider identify:<br />
<br />
* The users who will have access<br />
* The user permissions<br />
* The multiple-choice field values<br />
* The list of available accommodations<br />
<br />
==Licensing Agreement==<br />
<br />
*[[Media:SAMV2_Services_Agreement.doc|SAM V2 Services Agreement]]<br />
<br />
==Pricing==<br />
<br />
{|width="100%" border="0" cellspacing="0" cellpadding="0" valign="top" <br />
|-<br />
| colspan="2" style="border: 1px solid #cccccc; text-align: left; background: #cedff2; font-weight: bold; color: #000000; padding: 0.2em 0.4em;"|<br />
===Required Costs===<br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Initial Application Fee and Training<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
One Payment of $950, [[Disability_Professional_Member_Guide|AMAC Members]] $750 (Reduced) <br />
*Source code for the SAM V2 application and database.<br />
*Access to the SAM V2 online application documentation. <br />
*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.<br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Hosting/User Fees<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
None<br />
*PHP and SAM V2 PHP source code are installed on web server owned and managed by institution.<br />
*MySQL and SAM V2 MySQL database are installed by the institution on server owned and managed by institution.<br />
*PHP and MySQL are open source.<br />
|-<br />
| style="border-left: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Support Fee<br />
| style="border-left: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$500/year <br />
*Required the first year of purchase.<br />
*Estimated ten hours of support per month.<br />
*Covers application questions and assistance with report creation.<br />
|-<br />
| colspan="2" style="border: 1px solid #cccccc; text-align: left; background: #cedff2; font-weight: bold; color: #000000; padding: 0.2em 0.4em;"|<br />
<br />
===Optional Costs===<br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Support Fee<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$500/year <br />
*Optional after the first year of purchase.<br />
*Estimated ten hours of support per month.<br />
*Covers application questions and assistance with report creation.<br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
Customization Fee<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$125/hour <br />
*Covers application customization, import of legacy data, and integration with external systems (i.e. Banner).<br />
|-<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
On-Site Customer Training<br />
| style="border-left: 1px solid #cccccc; border-bottom: 1px solid #cccccc; border-right: 1px solid #cccccc; vertical-align: top; background: #fafafa; padding: 0.2em 0.4em;"|<br />
$1,200/day plus travel costs <br />
|}<br />
<br />
[[Category:Disability Service Provider]]<br />
[[Category:Information Technology]]<br />
[[Category:Software]]<br />
[[Category:Reference]]</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=Student&diff=4964Student2009-06-25T18:06:26Z<p>Ben: New page: ==Student== The Banner student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in pl...</p>
<hr />
<div>==Student==<br />
<br />
The Banner student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract.<br />
<br />
The SAM application contains the follow data elements for student:<br />
{| border="1" cellspacing="1" cellpadding="1"<br />
!Field Name<br />
!Data Type<br />
!Notes<br />
!Possible Banner Feed<br />
|-<br />
|Student ID<br />
|varchar<br />
|Unique Student ID (ss#/School ID)<br />
|yes<br />
|-<br />
|Status<br />
|varchar<br />
|&nbsp;<br />
|yes<br />
|- <br />
|Last Name<br />
|varchar<br />
|&nbsp;<br />
|yes<br />
|-<br />
|First Name <br />
|varchar<br />
|&nbsp; <br />
|yes<br />
|-<br />
|Middle Name <br />
|varchar<br />
|&nbsp; <br />
|yes<br />
|-<br />
|Preferred Name <br />
|varchar<br />
|The name the Student prefers<br />
|yes<br />
|-<br />
|Address<br />
|varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|City<br />
|varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|State<br />
|varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|Zip Code<br />
|varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|Alternate Address<br />
|varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|City<br />
|varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|State<br />
|varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|Zip Code<br />
|varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|Email<br />
|varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|Alternate Email<br />
|Varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|Phone Number<br />
|varchar<br />
|10 digit number without formatting is preferred<br />
|Yes<br />
|-<br />
|Phone Type<br />
|varchar<br />
|Home, Cell, Fax, etc.<br />
|Yes<br />
|-<br />
|Alternative Phone Number<br />
|varchar<br />
|10 digit number without formatting is preferred<br />
|Yes<br />
|-<br />
|Alternative Type<br />
|varchar<br />
|Home, Cell, Fax, etc.<br />
|Yes<br />
|-<br />
|Gender<br />
|varchar<br />
|Male, Female, etc.<br />
|Yes<br />
|-<br />
|Date Of Birth<br />
|date<br />
|MM/DD/YYYY<br />
|Yes<br />
|-<br />
|Ethnicity<br />
|varchar<br />
|Caucasian, African American, Hispanic, Etc.<br />
|Yes<br />
|-<br />
|US Citizen<br />
|boolean<br />
|&nbsp;<br />
|Yes/no <br />
|-<br />
|Emergency Contact Name<br />
|varchar<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Emergency Contact Phone Number<br />
|varchar<br />
|10 digit number without formatting is preferred <br />
|&nbsp;<br />
|-<br />
|Emergency Phone Type<br />
|varchar<br />
|Home, Cell, Fax, etc. <br />
|&nbsp;<br />
|-<br />
|Campus<br />
|varchar <br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Service Provider<br />
|varchar <br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Primary campus student attends<br />
|varchar<br />
|&nbsp;<br />
|&nbsp;<br />
|- <br />
|Academic Level<br />
|varchar<br />
|Freshmen, Sophomore, Junior, Senior, Graduate, etc.<br />
|Yes<br />
|-<br />
|Enrollment<br />
|varchar<br />
|Enrolled, Graduated, Transferred, Withdrawn, etc.<br />
|Yes<br />
|}</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:import&diff=4963SAM V1:import2009-06-25T17:54:23Z<p>Ben: </p>
<hr />
<div>=='''Banner Data'''==<br />
<br />
In order to import data into SAM a Banner data extract/script will have to be created. There are two SAM tables that need to be submitted to the Banner IT professional '''student and class schedules'''. The Banner data extract format can be either a CSV file or a tab-delimited text file. Ideally the DSP should be able to run the Banner extract (created by the Banner IT professional) on demand and save the data to a local file. This local file would then be [https://www.quickbase.com/help/default.html#importing_data.html imported] by the end-user into SAM. <br />
<br />
'''THE DSP SHOULD SUBMIT A COPY OF THE '''[[Student]]''' AND '''[[Class Schedules]]''' DATA TO THEIR BANNER IT REPRESENTATIVE.''' From that point the Banner It representative can assemble a script containing all students receiving disability services. Now the DSP has a list from Banner that contains all of the required fields for SAM. The Banner IT representative should make the script into a process that the DSP can use weekly to update SAM.<br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V2:import&diff=4962SAM V2:import2009-06-25T17:52:13Z<p>Ben: </p>
<hr />
<div>=='''Banner Data'''==<br />
<br />
In order to import data into SAMV2 a Banner data extract/script will have to be created. There are two SAM tables that need to be submitted to the Banner IT professional '''student and class schedules'''. The Banner data extract format can be either a CSV file or a tab-delimited text file. Ideally the IT professional should be able to run the Banner extract on demand and save the data to a local file. This local file would then be loaded/updated by the IT professional using SQL/MySQL into SAM.<br />
'''THE IT PROFESSIONAL SHOULD SUBMIT A COPY OF THE '''[[Student]]''' AND '''[[Class Schedules]]''' DATA TO THEIR BANNER IT REPRESENTATIVE.''' <br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V2:import&diff=4959SAM V2:import2009-06-25T17:48:30Z<p>Ben: </p>
<hr />
<div>=='''Banner Data'''==<br />
<br />
In order to import data into SAMV2 a Banner data extract/script will have to be created. There are two SAM tables that need to be submitted to the Banner IT professional '''student and class schedules'''. The Banner data extract format can be either a CSV file or a tab-delimited text file. Ideally the IT professional should be able to run the Banner extract on demand and save the data to a local file. This local file would then be loaded by the IT professional using SQL/MySQL into SAM.<br />
'''THE IT PROFESSIONAL SHOULD SUBMIT A COPY OF THE '''[[Student]]''' AND '''[[Class Schedules]]''' DATA TO THEIR BANNER IT REPRESENTATIVE.''' <br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V2:import&diff=4958SAM V2:import2009-06-25T16:29:11Z<p>Ben: </p>
<hr />
<div>=='''Banner Data'''==<br />
<br />
In order to import data into SAMV2 a Banner data extract/script will have to be created. There are two SAM tables that need to be submitted to the Banner IT professional '''student and class schedules'''. The Banner data extract format can be either a CSV file or a tab-delimited text file. Ideally the IT professional should be able to run the Banner extract on demand and save the data to a local file. This local file would then be loaded by the IT professional using SQL/MySQL into SAM. <br />
<br />
'''THE DSP SHOULD SUBMIT A COPY OF THE '''[[Student]]''' AND '''[[Class Schedules]]''' DATA TO THEIR BANNER IT REPRESENTATIVE.''' From that point the Banner It representative can assemble a script containing all students receiving disability services. Now the DSP has a list from Banner that contains all of the required fields for SAM. The Banner IT representative should make the script into a process that the DSP can use weekly to update SAM.<br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V2:import&diff=4957SAM V2:import2009-06-25T16:28:05Z<p>Ben: </p>
<hr />
<div>=='''Banner Data'''==<br />
<br />
In order to import data into SAMV2 a Banner data extract/script will have to be created. There are two SAM tables that need to be submitted to the Banner IT professional '''student and class schedules'''. The Banner data extract format can be either a CSV file or a tab-delimited text file. Ideally the DSP should be able to run the Banner extract on demand and save the data to a local file. This local file would then be loaded by the IT professional using SQL/MsQL into SAM. <br />
<br />
'''THE DSP SHOULD SUBMIT A COPY OF THE '''[[Student]]''' AND '''[[Class Schedules]]''' DATA TO THEIR BANNER IT REPRESENTATIVE.''' From that point the Banner It representative can assemble a script containing all students receiving disability services. Now the DSP has a list from Banner that contains all of the required fields for SAM. The Banner IT representative should make the script into a process that the DSP can use weekly to update SAM.<br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V2:import&diff=4956SAM V2:import2009-06-25T16:27:05Z<p>Ben: </p>
<hr />
<div>=='''Banner Data'''==<br />
<br />
In order to import data into SAMV2 a Banner data extract/script will have to be created. There are two SAM tables that need to be submitted to the Banner IT professional '''student and class schedules'''. The Banner data extract format can be either a CSV file or a tab-delimited text file. Ideally the DSP should be able to run the Banner extract on demand and save the data to a local file. This local file would then be loaded by the end-user into SAM. <br />
<br />
'''THE DSP SHOULD SUBMIT A COPY OF THE '''[[Student]]''' AND '''[[Class Schedules]]''' DATA TO THEIR BANNER IT REPRESENTATIVE.''' From that point the Banner It representative can assemble a script containing all students receiving disability services. Now the DSP has a list from Banner that contains all of the required fields for SAM. The Banner IT representative should make the script into a process that the DSP can use weekly to update SAM.<br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:import&diff=4954SAM V1:import2009-06-25T16:22:49Z<p>Ben: </p>
<hr />
<div>=='''Banner Data'''==<br />
<br />
In order to import data into SAM a Banner data extract/script will have to be created. There are two SAM tables that need to be submitted to the Banner IT professional '''student and class schedules'''. The Banner data extract format can be either a CSV file or a tab-delimited text file. Ideally the DSP should be able to run the Banner extract (created by the Banner IT professional) on demand and save the data to a local file. This local file would then be [https://www.quickbase.com/help/default.html#importing_data.html imported] by the end-user into SAM. <br />
<br />
'''THE DSP SHOULD SUBMIT A COPY OF THE '''[[Student]]''' AND '''[[Class Schedules]]''' DATA TO THEIR BANNER IT REPRESENTATIVE.''' From that point the Banner It representative can assemble a script containing all students receiving disability services. Now the DSP has a list from Banner that contains all of the required fields for SAM. The Banner IT representative should make the script into a process that the DSP can use weekly to update SAM.<br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V2:import&diff=4949SAM V2:import2009-06-25T16:13:16Z<p>Ben: </p>
<hr />
<div>=='''Banner Data'''==<br />
<br />
In order to import data into SAM a Banner data extract/script will have to be created. There are two SAM tables that need to be submitted to the Banner IT professional '''student and class schedules'''. The Banner data extract format can be either a CSV file or a tab-delimited text file. Ideally the DSP should be able to run the Banner extract on demand and save the data to a local file. This local file would then be loaded by the end-user into SAM. <br />
<br />
'''THE DSP SHOULD SUBMIT A COPY OF THE '''[[Student]]''' AND '''[[Class Schedules]]''' DATA TO THEIR BANNER IT REPRESENTATIVE.''' From that point the Banner It representative can assemble a script containing all students receiving disability services. Now the DSP has a list from Banner that contains all of the required fields for SAM. The Banner IT representative should make the script into a process that the DSP can use weekly to update SAM.<br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V2:import&diff=4948SAM V2:import2009-06-25T16:12:28Z<p>Ben: </p>
<hr />
<div>=='''Banner Data'''==<br />
<br />
In order to import data into SAM a Banner data extract/script will have to be created. There are two SAM tables that need to be submitted to the Banner IT professional '''student and class schedules'''. The Banner data extract format can be either a CSV file or a tab-delimited text file. Ideally the end-user should be able to run the Banner extract on demand and save the data to a local file. This local file would then be loaded by the end-user into SAM. <br />
<br />
'''THE DSP SHOULD SUBMIT A COPY OF THE '''[[Student]]''' AND '''[[Class Schedules]]''' DATA TO THEIR BANNER IT REPRESENTATIVE.''' From that point the Banner It representative can assemble a script containing all students receiving disability services. Now the DSP has a list from Banner that contains all of the required fields for SAM. The Banner IT representative should make the script into a process that the DSP can use weekly to update SAM.<br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:import&diff=4947SAM V1:import2009-06-25T16:07:52Z<p>Ben: </p>
<hr />
<div>=='''Banner Data'''==<br />
<br />
In order to import data into SAM a Banner data extract/script will have to be created. There are two SAM tables that need to be submitted to the Banner IT professional '''student and class schedules'''. The Banner data extract format can be either a CSV file or a tab-delimited text file. Ideally the DSP should be able to run the Banner extract (created by the Banner IT professional) on demand and save the data to a local file. This local file would then be imported by the end-user into SAM. <br />
<br />
'''THE DSP SHOULD SUBMIT A COPY OF THE '''[[Student]]''' AND '''[[Class Schedules]]''' DATA TO THEIR BANNER IT REPRESENTATIVE.''' From that point the Banner It representative can assemble a script containing all students receiving disability services. Now the DSP has a list from Banner that contains all of the required fields for SAM. The Banner IT representative should make the script into a process that the DSP can use weekly to update SAM.<br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:import&diff=4946SAM V1:import2009-06-25T16:06:32Z<p>Ben: </p>
<hr />
<div>=='''Banner Data'''==<br />
<br />
In order to import data into SAM a Banner data extract/script will have to be created. There are two SAM tables that need to be submitted to the Banner IT professional '''student and class schedules'''. The Banner data extract format can be either a CSV file or a tab-delimited text file. Ideally the end-user should be able to run the Banner extract (created by the Banner IT professional) on demand and save the data to a local file. This local file would then be imported by the end-user into SAM. <br />
<br />
'''THE DSP SHOULD SUBMIT A COPY OF THE '''[[Student]]''' AND '''[[Class Schedules]]''' DATA TO THEIR BANNER IT REPRESENTATIVE.''' From that point the Banner It representative can assemble a script containing all students receiving disability services. Now the DSP has a list from Banner that contains all of the required fields for SAM. The Banner IT representative should make the script into a process that the DSP can use weekly to update SAM.<br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:import&diff=4945SAM V1:import2009-06-25T16:05:39Z<p>Ben: </p>
<hr />
<div>=='''Banner Data'''==<br />
<br />
In order to import data into SAM a Banner data extract/script will have to be created. There are two SAM tables that need to be submitted to the Banner IT professional '''student and class schedules'''. The Banner data extract format can be either a CSV file or a tab-delimited text file. Ideally the end-user should be able to run the Banner extract (that was created by the Banner IT professional) on demand and save the data to a local file. This local file would then be imported by the end-user into SAM. <br />
<br />
'''THE DSP SHOULD SUBMIT A COPY OF THE '''[[Student]]''' AND '''[[Class Schedules]]''' DATA TO THEIR BANNER IT REPRESENTATIVE.''' From that point the Banner It representative can assemble a script containing all students receiving disability services. Now the DSP has a list from Banner that contains all of the required fields for SAM. The Banner IT representative should make the script into a process that the DSP can use weekly to update SAM.<br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:import&diff=4944SAM V1:import2009-06-25T16:04:26Z<p>Ben: </p>
<hr />
<div>=='''Banner Data'''==<br />
<br />
In order to import data into SAM a Banner data extract/script will have to be created. There are two SAM tables that ''student and class schedules''' that need to be submitted to the Banner IT professional. The Banner data extract format can be either a CSV file or a tab-delimited text file. Ideally the end-user should be able to run the Banner extract (that was created by the Banner IT professional) on demand and save the data to a local file. This local file would then be imported by the end-user into SAM. <br />
<br />
'''THE DSP SHOULD SUBMIT A COPY OF THE '''[[Student]]''' AND '''[[Class Schedules]]''' DATA TO THEIR BANNER IT REPRESENTATIVE.''' From that point the Banner It representative can assemble a script containing all students receiving disability services. Now the DSP has a list from Banner that contains all of the required fields for SAM. The Banner IT representative should make the script into a process that the DSP can use weekly to update SAM.<br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=Class_Schedules&diff=4943Class Schedules2009-06-25T15:50:08Z<p>Ben: New page: '''Class Schedule''' The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three ro...</p>
<hr />
<div>'''Class Schedule'''<br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.<br />
<br />
The SAM application contains the follow data elements for class schedule:<br />
{| border="1" cellspacing="1" cellpadding="1"<br />
!Field Name<br />
!Data Type<br />
!Format<br />
!Possible Banner Feed<br />
|-<br />
|Unique Student ID (ss#)<br />
|varchar<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Term<br />
|varchar<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Year<br />
|varchar<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Course<br />
|varchar<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Description<br />
|varchar<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Instructor<br />
|varchar<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Instructor Phone<br />
|varchar<br />
|&nbsp;<br />
|&nbsp;<br />
|- <br />
|Instructor Email<br />
|varchar<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Location<br />
|varchar <br />
|&nbsp;<br />
|yes<br />
|-<br />
|Monday<br />
|boolean<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Tuesday<br />
|boolean<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Wednesday<br />
|boolean<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Thursday<br />
|boolean<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Friday<br />
|boolean<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Saturday<br />
|boolean<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Sunday<br />
|boolean<br />
|&nbsp;<br />
|yes<br />
|-<br />
|StartTime<br />
|timeofday<br />
|HH:MM AM or PM<br />
|yes<br />
|-<br />
|End time<br />
|timeofday<br />
|HH:MM AM or PM<br />
|yes<br />
|-<br />
|Notes<br />
|varchar<br />
|&nbsp;<br />
|&nbsp;<br />
|}<br />
<br />
[[Category:Reference]]</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V2:import&diff=4942SAM V2:import2009-06-25T15:42:01Z<p>Ben: New page: =='''Banner Data'''== There are two SAM tables that can be data imported from Banner: '''student and class schedules''' . The Banner data extract format can be either a CSV file or a tab...</p>
<hr />
<div>=='''Banner Data'''==<br />
<br />
There are two SAM tables that can be data imported from Banner: '''student and class schedules''' . The Banner data extract format can be either a CSV file or a tab-delimited text file. Ideally the end-user should be able to run the Banner extract on demand and save the data to a local file. This local file would then be loaded by the end-user into SAM. <br />
<br />
'''THE DSP SHOULD SUBMIT A COPY OF THE '''[[Student]]''' AND '''[[Class Schedules]]''' DATA TO THEIR BANNER IT REPRESENTATIVE.''' From that point the Banner It representative can assemble a script containing all students receiving disability services. Now the DSP has a list from Banner that contains all of the required fields for SAM. The Banner IT representative should make the script into a process that the DSP can use weekly to update SAM.<br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:import&diff=4939SAM V1:import2009-06-25T15:33:31Z<p>Ben: </p>
<hr />
<div>=='''Banner Data'''==<br />
<br />
There are two SAM tables that can be data imported from Banner: '''student and class schedules''' . The Banner data extract format can be either a CSV file or a tab-delimited text file. Ideally the end-user should be able to run the Banner extract on demand and save the data to a local file. This local file would then be loaded by the end-user into SAM. <br />
<br />
'''THE DSP SHOULD SUBMIT A COPY OF THE '''[[Student]]''' AND '''[[Class Schedules]]''' DATA TO THEIR BANNER IT REPRESENTATIVE.''' From that point the Banner It representative can assemble a script containing all students receiving disability services. Now the DSP has a list from Banner that contains all of the required fields for SAM. The Banner IT representative should make the script into a process that the DSP can use weekly to update SAM.<br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V2:Students&diff=4938SAM V2:Students2009-06-25T15:15:38Z<p>Ben: </p>
<hr />
<div>The student table contains information about the students that receive disability services. A student record is created one time only. The student record is considered the master or parent record. The disabilities, accommodations, consent types, referrals, case notes, tasks, test scores, and class schedules are sub-tables or child records of the student record. The relationship is many children to one parent. In other words, the student record has many disabilities, accommodations, or case notes records related to it.<br />
<br />
When the student record is deleted, all child records related to it are also deleted. This cascading deletion scheme is used so that the child records will not be orphaned. <br />
<br />
[[SAM V2#Tables|Back to SAM V2 Tables]]<br />
<br />
==Status==<br />
<br />
The status field can be the value active, inactive, etc. It is used to determine if the student is using disability services.<br />
<br />
The status field can be reset to inactive for all students at the beginning of each term. Then, as service providers work with students, the status field would be changed to active. By doing so, it would be possible to determine which students are active for the current term. <br />
<br />
==Fields==<br />
<br />
The fields of the students table are:<br />
<br />
{| border="1" cellspacing="1" cellpadding="1"<br />
!Field<br />
!Description<br />
|-<br />
|academic_level <br />
|Academic Level of student: Freshman, Sophomore, Junior, Senior, Graduate, etc.<br />
|-<br />
|address1 <br />
|Address line 1 of student.<br />
|-<br />
|address2<br />
|Address line 2 of student.<br />
|-<br />
|alt_address1 <br />
|Alternate address line 1 of student.<br />
|-<br />
|alt_address2<br />
|Alternate address line 2 of student.<br />
|-<br />
|alt_city<br />
|Alternate address city of student.<br />
|-<br />
|alt_email<br />
|Alternative email address of student.<br />
|-<br />
|alt_phone <br />
|Alternate phone number of student.<br />
|-<br />
|alt_phone_type <br />
|Type of alternative phone number: Home, Cell, Fax, etc.<br />
|-<br />
|alt_state<br />
|Alternate address state of student.<br />
|-<br />
|alt_zip<br />
|Alternate address zip code of the student.<br />
|-<br />
|campus <br />
|The primary campus the student attends.<br />
|-<br />
|city<br />
|Address city of student.<br />
|-<br />
|date_of_birth <br />
|Date of birth of student.<br />
|-<br />
|emergency_contact<br />
|First and last name of emergency contact of student.<br />
|-<br />
|emergency_contact_phone<br />
|Phone number for the emegency contact of the student.<br />
|-<br />
|emergency_relationship<br />
|Relationship of the emergency contact to the student.<br />
|-<br />
|email<br />
|Email address of student.<br />
|-<br />
|enrollment <br />
|Enrollment status of the student: Enrolled, Graduated, Transferred, Withdrawn, etc.<br />
|-<br />
|ethnicity <br />
|Ethnicity of student: Caucasian, African American, Hispanic, etc.<br />
|-<br />
|first_name<br />
|First name of student. First Name is required.<br />
|-<br />
|gender <br />
|Gender of student: Male, Female, etc.<br />
|-<br />
|id <br />
|Unique student identifier. This field could contain university identification number, social security number, or something similar. ID is required.<br />
|-<br />
|last_name <br />
|Last name of student. Last Name is required.<br />
|-<br />
|last_updated <br />
|Date record was last updated.<br />
|-<br />
|middle_name <br />
|Middle name of student.<br />
|-<br />
|notes <br />
|Notes pertaining to the student. These are not case notes but additional information about the student.<br />
|-<br />
|phone <br />
|Phone number of student.<br />
|-<br />
|phone_type <br />
|Type of phone number: Home, Cell, Fax, etc.<br />
|-<br />
|preferred_ame <br />
|The name the student prefers to go by.<br />
|-<br />
|sid <br />
|Unique ID# of the record.<br />
|-<br />
|service_provider <br />
|The service provider working with or assigned to the student.<br />
|-<br />
|state<br />
|Address state of the student.<br />
|-<br />
|status <br />
|Student status: Active, Inactive, Prospective. Status is required. The default value is Active.<br />
|-<br />
|updated_by <br />
|User who last modified the record.<br />
|-<br />
|us_citizen <br />
|Checkbox to be checked if student is a citizen of the USA.<br />
|-<br />
|zip<br />
|Address zip code of the student<br />
|}<br />
<br />
=='''Banner'''== <br />
<br />
How to [[SAM V2:import|import]] information into SAMV2.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V2:Students&diff=4937SAM V2:Students2009-06-25T15:14:31Z<p>Ben: </p>
<hr />
<div>The student table contains information about the students that receive disability services. A student record is created one time only. The student record is considered the master or parent record. The disabilities, accommodations, consent types, referrals, case notes, tasks, test scores, and class schedules are sub-tables or child records of the student record. The relationship is many children to one parent. In other words, the student record has many disabilities, accommodations, or case notes records related to it.<br />
<br />
When the student record is deleted, all child records related to it are also deleted. This cascading deletion scheme is used so that the child records will not be orphaned. <br />
<br />
[[SAM V2#Tables|Back to SAM V2 Tables]]<br />
<br />
==Status==<br />
<br />
The status field can be the value active, inactive, etc. It is used to determine if the student is using disability services.<br />
<br />
The status field can be reset to inactive for all students at the beginning of each term. Then, as service providers work with students, the status field would be changed to active. By doing so, it would be possible to determine which students are active for the current term. <br />
<br />
==Fields==<br />
<br />
The fields of the students table are:<br />
<br />
{| border="1" cellspacing="1" cellpadding="1"<br />
!Field<br />
!Description<br />
|-<br />
|academic_level <br />
|Academic Level of student: Freshman, Sophomore, Junior, Senior, Graduate, etc.<br />
|-<br />
|address1 <br />
|Address line 1 of student.<br />
|-<br />
|address2<br />
|Address line 2 of student.<br />
|-<br />
|alt_address1 <br />
|Alternate address line 1 of student.<br />
|-<br />
|alt_address2<br />
|Alternate address line 2 of student.<br />
|-<br />
|alt_city<br />
|Alternate address city of student.<br />
|-<br />
|alt_email<br />
|Alternative email address of student.<br />
|-<br />
|alt_phone <br />
|Alternate phone number of student.<br />
|-<br />
|alt_phone_type <br />
|Type of alternative phone number: Home, Cell, Fax, etc.<br />
|-<br />
|alt_state<br />
|Alternate address state of student.<br />
|-<br />
|alt_zip<br />
|Alternate address zip code of the student.<br />
|-<br />
|campus <br />
|The primary campus the student attends.<br />
|-<br />
|city<br />
|Address city of student.<br />
|-<br />
|date_of_birth <br />
|Date of birth of student.<br />
|-<br />
|emergency_contact<br />
|First and last name of emergency contact of student.<br />
|-<br />
|emergency_contact_phone<br />
|Phone number for the emegency contact of the student.<br />
|-<br />
|emergency_relationship<br />
|Relationship of the emergency contact to the student.<br />
|-<br />
|email<br />
|Email address of student.<br />
|-<br />
|enrollment <br />
|Enrollment status of the student: Enrolled, Graduated, Transferred, Withdrawn, etc.<br />
|-<br />
|ethnicity <br />
|Ethnicity of student: Caucasian, African American, Hispanic, etc.<br />
|-<br />
|first_name<br />
|First name of student. First Name is required.<br />
|-<br />
|gender <br />
|Gender of student: Male, Female, etc.<br />
|-<br />
|id <br />
|Unique student identifier. This field could contain university identification number, social security number, or something similar. ID is required.<br />
|-<br />
|last_name <br />
|Last name of student. Last Name is required.<br />
|-<br />
|last_updated <br />
|Date record was last updated.<br />
|-<br />
|middle_name <br />
|Middle name of student.<br />
|-<br />
|notes <br />
|Notes pertaining to the student. These are not case notes but additional information about the student.<br />
|-<br />
|phone <br />
|Phone number of student.<br />
|-<br />
|phone_type <br />
|Type of phone number: Home, Cell, Fax, etc.<br />
|-<br />
|preferred_ame <br />
|The name the student prefers to go by.<br />
|-<br />
|sid <br />
|Unique ID# of the record.<br />
|-<br />
|service_provider <br />
|The service provider working with or assigned to the student.<br />
|-<br />
|state<br />
|Address state of the student.<br />
|-<br />
|status <br />
|Student status: Active, Inactive, Prospective. Status is required. The default value is Active.<br />
|-<br />
|updated_by <br />
|User who last modified the record.<br />
|-<br />
|us_citizen <br />
|Checkbox to be checked if student is a citizen of the USA.<br />
|-<br />
|zip<br />
|Address zip code of the student<br />
|}<br />
<br />
=='''Banner'''== <br />
<br />
How to [[SAM V1:import|import]] information into SAMV1.</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V2:Class_Schedules&diff=4934SAM V2:Class Schedules2009-06-25T15:10:16Z<p>Ben: </p>
<hr />
<div>The class schedules table contains the class schedules for each student. A class schedule record exists for each class taken by the student, so if the student has registered for 3 classes, then the one student parent record will have 3 child class schedule records.<br />
<br />
The accommodation notification can be printed from the class schedules record and will display course and instructor information.<br />
<br />
[[SAM V2#Tables|Back to SAM V2 Tables]]<br />
<br />
==Fields==<br />
<br />
The fields of the class schedules table are:<br />
<br />
{| border="1" cellspacing="1" cellpadding="1"<br />
!Field<br />
!Description<br />
|-<br />
|course <br />
|Name of course. Course is required.<br />
|-<br />
|course_number<br />
|Number of course.<br />
|-<br />
|credits<br />
|Number of credits student receives for the course.<br />
|-<br />
|end_time <br />
|Time the course instruction ends.<br />
|-<br />
|final_grade<br />
|Final grade received by student for the course.<br />
|-<br />
|friday <br />
|Check if the course is taught on Friday.<br />
|-<br />
|instructor <br />
|Name of instructor teaching the course.<br />
|-<br />
|last_updated <br />
|Date record was last updated.<br />
|-<br />
|location <br />
|Physical location (i.e.: building and room number) where the course is taught.<br />
|-<br />
|monday <br />
|Check if the course is taught on Monday.<br />
|-<br />
|notes <br />
|Notes regarding the class schedule.<br />
|-<br />
|saturday <br />
|Check if the course is taught on Saturday.<br />
|-<br />
|sunday <br />
|Check if the course is taught on Sunday.<br />
|-<br />
|start_time <br />
|Time the course instruction begins.<br />
|-<br />
|sid <br />
|The student the class schedule is related to. Student is required.<br />
|-<br />
|term <br />
|Term the student is taking the class: Fall, Winter, Spring, Summer, etc. Term is required.<br />
|-<br />
|tuesday <br />
|Check if the course is taught on Tuesday.<br />
|-<br />
|thursday <br />
|Check if the course is taught on Thursday<br />
|-<br />
|wednesday <br />
|Check if the course is taught on Wednesday.<br />
|-<br />
|year <br />
|Year the student is taking the class. Year is required.<br />
|-<br />
|uid <br />
|Unique ID# of the record.<br />
|-<br />
|updated_by <br />
|User who last modified the record.<br />
|}</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:Class_Schedules&diff=4933SAM V1:Class Schedules2009-06-25T15:09:24Z<p>Ben: </p>
<hr />
<div>The class schedules table contains the class schedules for each student. A class schedule record exists for each class taken by the student, so if the student has registered for 3 classes, then the one student parent record will have 3 child class schedule records.<br />
<br />
[[SAM V1#Tables|Back to SAM V1 Tables]]<br />
<br />
==Fields==<br />
<br />
The fields of the class schedules table are:<br />
<br />
{| border="1" cellspacing="1" cellpadding="1"<br />
!Field<br />
!Description<br />
|-<br />
|Date Created <br />
|Date record was created.<br />
|-<br />
|Date Modified <br />
|Date record was last updated.<br />
|-<br />
|Class Schedule ID# <br />
|Unique ID# of the record.<br />
|-<br />
|Record Owner <br />
|User who owns the record.<br />
|-<br />
|Last Modified By <br />
|User who last modified the record.<br />
|-<br />
|Course <br />
|Name or number of the course. Course is required.<br />
|-<br />
|Description <br />
|Description of the course.<br />
|-<br />
|End Time <br />
|Time the course instruction ends.<br />
|-<br />
|Friday <br />
|Check if the course is taught on Friday.<br />
|-<br />
|Instructor <br />
|Name of instructor teaching the course.<br />
|-<br />
|Instructor Email <br />
|Email of the instructor teaching the course.<br />
|-<br />
|Instructor Phone <br />
|Phone number of the instructor teaching the course.<br />
|-<br />
|Location <br />
|Physical location (i.e.: building and room number) where the course is taught.<br />
|-<br />
|Monday <br />
|Check if the course is taught on Monday.<br />
|-<br />
|Notes <br />
|Notes regarding the class schedule. The notes field is a cumulative field and date stamped with the date, time and user adding the notes.<br />
|-<br />
|Print Faculty Accommodation Notification <br />
|Use this link to print the faculty accommodation notification letter for the student. The faculty accommodation notification letter contains the instructor and course name.<br />
|-<br />
|Saturday <br />
|Check if the course is taught on Saturday.<br />
|-<br />
|Sunday <br />
|Check if the course is taught on Sunday.<br />
|-<br />
|Start Time <br />
|Time the course instruction begins.<br />
|-<br />
|Student ID <br />
|The student the class schedule is related to. Student ID is required.<br />
|-<br />
|Term <br />
|Term the student is taking the class: Fall, Winter, Spring, Summer, etc. Term is required.<br />
|-<br />
|Tuesday <br />
|Check if the course is taught on Tuesday.<br />
|-<br />
|Thursday <br />
|Check if the course is taught on Thursday<br />
|-<br />
|Wednesday <br />
|Check if the course is taught on Wednesday.<br />
|-<br />
|Year <br />
|Year the student is taking the class. Year is required.<br />
|}</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:Class_Schedules&diff=4932SAM V1:Class Schedules2009-06-25T15:09:01Z<p>Ben: </p>
<hr />
<div>The class schedules table contains the class schedules for each student. A class schedule record exists for each class taken by the student, so if the student has registered for 3 classes, then the one student parent record will have 3 child class schedule records.<br />
<br />
[[SAM V1#Tables|Back to SAM V1 Tables]]<br />
<br />
==Fields==<br />
<br />
The fields of the class schedules table are:<br />
<br />
{| border="1" cellspacing="1" cellpadding="1"<br />
!Field<br />
!Description<br />
|-<br />
|Date Created <br />
|Date record was created.<br />
|-<br />
|Date Modified <br />
|Date record was last updated.<br />
|-<br />
|Class Schedule ID# <br />
|Unique ID# of the record.<br />
|-<br />
|Record Owner <br />
|User who owns the record.<br />
|-<br />
|Last Modified By <br />
|User who last modified the record.<br />
|-<br />
|Course <br />
|Name or number of the course. Course is required.<br />
|-<br />
|Description <br />
|Description of the course.<br />
|-<br />
|End Time <br />
|Time the course instruction ends.<br />
|-<br />
|Friday <br />
|Check if the course is taught on Friday.<br />
|-<br />
|Instructor <br />
|Name of instructor teaching the course.<br />
|-<br />
|Instructor Email <br />
|Email of the instructor teaching the course.<br />
|-<br />
|Instructor Phone <br />
|Phone number of the instructor teaching the course.<br />
|-<br />
|Location <br />
|Physical location (i.e.: building and room number) where the course is taught.<br />
|-<br />
|Monday <br />
|Check if the course is taught on Monday.<br />
|-<br />
|Notes <br />
|Notes regarding the class schedule. The notes field is a cumulative field and date stamped with the date, time and user adding the notes.<br />
|-<br />
|Print Faculty Accommodation Notification <br />
|Use this link to print the faculty accommodation notification letter for the student. The faculty accommodation notification letter contains the instructor and course name.<br />
|-<br />
|Saturday <br />
|Check if the course is taught on Saturday.<br />
|-<br />
|Sunday <br />
|Check if the course is taught on Sunday.<br />
|-<br />
|Start Time <br />
|Time the course instruction begins.<br />
|-<br />
|Student ID <br />
|The student the class schedule is related to. Student ID is required.<br />
|-<br />
|Term <br />
|Term the student is taking the class: Fall, Winter, Spring, Summer, etc. Term is required.<br />
|-<br />
|Tuesday <br />
|Check if the course is taught on Tuesday.<br />
|-<br />
|Thursday <br />
|Check if the course is taught on Thursday<br />
|-<br />
|Wednesday <br />
|Check if the course is taught on Wednesday.<br />
|-<br />
|Year <br />
|Year the student is taking the class. Year is required.<br />
|}<br />
<br />
[[SAM V1#Tables|Back to SAM V1 Tables]]</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:import&diff=4927SAM V1:import2009-06-24T18:31:26Z<p>Ben: </p>
<hr />
<div>There are two SAM tables that could data imported from Banner: '''student and class schedules'''. The Banner data extract format can be either a [[Wikipedia:Comma-separated_values|CSV]] file or a tab-delimited text file. Ideally the end-user should be able to run the Banner extract on demand and save the data to a local file. This local file would then be loaded by the end-user into SAM using the QuickBase [http://www.quickbase.com/help/default.html#importing_data.html import data] feature. <br />
<br />
The DSP should submit a copy of the student and class schedule data fields to their Banner IT representative. From that point the Banner IT representative can assemble a script containing all students receiving disability services. Now the DSP has a list from Banner that contains all of the fields to import into SAM. The Banner IT representative should make the script into a process that the DSP can use weekly to update SAM.<br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.<br />
<br />
==Student==<br />
<br />
The Banner student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract.<br />
<br />
The SAM application contains the follow data elements for student:<br />
{| border="1" cellspacing="1" cellpadding="1"<br />
!Field Name<br />
!Data Type<br />
!Notes<br />
!Possible Banner Feed<br />
|-<br />
|Student ID<br />
|varchar<br />
|Unique Student ID (ss#/School ID)<br />
|yes<br />
|-<br />
|Status<br />
|varchar<br />
|&nbsp;<br />
|yes<br />
|- <br />
|Last Name<br />
|varchar<br />
|&nbsp;<br />
|yes<br />
|-<br />
|First Name <br />
|varchar<br />
|&nbsp; <br />
|yes<br />
|-<br />
|Middle Name <br />
|varchar<br />
|&nbsp; <br />
|yes<br />
|-<br />
|Preferred Name <br />
|varchar<br />
|The name the Student prefers<br />
|yes<br />
|-<br />
|Address<br />
|varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|City<br />
|varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|State<br />
|varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|Zip Code<br />
|varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|Alternate Address<br />
|varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|City<br />
|varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|State<br />
|varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|Zip Code<br />
|varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|Email<br />
|varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|Alternate Email<br />
|Varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|Phone Number<br />
|varchar<br />
|10 digit number without formatting is preferred<br />
|Yes<br />
|-<br />
|Phone Type<br />
|varchar<br />
|Home, Cell, Fax, etc.<br />
|Yes<br />
|-<br />
|Alternative Phone Number<br />
|varchar<br />
|10 digit number without formatting is preferred<br />
|Yes<br />
|-<br />
|Alternative Type<br />
|varchar<br />
|Home, Cell, Fax, etc.<br />
|Yes<br />
|-<br />
|Gender<br />
|varchar<br />
|Male, Female, etc.<br />
|Yes<br />
|-<br />
|Date Of Birth<br />
|date<br />
|MM/DD/YYYY<br />
|Yes<br />
|-<br />
|Ethnicity<br />
|varchar<br />
|Caucasian, African American, Hispanic, Etc.<br />
|Yes<br />
|-<br />
|US Citizen<br />
|boolean<br />
|&nbsp;<br />
|Yes/no <br />
|-<br />
|Emergency Contact Name<br />
|varchar<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Emergency Contact Phone Number<br />
|varchar<br />
|10 digit number without formatting is preferred <br />
|&nbsp;<br />
|-<br />
|Emergency Phone Type<br />
|varchar<br />
|Home, Cell, Fax, etc. <br />
|&nbsp;<br />
|-<br />
|Campus<br />
|varchar <br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Service Provider<br />
|varchar <br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Primary campus student attends<br />
|varchar<br />
|&nbsp;<br />
|&nbsp;<br />
|- <br />
|Academic Level<br />
|varchar<br />
|Freshmen, Sophomore, Junior, Senior, Graduate, etc.<br />
|Yes<br />
|-<br />
|Enrollment<br />
|varchar<br />
|Enrolled, Graduated, Transferred, Withdrawn, etc.<br />
|Yes<br />
|}<br />
<br />
<br />
'''Class Schedule'''<br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.<br />
<br />
The SAM application contains the follow data elements for class schedule:<br />
{| border="1" cellspacing="1" cellpadding="1"<br />
!Field Name<br />
!Data Type<br />
!Format<br />
!Possible Banner Feed<br />
|-<br />
|Unique Student ID (ss#)<br />
|varchar<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Term<br />
|varchar<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Year<br />
|varchar<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Course<br />
|varchar<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Description<br />
|varchar<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Instructor<br />
|varchar<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Instructor Phone<br />
|varchar<br />
|&nbsp;<br />
|&nbsp;<br />
|- <br />
|Instructor Email<br />
|varchar<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Location<br />
|varchar <br />
|&nbsp;<br />
|yes<br />
|-<br />
|Monday<br />
|boolean<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Tuesday<br />
|boolean<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Wednesday<br />
|boolean<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Thursday<br />
|boolean<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Friday<br />
|boolean<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Saturday<br />
|boolean<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Sunday<br />
|boolean<br />
|&nbsp;<br />
|yes<br />
|-<br />
|StartTime<br />
|timeofday<br />
|HH:MM AM or PM<br />
|yes<br />
|-<br />
|End time<br />
|timeofday<br />
|HH:MM AM or PM<br />
|yes<br />
|-<br />
|Notes<br />
|varchar<br />
|&nbsp;<br />
|&nbsp;<br />
|}<br />
<br />
[[Category:Reference]]</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:import&diff=4926SAM V1:import2009-06-24T18:29:53Z<p>Ben: New page: There are two SAM tables that could data imported from Banner: '''student and class schedules'''. The Banner data extract format can be either a CSV f...</p>
<hr />
<div>There are two SAM tables that could data imported from Banner: '''student and class schedules'''. The Banner data extract format can be either a [[Wikipedia:Comma-separated_values|CSV]] file or a tab-delimited text file. Ideally the end-user should be able to run the Banner extract on demand and save the data to a local file. This local file would then be loaded by the end-user into SAM using the QuickBase [http://www.quickbase.com/help/default.html#importing_data.html import data] feature. <br />
<br />
The DSP should submit a copy of the student and class schedule data fields to their Banner IT representative. From that point the Banner IT representative can assemble a script containing all students receiving disability services. Now the DSP has a list from Banner that contains all of the fields to import into SAM. The Banner IT representative should make the script into a process that the DSP can use weekly to update SAM.<br />
<br />
The Banner Student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract. <br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.<br />
<br />
==Student==<br />
<br />
The Banner student extract should contain a single row for each student. The student extract would not contain a row for every student in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only those students should be included in the extract.<br />
<br />
The SAM application contains the follow data elements for student:<br />
{| border="1" cellspacing="1" cellpadding="1"<br />
!Field Name<br />
!Data Type<br />
!Notes<br />
!Possible Banner Feed<br />
|-<br />
|Student ID<br />
|varchar<br />
|Unique Student ID (ss#/School ID)<br />
|yes<br />
|-<br />
|Status<br />
|varchar<br />
|&nbsp;<br />
|yes<br />
|- <br />
|Last Name<br />
|varchar<br />
|&nbsp;<br />
|yes<br />
|-<br />
|First Name <br />
|varchar<br />
|&nbsp; <br />
|yes<br />
|-<br />
|Middle Name <br />
|varchar<br />
|&nbsp; <br />
|yes<br />
|-<br />
|Preferred Name <br />
|varchar<br />
|The name the Student prefers<br />
|yes<br />
|-<br />
|Address<br />
|varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|City<br />
|varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|State<br />
|varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|Zip Code<br />
|varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|Alternate Address<br />
|varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|City<br />
|varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|State<br />
|varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|Zip Code<br />
|varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|Email<br />
|varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|Alternate Email<br />
|Varchar<br />
|&nbsp;<br />
|Yes<br />
|-<br />
|Phone Number<br />
|varchar<br />
|10 digit number without formatting is preferred<br />
|Yes<br />
|-<br />
|Phone Type<br />
|varchar<br />
|Home, Cell, Fax, etc.<br />
|Yes<br />
|-<br />
|Alternative Phone Number<br />
|varchar<br />
|10 digit number without formatting is preferred<br />
|Yes<br />
|-<br />
|Alternative Type<br />
|varchar<br />
|Home, Cell, Fax, etc.<br />
|Yes<br />
|-<br />
|Gender<br />
|varchar<br />
|Male, Female, etc.<br />
|Yes<br />
|-<br />
|Date Of Birth<br />
|date<br />
|MM/DD/YYYY<br />
|Yes<br />
|-<br />
|Ethnicity<br />
|varchar<br />
|Caucasian, African American, Hispanic, Etc.<br />
|Yes<br />
|-<br />
|US Citizen<br />
|boolean<br />
|&nbsp;<br />
|Yes/no <br />
|-<br />
|Emergency Contact Name<br />
|varchar<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Emergency Contact Phone Number<br />
|varchar<br />
|10 digit number without formatting is preferred <br />
|&nbsp;<br />
|-<br />
|Emergency Phone Type<br />
|varchar<br />
|Home, Cell, Fax, etc. <br />
|&nbsp;<br />
|-<br />
|Campus<br />
|varchar <br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Service Provider<br />
|varchar <br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Primary campus student attends<br />
|varchar<br />
|&nbsp;<br />
|&nbsp;<br />
|- <br />
|Academic Level<br />
|varchar<br />
|Freshmen, Sophomore, Junior, Senior, Graduate, etc.<br />
|Yes<br />
|-<br />
|Enrollment<br />
|varchar<br />
|Enrolled, Graduated, Transferred, Withdrawn, etc.<br />
|Yes<br />
|}<br />
<br />
<br />
'''Class Schedule'''<br />
<br />
The Banner class schedule extract should contain a single row for each class of a student. For example, if a student is taking three classes, there would be three rows of data, one for each class with the same student identifier. The class schedule extract would not contain a row for every student class in Banner, so a mechanism must be in place within Banner to identify or flag disability services students, as only the class schedules of those students should be included in the extract.<br />
<br />
The SAM application contains the follow data elements for class schedule:<br />
{| border="1" cellspacing="1" cellpadding="1"<br />
!Field Name<br />
!Data Type<br />
!Format<br />
!Possible Banner Feed<br />
|-<br />
|Unique Student ID (ss#)<br />
|varchar<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Term<br />
|varchar<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Year<br />
|varchar<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Course<br />
|varchar<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Description<br />
|varchar<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Instructor<br />
|varchar<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Instructor Phone<br />
|varchar<br />
|&nbsp;<br />
|&nbsp;<br />
|- <br />
|Instructor Email<br />
|varchar<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Location<br />
|varchar <br />
|&nbsp;<br />
|yes<br />
|-<br />
|Monday<br />
|boolean<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Tuesday<br />
|boolean<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Wednesday<br />
|boolean<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Thursday<br />
|boolean<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Friday<br />
|boolean<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Saturday<br />
|boolean<br />
|&nbsp;<br />
|yes<br />
|-<br />
|Sunday<br />
|boolean<br />
|&nbsp;<br />
|yes<br />
|-<br />
|StartTime<br />
|timeofday<br />
|HH:MM AM or PM<br />
|yes<br />
|-<br />
|End time<br />
|timeofday<br />
|HH:MM AM or PM<br />
|yes<br />
|-<br />
|Notes<br />
|varchar<br />
|&nbsp;<br />
|&nbsp;<br />
|}<br />
<br />
[[Category:Resources]]</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:Students&diff=4925SAM V1:Students2009-06-24T18:29:24Z<p>Ben: </p>
<hr />
<div>The student table contains information about the students that receive disability services. A student record is created one time only. The student record is considered the master or parent record. The disabilities, accommodations, consent types, referrals, case notes, tasks, test scores, and class schedules are sub-tables or child records of the student record. The relationship is many children to one parent. In other words, the student record has many disabilities, accommodations, or case notes records related to it.<br />
<br />
The student record should not be deleted without first deleting all the child records related to it. Otherwise, the child records would be orphaned. <br />
<br />
[[SAM V1#Tables|Back to SAM V1 Tables]]<br />
<br />
==Status==<br />
<br />
The status field can be the value active, inactive, or prospective. It is used to determine if the student is using disability services.<br />
<br />
The status field can be reset to inactive for all students at the beginning of each term. Then, as service providers work with students, the status field would be changed to active. By doing so, it would be possible to determine which students are active for the current term. <br />
<br />
==Fields==<br />
<br />
The fields of the students table are:<br />
<br />
{| border="1" cellspacing="1" cellpadding="1"<br />
!Field<br />
!Description<br />
|-<br />
|Date Created <br />
|Date record was created.<br />
|-<br />
|Date Modified <br />
|Date record was last updated.<br />
|-<br />
|Student ID# <br />
|Unique ID# of the record.<br />
|-<br />
|Record Owner <br />
|User who owns the record.<br />
|-<br />
|Last Modified By <br />
|User who last modified the record.<br />
|-<br />
|Academic Level <br />
|Academic Level of student: Freshman, Sophomore, Junior, Senior, Graduate, etc.<br />
|-<br />
|Address <br />
|Address of student. Format is address, city, state and zip code.<br />
|-<br />
|Alternate Address <br />
|Alternate address of student. Format is address, city, state and zip code.<br />
|-<br />
|Alternate Email <br />
|Alternative email address of student.<br />
|-<br />
|Alternate Phone <br />
|Alternate phone number of student.<br />
|-<br />
|Alternate Phone Type <br />
|Type of alternative phone number: Home, Cell, Fax, etc.<br />
|-<br />
|Campus <br />
|The primary campus the student attends.<br />
|-<br />
|Date of Birth <br />
|Date of birth of student.<br />
|-<br />
|Email <br />
|Email address of student.<br />
|-<br />
|Enrollment <br />
|Enrollment status of the student: Enrolled, Graduated, Transferred, Withdrawn, etc.<br />
|-<br />
|Ethnicity <br />
|Ethnicity of student: Caucasian, African American, Hispanic, etc.<br />
|-<br />
|First Name <br />
|First name of student. First Name is required.<br />
|-<br />
|Gender <br />
|Gender of student: Male, Female, etc.<br />
|-<br />
|ID <br />
|Unique student identifier. This field could contain university identification number, social security number, or something similar. ID is required.<br />
|-<br />
|Last Name <br />
|Last name of student. Last Name is required.<br />
|-<br />
|Middle Name <br />
|Middle name of student.<br />
|-<br />
|Name <br />
|Formula field that is the concatenation of Last Name, First Name and Middle Name.<br />
|-<br />
|NEON Student <br />
|The NEON student that corresponds to the SAM student. A SAM student is created in NEON if the SAM student receives AMAC services.<br />
|-<br />
|NEON Student Data Out of Synch <br />
|Checkbox that is checked if the student data in NEON does not match the student data in SAM. SAM is considered the authoritative source. SAM and NEON student data must be kept in synch manually.<br />
|-<br />
|Notes <br />
|Notes regarding the student. The notes field is a cumulative field and date stamped with the date, time and user adding the notes.<br />
|-<br />
|Phone <br />
|Phone number of student.<br />
|-<br />
|Phone Type <br />
|Type of phone number: Home, Cell, Fax, etc.<br />
|-<br />
|Preferred Name <br />
|The name the student prefers to go by.<br />
|-<br />
|Print Accommodation Notification <br />
|Use this link to print the general accommodation notification letter for the student. The general accommodation notification letter does not include the instructor and course name.<br />
|-<br />
|Service Provider <br />
|The service provider assigned to the student.<br />
|-<br />
|Status <br />
|Student status: Active, Inactive, Prospective. Status is required. The default value is Active.<br />
|-<br />
|US Citizen <br />
|Checkbox to be checked if student is a citizen of the USA.<br />
|-<br />
|Why NEON Student Data Out of Synch <br />
|A list of fields where the SAM student data does not match the NEON student data. Identifies which fields needs to be addressed in order for SAM and NEON student data to match.<br />
|}<br />
<br />
=='''Banner'''== <br />
<br />
How to [[SAM V1:import|import]] information into SAMV1.<br />
<br />
=='''PeopleSoft'''==<br />
<br />
To synchronize PeopleSoft data with SAM data, you will perform an [http://www.quickbase.com/help/default.html#importing_data.html import data] of a flat .txt or .csv file into SAM. The flat file is essentially the data file provided by PeopleSoft, but with an additional column pre-pended to each row that uniquely identifies the student record in SAM. The additional column is the unique SAM key field Student ID#. <br />
<br />
Either the Microsoft Access application ps2sam.mdb or the PeopleSoft to SAM Web Conversion Utility can be used to append the Student ID# to the PeopleSoft data file. <br />
<br />
With the addition of the Student ID# column, the import of data into SAM then becomes an update import and updates records in SAM rather than creating new records. If the Student ID# value in the data file row exists within SAM, then the imported row of data updates the existing record in SAM. If the Student ID# value in the data file row does not exist within SAM, then the imported row of data creates a new student record in SAM during the import.<br />
Source Data<br />
<br />
===Source Data===<br />
<br />
====<u>PeopleSoft</u>====<br />
<br />
The data file received from PeopleSoft is a Microsoft Excel file consisting of a row for each student.<br />
<br />
====<u>SAM</u>====<br />
<br />
In SAM, the structure of the student table contains most of the fields referenced in the PeopleSoft file, plus many more. There are fields for Student ID, First Name, Last Name, Address1, Address2, City, State, Zip Code, Email, Phone Number, Academic Level, and Business Plan. However, Student ID is not the key field in SAM. Instead, SAM contains a unique key field on each student record called Student ID#. It is an auto-assigned integer value that is meaningless other than uniquely identifying the student record. To locate or update a student record in SAM, you use the Student ID#.<br />
<br />
====<u>Mapping</u>====<br />
<br />
{| class="wikitable" border="1"<br />
|- <br />
! PeopleSoft File Column !! SAM Student Table field !! Notes<br />
|-<br />
| Student Group Effective Date || &nbsp; || &nbsp;<br />
|-<br />
| Student Group Status || Status || A = ACTIVE, I = INACTIVE<br />
|-<br />
| PeopleSoft ID || Student ID || &nbsp;<br />
|-<br />
| Last Name || Last Name || &nbsp;<br />
|-<br />
| First Name || First Name || &nbsp;<br />
|-<br />
| Middle Name || Middle Name || &nbsp;<br />
|-<br />
| Address || Address1 || &nbsp;<br />
|-<br />
| City || City || &nbsp;<br />
|-<br />
| State || State || &nbsp;<br />
|-<br />
| Postal Code || Zip || &nbsp; <br />
|-<br />
| Preferred Phone Number || Phone || Formatting removed<br />
|-<br />
| Alternate Phone Number || Alternate Phone || Formatting removed<br />
|-<br />
| Alternate Phone Type || Alternate Phone Type || &nbsp;<br />
|-<br />
| Email || Email || &nbsp;<br />
|-<br />
| Ethnic Grp || Ethnicity || &nbsp;<br />
|-<br />
| Gender || Gender || M = MALE, F = FEMALE<br />
|-<br />
| DOB || Date of Birth || &nbsp; <br />
|-<br />
| Cum GPA || &nbsp; || &nbsp;<br />
|-<br />
| Academic Level || Academic Level || &nbsp;<br />
|-<br />
| Plan Code || Business Plan || &nbsp;<br />
|-<br />
| ERRS DSSVD Code || ERSS – D Code || &nbsp;<br />
|-<br />
| ERRS DSSPS Code || ERSS – A Code || &nbsp;<br />
|}<br />
<br />
===Building the SAM Import File using Microsoft Access===<br />
<br />
A Microsoft Access application can be used to compare the PeopleSoft and SAM Student files and generate a flat .txt file that can be imported into SAM.<br />
<br />
Using the Microsoft Access application assumes the following:<br />
<br />
# The PeopleSoft data file will not contain the SAM Student ID#.<br />
# You are manually maintaining the Student ID in SAM.<br />
# If there is not a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will be inserted to SAM.<br />
# If there is a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will update the SAM row.<br />
<br />
The Access application contains the following objects:<br />
<br />
Tables:<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
| PeopleSoft || A link table to the PeopleSoft flat file.<br />
|-<br />
| Students || A link table to the SAM export student table flat file.<br />
|}<br />
<br />
You want your tables to be link tables so that all you need to do is replace the underlying files to refresh the table data.<br />
<br />
Queries:<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
|Matched Query || A query that joins PeopleSoft to SAM using Student ID that selects all PeopleSoft rows and only the SAM rows where there is a match. The output columns are the SAM Student ID# and the columns from the PeopleSoft file that map to the columns in the SAM student table. The status column is changed from A or I to ACTIVE or INACTIVE. The phone number columns have formatting removed. The gender column is changed from M or F to MALE or FEMALE. These are the rows that need to be updated or imported in SAM using the PeopleSoft data.<br />
|}<br />
<br />
Macros:<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
| Matched Query Export || A macro that runs and exports the match query.<br />
|}<br />
<br />
====<u>Process</u>====<br />
<br />
The following process assumes the following:<br />
<br />
* The PeopleSoft file is called peoplesoft.xls.<br />
* The SAM student export is called Students.txt.<br />
* The Microsoft Access application is called ps2sam.mdb.<br />
* The match query output file is called Matched Query.xls.<br />
* The files and Microsoft Access application reside in folder called peoplesoft.<br />
<br />
=====<u>Step 1</u>=====<br />
<br />
# Open the PeopleSoft file peoplesoft.xls in the folder peoplesoft.<br />
# In SAM application, use Customize, Import/Export, and export the student table as a tab-delimited file called Students.txt in the folder peoplesoft. Note that you must change the file extension from tsv to txt.<br />
<br />
=====<u>Step 2</u>=====<br />
<br />
# Open ps2sam.mdb<br />
# Run macro Matched Query Export<br />
# Save file in folder peoplesoft and call file Matched Query.xls.<br />
# Quit ps2sam.mdb<br />
<br />
=====<u>Step 3</u>=====<br />
<br />
# Open the file Matched Query.xls.<br />
# Review the file and ensure that a pending student does not already exist in SAM with a blank or different Student ID. Perhaps the student is listed in SAM with the student ID of lastname + firstname but in the PeopleSoft file their 9 digit ID number is listed. <br />
# If the student is already in SAM, you need to update the SAM Student ID and start over at step 1. If not, a duplicate SAM student record will be created if you import the query file.<br />
# Save the Matched Query.xls file as a tab delimited .txt format file. This is necessary because QuickBase cannot import an Excel file but can import a tab delimited text file.<br />
<br />
=====<u>Step 4</u>=====<br />
<br />
# In SAM application, use Customize, Import/Export, and import into the student table the Matched Query.txt file. Check the box that states the first row is a list of field names. The import should state that the import is an update import. Be careful to review the fields that the data will import into and ensure that the columns are in the correct order. Student ID# should be the first columns followed by the columns in this order: Status, Student ID, Last Name, First Name, Middle Name, Address1, City, State, Zip, Phone, Alternate Phone, Alternate Phone Type, Email, Ethnicity, Gender, Date of Birth, Academic Level, Business Plan, ERRS – D Code, ERRS – A Code.<br />
# You are not required to import all columns, but you must select to import the Student ID#. This import will update SAM student records with the PeopleSoft data.<br />
<br />
===Building the SAM Import File using the Web Utility===<br />
<br />
A web utility can be used to compare the PeopleSoft and SAM Student files and generate a flat .csv file that can be imported into SAM.<br />
<br />
The web utility assumes the following:<br />
<br />
# The PeopleSoft data file will not contain the SAM Student ID#.<br />
# You are manually maintaining the Student ID in SAM.<br />
# If there is not a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will be inserted to SAM.<br />
# If there is a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will update the SAM row.<br />
<br />
====<u>Process</u>====<br />
<br />
The following process assumes the following:<br />
<br />
* The PeopleSoft file is called peoplesoft.xls.<br />
<br />
=====<u>Step 1</u>=====<br />
<br />
# Save the PeopleSoft file peoplesoft.xls as a CSV file named peoplesoft.csv.<br />
<br />
=====<u>Step 2</u>=====<br />
<br />
# Log into the SAM application.<br />
# On the dashboard, in the toolbox, click on the PeopleSoft to SAM Conversion Utility link.<br />
<br />
=====<u>Step 3</u>=====<br />
<br />
# Attach the peoplesoft.csv file.<br />
# Select the option that you want to create a file to be imported into SAM that will update existing SAM student data as well as create new students not currently in SAM but listed in PeopleSoft.<br />
# Click the submit button. <br />
# Save the file studentimport.csv to your computer.<br />
<br />
=====<u>Step 4</u>=====<br />
<br />
# In SAM application, use Customize, Import/Export, and import into the student table the studentimport.csv file. Check the box that states the first row is a list of field names. The import should state that the import is an update import. Be careful to review the fields that the data will import into and ensure that the columns are in the correct order. Student ID# should be the first columns followed by the columns in this order: Status, Student ID, Last Name, First Name, Middle Name, Address1, City, State, Zip, Phone, Alternate Phone, Alternate Phone Type, Email, Ethnicity, Gender, Date of Birth, Academic Level, Business Plan, ERRS – D Code, ERRS – A Code.<br />
# You are not required to import all columns, but you must select to import the Student ID#. This import will update SAM student records with the PeopleSoft data.<br />
<br />
===Further Reading===<br />
<br />
[http://www.quickbase.com/help/default.html#importing_data.html Import Data from Outside QuickBase]</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:Students&diff=4924SAM V1:Students2009-06-24T18:28:44Z<p>Ben: </p>
<hr />
<div>The student table contains information about the students that receive disability services. A student record is created one time only. The student record is considered the master or parent record. The disabilities, accommodations, consent types, referrals, case notes, tasks, test scores, and class schedules are sub-tables or child records of the student record. The relationship is many children to one parent. In other words, the student record has many disabilities, accommodations, or case notes records related to it.<br />
<br />
The student record should not be deleted without first deleting all the child records related to it. Otherwise, the child records would be orphaned. <br />
<br />
[[SAM V1#Tables|Back to SAM V1 Tables]]<br />
<br />
==Status==<br />
<br />
The status field can be the value active, inactive, or prospective. It is used to determine if the student is using disability services.<br />
<br />
The status field can be reset to inactive for all students at the beginning of each term. Then, as service providers work with students, the status field would be changed to active. By doing so, it would be possible to determine which students are active for the current term. <br />
<br />
==Fields==<br />
<br />
The fields of the students table are:<br />
<br />
{| border="1" cellspacing="1" cellpadding="1"<br />
!Field<br />
!Description<br />
|-<br />
|Date Created <br />
|Date record was created.<br />
|-<br />
|Date Modified <br />
|Date record was last updated.<br />
|-<br />
|Student ID# <br />
|Unique ID# of the record.<br />
|-<br />
|Record Owner <br />
|User who owns the record.<br />
|-<br />
|Last Modified By <br />
|User who last modified the record.<br />
|-<br />
|Academic Level <br />
|Academic Level of student: Freshman, Sophomore, Junior, Senior, Graduate, etc.<br />
|-<br />
|Address <br />
|Address of student. Format is address, city, state and zip code.<br />
|-<br />
|Alternate Address <br />
|Alternate address of student. Format is address, city, state and zip code.<br />
|-<br />
|Alternate Email <br />
|Alternative email address of student.<br />
|-<br />
|Alternate Phone <br />
|Alternate phone number of student.<br />
|-<br />
|Alternate Phone Type <br />
|Type of alternative phone number: Home, Cell, Fax, etc.<br />
|-<br />
|Campus <br />
|The primary campus the student attends.<br />
|-<br />
|Date of Birth <br />
|Date of birth of student.<br />
|-<br />
|Email <br />
|Email address of student.<br />
|-<br />
|Enrollment <br />
|Enrollment status of the student: Enrolled, Graduated, Transferred, Withdrawn, etc.<br />
|-<br />
|Ethnicity <br />
|Ethnicity of student: Caucasian, African American, Hispanic, etc.<br />
|-<br />
|First Name <br />
|First name of student. First Name is required.<br />
|-<br />
|Gender <br />
|Gender of student: Male, Female, etc.<br />
|-<br />
|ID <br />
|Unique student identifier. This field could contain university identification number, social security number, or something similar. ID is required.<br />
|-<br />
|Last Name <br />
|Last name of student. Last Name is required.<br />
|-<br />
|Middle Name <br />
|Middle name of student.<br />
|-<br />
|Name <br />
|Formula field that is the concatenation of Last Name, First Name and Middle Name.<br />
|-<br />
|NEON Student <br />
|The NEON student that corresponds to the SAM student. A SAM student is created in NEON if the SAM student receives AMAC services.<br />
|-<br />
|NEON Student Data Out of Synch <br />
|Checkbox that is checked if the student data in NEON does not match the student data in SAM. SAM is considered the authoritative source. SAM and NEON student data must be kept in synch manually.<br />
|-<br />
|Notes <br />
|Notes regarding the student. The notes field is a cumulative field and date stamped with the date, time and user adding the notes.<br />
|-<br />
|Phone <br />
|Phone number of student.<br />
|-<br />
|Phone Type <br />
|Type of phone number: Home, Cell, Fax, etc.<br />
|-<br />
|Preferred Name <br />
|The name the student prefers to go by.<br />
|-<br />
|Print Accommodation Notification <br />
|Use this link to print the general accommodation notification letter for the student. The general accommodation notification letter does not include the instructor and course name.<br />
|-<br />
|Service Provider <br />
|The service provider assigned to the student.<br />
|-<br />
|Status <br />
|Student status: Active, Inactive, Prospective. Status is required. The default value is Active.<br />
|-<br />
|US Citizen <br />
|Checkbox to be checked if student is a citizen of the USA.<br />
|-<br />
|Why NEON Student Data Out of Synch <br />
|A list of fields where the SAM student data does not match the NEON student data. Identifies which fields needs to be addressed in order for SAM and NEON student data to match.<br />
|}<br />
<br />
=='''Banner'''== <br />
<br />
How to [[SAM V1:import|import]] information for SAMV1.<br />
<br />
=='''PeopleSoft'''==<br />
<br />
To synchronize PeopleSoft data with SAM data, you will perform an [http://www.quickbase.com/help/default.html#importing_data.html import data] of a flat .txt or .csv file into SAM. The flat file is essentially the data file provided by PeopleSoft, but with an additional column pre-pended to each row that uniquely identifies the student record in SAM. The additional column is the unique SAM key field Student ID#. <br />
<br />
Either the Microsoft Access application ps2sam.mdb or the PeopleSoft to SAM Web Conversion Utility can be used to append the Student ID# to the PeopleSoft data file. <br />
<br />
With the addition of the Student ID# column, the import of data into SAM then becomes an update import and updates records in SAM rather than creating new records. If the Student ID# value in the data file row exists within SAM, then the imported row of data updates the existing record in SAM. If the Student ID# value in the data file row does not exist within SAM, then the imported row of data creates a new student record in SAM during the import.<br />
Source Data<br />
<br />
===Source Data===<br />
<br />
====<u>PeopleSoft</u>====<br />
<br />
The data file received from PeopleSoft is a Microsoft Excel file consisting of a row for each student.<br />
<br />
====<u>SAM</u>====<br />
<br />
In SAM, the structure of the student table contains most of the fields referenced in the PeopleSoft file, plus many more. There are fields for Student ID, First Name, Last Name, Address1, Address2, City, State, Zip Code, Email, Phone Number, Academic Level, and Business Plan. However, Student ID is not the key field in SAM. Instead, SAM contains a unique key field on each student record called Student ID#. It is an auto-assigned integer value that is meaningless other than uniquely identifying the student record. To locate or update a student record in SAM, you use the Student ID#.<br />
<br />
====<u>Mapping</u>====<br />
<br />
{| class="wikitable" border="1"<br />
|- <br />
! PeopleSoft File Column !! SAM Student Table field !! Notes<br />
|-<br />
| Student Group Effective Date || &nbsp; || &nbsp;<br />
|-<br />
| Student Group Status || Status || A = ACTIVE, I = INACTIVE<br />
|-<br />
| PeopleSoft ID || Student ID || &nbsp;<br />
|-<br />
| Last Name || Last Name || &nbsp;<br />
|-<br />
| First Name || First Name || &nbsp;<br />
|-<br />
| Middle Name || Middle Name || &nbsp;<br />
|-<br />
| Address || Address1 || &nbsp;<br />
|-<br />
| City || City || &nbsp;<br />
|-<br />
| State || State || &nbsp;<br />
|-<br />
| Postal Code || Zip || &nbsp; <br />
|-<br />
| Preferred Phone Number || Phone || Formatting removed<br />
|-<br />
| Alternate Phone Number || Alternate Phone || Formatting removed<br />
|-<br />
| Alternate Phone Type || Alternate Phone Type || &nbsp;<br />
|-<br />
| Email || Email || &nbsp;<br />
|-<br />
| Ethnic Grp || Ethnicity || &nbsp;<br />
|-<br />
| Gender || Gender || M = MALE, F = FEMALE<br />
|-<br />
| DOB || Date of Birth || &nbsp; <br />
|-<br />
| Cum GPA || &nbsp; || &nbsp;<br />
|-<br />
| Academic Level || Academic Level || &nbsp;<br />
|-<br />
| Plan Code || Business Plan || &nbsp;<br />
|-<br />
| ERRS DSSVD Code || ERSS – D Code || &nbsp;<br />
|-<br />
| ERRS DSSPS Code || ERSS – A Code || &nbsp;<br />
|}<br />
<br />
===Building the SAM Import File using Microsoft Access===<br />
<br />
A Microsoft Access application can be used to compare the PeopleSoft and SAM Student files and generate a flat .txt file that can be imported into SAM.<br />
<br />
Using the Microsoft Access application assumes the following:<br />
<br />
# The PeopleSoft data file will not contain the SAM Student ID#.<br />
# You are manually maintaining the Student ID in SAM.<br />
# If there is not a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will be inserted to SAM.<br />
# If there is a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will update the SAM row.<br />
<br />
The Access application contains the following objects:<br />
<br />
Tables:<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
| PeopleSoft || A link table to the PeopleSoft flat file.<br />
|-<br />
| Students || A link table to the SAM export student table flat file.<br />
|}<br />
<br />
You want your tables to be link tables so that all you need to do is replace the underlying files to refresh the table data.<br />
<br />
Queries:<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
|Matched Query || A query that joins PeopleSoft to SAM using Student ID that selects all PeopleSoft rows and only the SAM rows where there is a match. The output columns are the SAM Student ID# and the columns from the PeopleSoft file that map to the columns in the SAM student table. The status column is changed from A or I to ACTIVE or INACTIVE. The phone number columns have formatting removed. The gender column is changed from M or F to MALE or FEMALE. These are the rows that need to be updated or imported in SAM using the PeopleSoft data.<br />
|}<br />
<br />
Macros:<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
| Matched Query Export || A macro that runs and exports the match query.<br />
|}<br />
<br />
====<u>Process</u>====<br />
<br />
The following process assumes the following:<br />
<br />
* The PeopleSoft file is called peoplesoft.xls.<br />
* The SAM student export is called Students.txt.<br />
* The Microsoft Access application is called ps2sam.mdb.<br />
* The match query output file is called Matched Query.xls.<br />
* The files and Microsoft Access application reside in folder called peoplesoft.<br />
<br />
=====<u>Step 1</u>=====<br />
<br />
# Open the PeopleSoft file peoplesoft.xls in the folder peoplesoft.<br />
# In SAM application, use Customize, Import/Export, and export the student table as a tab-delimited file called Students.txt in the folder peoplesoft. Note that you must change the file extension from tsv to txt.<br />
<br />
=====<u>Step 2</u>=====<br />
<br />
# Open ps2sam.mdb<br />
# Run macro Matched Query Export<br />
# Save file in folder peoplesoft and call file Matched Query.xls.<br />
# Quit ps2sam.mdb<br />
<br />
=====<u>Step 3</u>=====<br />
<br />
# Open the file Matched Query.xls.<br />
# Review the file and ensure that a pending student does not already exist in SAM with a blank or different Student ID. Perhaps the student is listed in SAM with the student ID of lastname + firstname but in the PeopleSoft file their 9 digit ID number is listed. <br />
# If the student is already in SAM, you need to update the SAM Student ID and start over at step 1. If not, a duplicate SAM student record will be created if you import the query file.<br />
# Save the Matched Query.xls file as a tab delimited .txt format file. This is necessary because QuickBase cannot import an Excel file but can import a tab delimited text file.<br />
<br />
=====<u>Step 4</u>=====<br />
<br />
# In SAM application, use Customize, Import/Export, and import into the student table the Matched Query.txt file. Check the box that states the first row is a list of field names. The import should state that the import is an update import. Be careful to review the fields that the data will import into and ensure that the columns are in the correct order. Student ID# should be the first columns followed by the columns in this order: Status, Student ID, Last Name, First Name, Middle Name, Address1, City, State, Zip, Phone, Alternate Phone, Alternate Phone Type, Email, Ethnicity, Gender, Date of Birth, Academic Level, Business Plan, ERRS – D Code, ERRS – A Code.<br />
# You are not required to import all columns, but you must select to import the Student ID#. This import will update SAM student records with the PeopleSoft data.<br />
<br />
===Building the SAM Import File using the Web Utility===<br />
<br />
A web utility can be used to compare the PeopleSoft and SAM Student files and generate a flat .csv file that can be imported into SAM.<br />
<br />
The web utility assumes the following:<br />
<br />
# The PeopleSoft data file will not contain the SAM Student ID#.<br />
# You are manually maintaining the Student ID in SAM.<br />
# If there is not a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will be inserted to SAM.<br />
# If there is a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will update the SAM row.<br />
<br />
====<u>Process</u>====<br />
<br />
The following process assumes the following:<br />
<br />
* The PeopleSoft file is called peoplesoft.xls.<br />
<br />
=====<u>Step 1</u>=====<br />
<br />
# Save the PeopleSoft file peoplesoft.xls as a CSV file named peoplesoft.csv.<br />
<br />
=====<u>Step 2</u>=====<br />
<br />
# Log into the SAM application.<br />
# On the dashboard, in the toolbox, click on the PeopleSoft to SAM Conversion Utility link.<br />
<br />
=====<u>Step 3</u>=====<br />
<br />
# Attach the peoplesoft.csv file.<br />
# Select the option that you want to create a file to be imported into SAM that will update existing SAM student data as well as create new students not currently in SAM but listed in PeopleSoft.<br />
# Click the submit button. <br />
# Save the file studentimport.csv to your computer.<br />
<br />
=====<u>Step 4</u>=====<br />
<br />
# In SAM application, use Customize, Import/Export, and import into the student table the studentimport.csv file. Check the box that states the first row is a list of field names. The import should state that the import is an update import. Be careful to review the fields that the data will import into and ensure that the columns are in the correct order. Student ID# should be the first columns followed by the columns in this order: Status, Student ID, Last Name, First Name, Middle Name, Address1, City, State, Zip, Phone, Alternate Phone, Alternate Phone Type, Email, Ethnicity, Gender, Date of Birth, Academic Level, Business Plan, ERRS – D Code, ERRS – A Code.<br />
# You are not required to import all columns, but you must select to import the Student ID#. This import will update SAM student records with the PeopleSoft data.<br />
<br />
===Further Reading===<br />
<br />
[http://www.quickbase.com/help/default.html#importing_data.html Import Data from Outside QuickBase]</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:Students&diff=4923SAM V1:Students2009-06-24T18:27:50Z<p>Ben: </p>
<hr />
<div>The student table contains information about the students that receive disability services. A student record is created one time only. The student record is considered the master or parent record. The disabilities, accommodations, consent types, referrals, case notes, tasks, test scores, and class schedules are sub-tables or child records of the student record. The relationship is many children to one parent. In other words, the student record has many disabilities, accommodations, or case notes records related to it.<br />
<br />
The student record should not be deleted without first deleting all the child records related to it. Otherwise, the child records would be orphaned. <br />
<br />
[[SAM V1#Tables|Back to SAM V1 Tables]]<br />
<br />
==Status==<br />
<br />
The status field can be the value active, inactive, or prospective. It is used to determine if the student is using disability services.<br />
<br />
The status field can be reset to inactive for all students at the beginning of each term. Then, as service providers work with students, the status field would be changed to active. By doing so, it would be possible to determine which students are active for the current term. <br />
<br />
==Fields==<br />
<br />
The fields of the students table are:<br />
<br />
{| border="1" cellspacing="1" cellpadding="1"<br />
!Field<br />
!Description<br />
|-<br />
|Date Created <br />
|Date record was created.<br />
|-<br />
|Date Modified <br />
|Date record was last updated.<br />
|-<br />
|Student ID# <br />
|Unique ID# of the record.<br />
|-<br />
|Record Owner <br />
|User who owns the record.<br />
|-<br />
|Last Modified By <br />
|User who last modified the record.<br />
|-<br />
|Academic Level <br />
|Academic Level of student: Freshman, Sophomore, Junior, Senior, Graduate, etc.<br />
|-<br />
|Address <br />
|Address of student. Format is address, city, state and zip code.<br />
|-<br />
|Alternate Address <br />
|Alternate address of student. Format is address, city, state and zip code.<br />
|-<br />
|Alternate Email <br />
|Alternative email address of student.<br />
|-<br />
|Alternate Phone <br />
|Alternate phone number of student.<br />
|-<br />
|Alternate Phone Type <br />
|Type of alternative phone number: Home, Cell, Fax, etc.<br />
|-<br />
|Campus <br />
|The primary campus the student attends.<br />
|-<br />
|Date of Birth <br />
|Date of birth of student.<br />
|-<br />
|Email <br />
|Email address of student.<br />
|-<br />
|Enrollment <br />
|Enrollment status of the student: Enrolled, Graduated, Transferred, Withdrawn, etc.<br />
|-<br />
|Ethnicity <br />
|Ethnicity of student: Caucasian, African American, Hispanic, etc.<br />
|-<br />
|First Name <br />
|First name of student. First Name is required.<br />
|-<br />
|Gender <br />
|Gender of student: Male, Female, etc.<br />
|-<br />
|ID <br />
|Unique student identifier. This field could contain university identification number, social security number, or something similar. ID is required.<br />
|-<br />
|Last Name <br />
|Last name of student. Last Name is required.<br />
|-<br />
|Middle Name <br />
|Middle name of student.<br />
|-<br />
|Name <br />
|Formula field that is the concatenation of Last Name, First Name and Middle Name.<br />
|-<br />
|NEON Student <br />
|The NEON student that corresponds to the SAM student. A SAM student is created in NEON if the SAM student receives AMAC services.<br />
|-<br />
|NEON Student Data Out of Synch <br />
|Checkbox that is checked if the student data in NEON does not match the student data in SAM. SAM is considered the authoritative source. SAM and NEON student data must be kept in synch manually.<br />
|-<br />
|Notes <br />
|Notes regarding the student. The notes field is a cumulative field and date stamped with the date, time and user adding the notes.<br />
|-<br />
|Phone <br />
|Phone number of student.<br />
|-<br />
|Phone Type <br />
|Type of phone number: Home, Cell, Fax, etc.<br />
|-<br />
|Preferred Name <br />
|The name the student prefers to go by.<br />
|-<br />
|Print Accommodation Notification <br />
|Use this link to print the general accommodation notification letter for the student. The general accommodation notification letter does not include the instructor and course name.<br />
|-<br />
|Service Provider <br />
|The service provider assigned to the student.<br />
|-<br />
|Status <br />
|Student status: Active, Inactive, Prospective. Status is required. The default value is Active.<br />
|-<br />
|US Citizen <br />
|Checkbox to be checked if student is a citizen of the USA.<br />
|-<br />
|Why NEON Student Data Out of Synch <br />
|A list of fields where the SAM student data does not match the NEON student data. Identifies which fields needs to be addressed in order for SAM and NEON student data to match.<br />
|}<br />
<br />
=='''Banner'''== <br />
<br />
[[SAM V1:import|import]] information for SAMV1<br />
<br />
=='''PeopleSoft'''==<br />
<br />
To synchronize PeopleSoft data with SAM data, you will perform an [http://www.quickbase.com/help/default.html#importing_data.html import data] of a flat .txt or .csv file into SAM. The flat file is essentially the data file provided by PeopleSoft, but with an additional column pre-pended to each row that uniquely identifies the student record in SAM. The additional column is the unique SAM key field Student ID#. <br />
<br />
Either the Microsoft Access application ps2sam.mdb or the PeopleSoft to SAM Web Conversion Utility can be used to append the Student ID# to the PeopleSoft data file. <br />
<br />
With the addition of the Student ID# column, the import of data into SAM then becomes an update import and updates records in SAM rather than creating new records. If the Student ID# value in the data file row exists within SAM, then the imported row of data updates the existing record in SAM. If the Student ID# value in the data file row does not exist within SAM, then the imported row of data creates a new student record in SAM during the import.<br />
Source Data<br />
<br />
===Source Data===<br />
<br />
====<u>PeopleSoft</u>====<br />
<br />
The data file received from PeopleSoft is a Microsoft Excel file consisting of a row for each student.<br />
<br />
====<u>SAM</u>====<br />
<br />
In SAM, the structure of the student table contains most of the fields referenced in the PeopleSoft file, plus many more. There are fields for Student ID, First Name, Last Name, Address1, Address2, City, State, Zip Code, Email, Phone Number, Academic Level, and Business Plan. However, Student ID is not the key field in SAM. Instead, SAM contains a unique key field on each student record called Student ID#. It is an auto-assigned integer value that is meaningless other than uniquely identifying the student record. To locate or update a student record in SAM, you use the Student ID#.<br />
<br />
====<u>Mapping</u>====<br />
<br />
{| class="wikitable" border="1"<br />
|- <br />
! PeopleSoft File Column !! SAM Student Table field !! Notes<br />
|-<br />
| Student Group Effective Date || &nbsp; || &nbsp;<br />
|-<br />
| Student Group Status || Status || A = ACTIVE, I = INACTIVE<br />
|-<br />
| PeopleSoft ID || Student ID || &nbsp;<br />
|-<br />
| Last Name || Last Name || &nbsp;<br />
|-<br />
| First Name || First Name || &nbsp;<br />
|-<br />
| Middle Name || Middle Name || &nbsp;<br />
|-<br />
| Address || Address1 || &nbsp;<br />
|-<br />
| City || City || &nbsp;<br />
|-<br />
| State || State || &nbsp;<br />
|-<br />
| Postal Code || Zip || &nbsp; <br />
|-<br />
| Preferred Phone Number || Phone || Formatting removed<br />
|-<br />
| Alternate Phone Number || Alternate Phone || Formatting removed<br />
|-<br />
| Alternate Phone Type || Alternate Phone Type || &nbsp;<br />
|-<br />
| Email || Email || &nbsp;<br />
|-<br />
| Ethnic Grp || Ethnicity || &nbsp;<br />
|-<br />
| Gender || Gender || M = MALE, F = FEMALE<br />
|-<br />
| DOB || Date of Birth || &nbsp; <br />
|-<br />
| Cum GPA || &nbsp; || &nbsp;<br />
|-<br />
| Academic Level || Academic Level || &nbsp;<br />
|-<br />
| Plan Code || Business Plan || &nbsp;<br />
|-<br />
| ERRS DSSVD Code || ERSS – D Code || &nbsp;<br />
|-<br />
| ERRS DSSPS Code || ERSS – A Code || &nbsp;<br />
|}<br />
<br />
===Building the SAM Import File using Microsoft Access===<br />
<br />
A Microsoft Access application can be used to compare the PeopleSoft and SAM Student files and generate a flat .txt file that can be imported into SAM.<br />
<br />
Using the Microsoft Access application assumes the following:<br />
<br />
# The PeopleSoft data file will not contain the SAM Student ID#.<br />
# You are manually maintaining the Student ID in SAM.<br />
# If there is not a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will be inserted to SAM.<br />
# If there is a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will update the SAM row.<br />
<br />
The Access application contains the following objects:<br />
<br />
Tables:<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
| PeopleSoft || A link table to the PeopleSoft flat file.<br />
|-<br />
| Students || A link table to the SAM export student table flat file.<br />
|}<br />
<br />
You want your tables to be link tables so that all you need to do is replace the underlying files to refresh the table data.<br />
<br />
Queries:<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
|Matched Query || A query that joins PeopleSoft to SAM using Student ID that selects all PeopleSoft rows and only the SAM rows where there is a match. The output columns are the SAM Student ID# and the columns from the PeopleSoft file that map to the columns in the SAM student table. The status column is changed from A or I to ACTIVE or INACTIVE. The phone number columns have formatting removed. The gender column is changed from M or F to MALE or FEMALE. These are the rows that need to be updated or imported in SAM using the PeopleSoft data.<br />
|}<br />
<br />
Macros:<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
| Matched Query Export || A macro that runs and exports the match query.<br />
|}<br />
<br />
====<u>Process</u>====<br />
<br />
The following process assumes the following:<br />
<br />
* The PeopleSoft file is called peoplesoft.xls.<br />
* The SAM student export is called Students.txt.<br />
* The Microsoft Access application is called ps2sam.mdb.<br />
* The match query output file is called Matched Query.xls.<br />
* The files and Microsoft Access application reside in folder called peoplesoft.<br />
<br />
=====<u>Step 1</u>=====<br />
<br />
# Open the PeopleSoft file peoplesoft.xls in the folder peoplesoft.<br />
# In SAM application, use Customize, Import/Export, and export the student table as a tab-delimited file called Students.txt in the folder peoplesoft. Note that you must change the file extension from tsv to txt.<br />
<br />
=====<u>Step 2</u>=====<br />
<br />
# Open ps2sam.mdb<br />
# Run macro Matched Query Export<br />
# Save file in folder peoplesoft and call file Matched Query.xls.<br />
# Quit ps2sam.mdb<br />
<br />
=====<u>Step 3</u>=====<br />
<br />
# Open the file Matched Query.xls.<br />
# Review the file and ensure that a pending student does not already exist in SAM with a blank or different Student ID. Perhaps the student is listed in SAM with the student ID of lastname + firstname but in the PeopleSoft file their 9 digit ID number is listed. <br />
# If the student is already in SAM, you need to update the SAM Student ID and start over at step 1. If not, a duplicate SAM student record will be created if you import the query file.<br />
# Save the Matched Query.xls file as a tab delimited .txt format file. This is necessary because QuickBase cannot import an Excel file but can import a tab delimited text file.<br />
<br />
=====<u>Step 4</u>=====<br />
<br />
# In SAM application, use Customize, Import/Export, and import into the student table the Matched Query.txt file. Check the box that states the first row is a list of field names. The import should state that the import is an update import. Be careful to review the fields that the data will import into and ensure that the columns are in the correct order. Student ID# should be the first columns followed by the columns in this order: Status, Student ID, Last Name, First Name, Middle Name, Address1, City, State, Zip, Phone, Alternate Phone, Alternate Phone Type, Email, Ethnicity, Gender, Date of Birth, Academic Level, Business Plan, ERRS – D Code, ERRS – A Code.<br />
# You are not required to import all columns, but you must select to import the Student ID#. This import will update SAM student records with the PeopleSoft data.<br />
<br />
===Building the SAM Import File using the Web Utility===<br />
<br />
A web utility can be used to compare the PeopleSoft and SAM Student files and generate a flat .csv file that can be imported into SAM.<br />
<br />
The web utility assumes the following:<br />
<br />
# The PeopleSoft data file will not contain the SAM Student ID#.<br />
# You are manually maintaining the Student ID in SAM.<br />
# If there is not a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will be inserted to SAM.<br />
# If there is a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will update the SAM row.<br />
<br />
====<u>Process</u>====<br />
<br />
The following process assumes the following:<br />
<br />
* The PeopleSoft file is called peoplesoft.xls.<br />
<br />
=====<u>Step 1</u>=====<br />
<br />
# Save the PeopleSoft file peoplesoft.xls as a CSV file named peoplesoft.csv.<br />
<br />
=====<u>Step 2</u>=====<br />
<br />
# Log into the SAM application.<br />
# On the dashboard, in the toolbox, click on the PeopleSoft to SAM Conversion Utility link.<br />
<br />
=====<u>Step 3</u>=====<br />
<br />
# Attach the peoplesoft.csv file.<br />
# Select the option that you want to create a file to be imported into SAM that will update existing SAM student data as well as create new students not currently in SAM but listed in PeopleSoft.<br />
# Click the submit button. <br />
# Save the file studentimport.csv to your computer.<br />
<br />
=====<u>Step 4</u>=====<br />
<br />
# In SAM application, use Customize, Import/Export, and import into the student table the studentimport.csv file. Check the box that states the first row is a list of field names. The import should state that the import is an update import. Be careful to review the fields that the data will import into and ensure that the columns are in the correct order. Student ID# should be the first columns followed by the columns in this order: Status, Student ID, Last Name, First Name, Middle Name, Address1, City, State, Zip, Phone, Alternate Phone, Alternate Phone Type, Email, Ethnicity, Gender, Date of Birth, Academic Level, Business Plan, ERRS – D Code, ERRS – A Code.<br />
# You are not required to import all columns, but you must select to import the Student ID#. This import will update SAM student records with the PeopleSoft data.<br />
<br />
===Further Reading===<br />
<br />
[http://www.quickbase.com/help/default.html#importing_data.html Import Data from Outside QuickBase]</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:Students&diff=4922SAM V1:Students2009-06-24T18:26:31Z<p>Ben: </p>
<hr />
<div>The student table contains information about the students that receive disability services. A student record is created one time only. The student record is considered the master or parent record. The disabilities, accommodations, consent types, referrals, case notes, tasks, test scores, and class schedules are sub-tables or child records of the student record. The relationship is many children to one parent. In other words, the student record has many disabilities, accommodations, or case notes records related to it.<br />
<br />
The student record should not be deleted without first deleting all the child records related to it. Otherwise, the child records would be orphaned. <br />
<br />
[[SAM V1#Tables|Back to SAM V1 Tables]]<br />
<br />
==Status==<br />
<br />
The status field can be the value active, inactive, or prospective. It is used to determine if the student is using disability services.<br />
<br />
The status field can be reset to inactive for all students at the beginning of each term. Then, as service providers work with students, the status field would be changed to active. By doing so, it would be possible to determine which students are active for the current term. <br />
<br />
==Fields==<br />
<br />
The fields of the students table are:<br />
<br />
{| border="1" cellspacing="1" cellpadding="1"<br />
!Field<br />
!Description<br />
|-<br />
|Date Created <br />
|Date record was created.<br />
|-<br />
|Date Modified <br />
|Date record was last updated.<br />
|-<br />
|Student ID# <br />
|Unique ID# of the record.<br />
|-<br />
|Record Owner <br />
|User who owns the record.<br />
|-<br />
|Last Modified By <br />
|User who last modified the record.<br />
|-<br />
|Academic Level <br />
|Academic Level of student: Freshman, Sophomore, Junior, Senior, Graduate, etc.<br />
|-<br />
|Address <br />
|Address of student. Format is address, city, state and zip code.<br />
|-<br />
|Alternate Address <br />
|Alternate address of student. Format is address, city, state and zip code.<br />
|-<br />
|Alternate Email <br />
|Alternative email address of student.<br />
|-<br />
|Alternate Phone <br />
|Alternate phone number of student.<br />
|-<br />
|Alternate Phone Type <br />
|Type of alternative phone number: Home, Cell, Fax, etc.<br />
|-<br />
|Campus <br />
|The primary campus the student attends.<br />
|-<br />
|Date of Birth <br />
|Date of birth of student.<br />
|-<br />
|Email <br />
|Email address of student.<br />
|-<br />
|Enrollment <br />
|Enrollment status of the student: Enrolled, Graduated, Transferred, Withdrawn, etc.<br />
|-<br />
|Ethnicity <br />
|Ethnicity of student: Caucasian, African American, Hispanic, etc.<br />
|-<br />
|First Name <br />
|First name of student. First Name is required.<br />
|-<br />
|Gender <br />
|Gender of student: Male, Female, etc.<br />
|-<br />
|ID <br />
|Unique student identifier. This field could contain university identification number, social security number, or something similar. ID is required.<br />
|-<br />
|Last Name <br />
|Last name of student. Last Name is required.<br />
|-<br />
|Middle Name <br />
|Middle name of student.<br />
|-<br />
|Name <br />
|Formula field that is the concatenation of Last Name, First Name and Middle Name.<br />
|-<br />
|NEON Student <br />
|The NEON student that corresponds to the SAM student. A SAM student is created in NEON if the SAM student receives AMAC services.<br />
|-<br />
|NEON Student Data Out of Synch <br />
|Checkbox that is checked if the student data in NEON does not match the student data in SAM. SAM is considered the authoritative source. SAM and NEON student data must be kept in synch manually.<br />
|-<br />
|Notes <br />
|Notes regarding the student. The notes field is a cumulative field and date stamped with the date, time and user adding the notes.<br />
|-<br />
|Phone <br />
|Phone number of student.<br />
|-<br />
|Phone Type <br />
|Type of phone number: Home, Cell, Fax, etc.<br />
|-<br />
|Preferred Name <br />
|The name the student prefers to go by.<br />
|-<br />
|Print Accommodation Notification <br />
|Use this link to print the general accommodation notification letter for the student. The general accommodation notification letter does not include the instructor and course name.<br />
|-<br />
|Service Provider <br />
|The service provider assigned to the student.<br />
|-<br />
|Status <br />
|Student status: Active, Inactive, Prospective. Status is required. The default value is Active.<br />
|-<br />
|US Citizen <br />
|Checkbox to be checked if student is a citizen of the USA.<br />
|-<br />
|Why NEON Student Data Out of Synch <br />
|A list of fields where the SAM student data does not match the NEON student data. Identifies which fields needs to be addressed in order for SAM and NEON student data to match.<br />
|}<br />
<br />
=='''Banner'''== [[SAM V1:import|import]] information for SAMV1<br />
<br />
=='''PeopleSoft'''==<br />
<br />
To synchronize PeopleSoft data with SAM data, you will perform an [http://www.quickbase.com/help/default.html#importing_data.html import data] of a flat .txt or .csv file into SAM. The flat file is essentially the data file provided by PeopleSoft, but with an additional column pre-pended to each row that uniquely identifies the student record in SAM. The additional column is the unique SAM key field Student ID#. <br />
<br />
Either the Microsoft Access application ps2sam.mdb or the PeopleSoft to SAM Web Conversion Utility can be used to append the Student ID# to the PeopleSoft data file. <br />
<br />
With the addition of the Student ID# column, the import of data into SAM then becomes an update import and updates records in SAM rather than creating new records. If the Student ID# value in the data file row exists within SAM, then the imported row of data updates the existing record in SAM. If the Student ID# value in the data file row does not exist within SAM, then the imported row of data creates a new student record in SAM during the import.<br />
Source Data<br />
<br />
===Source Data===<br />
<br />
====<u>PeopleSoft</u>====<br />
<br />
The data file received from PeopleSoft is a Microsoft Excel file consisting of a row for each student.<br />
<br />
====<u>SAM</u>====<br />
<br />
In SAM, the structure of the student table contains most of the fields referenced in the PeopleSoft file, plus many more. There are fields for Student ID, First Name, Last Name, Address1, Address2, City, State, Zip Code, Email, Phone Number, Academic Level, and Business Plan. However, Student ID is not the key field in SAM. Instead, SAM contains a unique key field on each student record called Student ID#. It is an auto-assigned integer value that is meaningless other than uniquely identifying the student record. To locate or update a student record in SAM, you use the Student ID#.<br />
<br />
====<u>Mapping</u>====<br />
<br />
{| class="wikitable" border="1"<br />
|- <br />
! PeopleSoft File Column !! SAM Student Table field !! Notes<br />
|-<br />
| Student Group Effective Date || &nbsp; || &nbsp;<br />
|-<br />
| Student Group Status || Status || A = ACTIVE, I = INACTIVE<br />
|-<br />
| PeopleSoft ID || Student ID || &nbsp;<br />
|-<br />
| Last Name || Last Name || &nbsp;<br />
|-<br />
| First Name || First Name || &nbsp;<br />
|-<br />
| Middle Name || Middle Name || &nbsp;<br />
|-<br />
| Address || Address1 || &nbsp;<br />
|-<br />
| City || City || &nbsp;<br />
|-<br />
| State || State || &nbsp;<br />
|-<br />
| Postal Code || Zip || &nbsp; <br />
|-<br />
| Preferred Phone Number || Phone || Formatting removed<br />
|-<br />
| Alternate Phone Number || Alternate Phone || Formatting removed<br />
|-<br />
| Alternate Phone Type || Alternate Phone Type || &nbsp;<br />
|-<br />
| Email || Email || &nbsp;<br />
|-<br />
| Ethnic Grp || Ethnicity || &nbsp;<br />
|-<br />
| Gender || Gender || M = MALE, F = FEMALE<br />
|-<br />
| DOB || Date of Birth || &nbsp; <br />
|-<br />
| Cum GPA || &nbsp; || &nbsp;<br />
|-<br />
| Academic Level || Academic Level || &nbsp;<br />
|-<br />
| Plan Code || Business Plan || &nbsp;<br />
|-<br />
| ERRS DSSVD Code || ERSS – D Code || &nbsp;<br />
|-<br />
| ERRS DSSPS Code || ERSS – A Code || &nbsp;<br />
|}<br />
<br />
===Building the SAM Import File using Microsoft Access===<br />
<br />
A Microsoft Access application can be used to compare the PeopleSoft and SAM Student files and generate a flat .txt file that can be imported into SAM.<br />
<br />
Using the Microsoft Access application assumes the following:<br />
<br />
# The PeopleSoft data file will not contain the SAM Student ID#.<br />
# You are manually maintaining the Student ID in SAM.<br />
# If there is not a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will be inserted to SAM.<br />
# If there is a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will update the SAM row.<br />
<br />
The Access application contains the following objects:<br />
<br />
Tables:<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
| PeopleSoft || A link table to the PeopleSoft flat file.<br />
|-<br />
| Students || A link table to the SAM export student table flat file.<br />
|}<br />
<br />
You want your tables to be link tables so that all you need to do is replace the underlying files to refresh the table data.<br />
<br />
Queries:<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
|Matched Query || A query that joins PeopleSoft to SAM using Student ID that selects all PeopleSoft rows and only the SAM rows where there is a match. The output columns are the SAM Student ID# and the columns from the PeopleSoft file that map to the columns in the SAM student table. The status column is changed from A or I to ACTIVE or INACTIVE. The phone number columns have formatting removed. The gender column is changed from M or F to MALE or FEMALE. These are the rows that need to be updated or imported in SAM using the PeopleSoft data.<br />
|}<br />
<br />
Macros:<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
| Matched Query Export || A macro that runs and exports the match query.<br />
|}<br />
<br />
====<u>Process</u>====<br />
<br />
The following process assumes the following:<br />
<br />
* The PeopleSoft file is called peoplesoft.xls.<br />
* The SAM student export is called Students.txt.<br />
* The Microsoft Access application is called ps2sam.mdb.<br />
* The match query output file is called Matched Query.xls.<br />
* The files and Microsoft Access application reside in folder called peoplesoft.<br />
<br />
=====<u>Step 1</u>=====<br />
<br />
# Open the PeopleSoft file peoplesoft.xls in the folder peoplesoft.<br />
# In SAM application, use Customize, Import/Export, and export the student table as a tab-delimited file called Students.txt in the folder peoplesoft. Note that you must change the file extension from tsv to txt.<br />
<br />
=====<u>Step 2</u>=====<br />
<br />
# Open ps2sam.mdb<br />
# Run macro Matched Query Export<br />
# Save file in folder peoplesoft and call file Matched Query.xls.<br />
# Quit ps2sam.mdb<br />
<br />
=====<u>Step 3</u>=====<br />
<br />
# Open the file Matched Query.xls.<br />
# Review the file and ensure that a pending student does not already exist in SAM with a blank or different Student ID. Perhaps the student is listed in SAM with the student ID of lastname + firstname but in the PeopleSoft file their 9 digit ID number is listed. <br />
# If the student is already in SAM, you need to update the SAM Student ID and start over at step 1. If not, a duplicate SAM student record will be created if you import the query file.<br />
# Save the Matched Query.xls file as a tab delimited .txt format file. This is necessary because QuickBase cannot import an Excel file but can import a tab delimited text file.<br />
<br />
=====<u>Step 4</u>=====<br />
<br />
# In SAM application, use Customize, Import/Export, and import into the student table the Matched Query.txt file. Check the box that states the first row is a list of field names. The import should state that the import is an update import. Be careful to review the fields that the data will import into and ensure that the columns are in the correct order. Student ID# should be the first columns followed by the columns in this order: Status, Student ID, Last Name, First Name, Middle Name, Address1, City, State, Zip, Phone, Alternate Phone, Alternate Phone Type, Email, Ethnicity, Gender, Date of Birth, Academic Level, Business Plan, ERRS – D Code, ERRS – A Code.<br />
# You are not required to import all columns, but you must select to import the Student ID#. This import will update SAM student records with the PeopleSoft data.<br />
<br />
===Building the SAM Import File using the Web Utility===<br />
<br />
A web utility can be used to compare the PeopleSoft and SAM Student files and generate a flat .csv file that can be imported into SAM.<br />
<br />
The web utility assumes the following:<br />
<br />
# The PeopleSoft data file will not contain the SAM Student ID#.<br />
# You are manually maintaining the Student ID in SAM.<br />
# If there is not a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will be inserted to SAM.<br />
# If there is a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will update the SAM row.<br />
<br />
====<u>Process</u>====<br />
<br />
The following process assumes the following:<br />
<br />
* The PeopleSoft file is called peoplesoft.xls.<br />
<br />
=====<u>Step 1</u>=====<br />
<br />
# Save the PeopleSoft file peoplesoft.xls as a CSV file named peoplesoft.csv.<br />
<br />
=====<u>Step 2</u>=====<br />
<br />
# Log into the SAM application.<br />
# On the dashboard, in the toolbox, click on the PeopleSoft to SAM Conversion Utility link.<br />
<br />
=====<u>Step 3</u>=====<br />
<br />
# Attach the peoplesoft.csv file.<br />
# Select the option that you want to create a file to be imported into SAM that will update existing SAM student data as well as create new students not currently in SAM but listed in PeopleSoft.<br />
# Click the submit button. <br />
# Save the file studentimport.csv to your computer.<br />
<br />
=====<u>Step 4</u>=====<br />
<br />
# In SAM application, use Customize, Import/Export, and import into the student table the studentimport.csv file. Check the box that states the first row is a list of field names. The import should state that the import is an update import. Be careful to review the fields that the data will import into and ensure that the columns are in the correct order. Student ID# should be the first columns followed by the columns in this order: Status, Student ID, Last Name, First Name, Middle Name, Address1, City, State, Zip, Phone, Alternate Phone, Alternate Phone Type, Email, Ethnicity, Gender, Date of Birth, Academic Level, Business Plan, ERRS – D Code, ERRS – A Code.<br />
# You are not required to import all columns, but you must select to import the Student ID#. This import will update SAM student records with the PeopleSoft data.<br />
<br />
===Further Reading===<br />
<br />
[http://www.quickbase.com/help/default.html#importing_data.html Import Data from Outside QuickBase]</div>Benhttps://www.amacusg.gatech.edu/wiki/index.php?title=SAM_V1:Students&diff=4921SAM V1:Students2009-06-24T18:25:58Z<p>Ben: </p>
<hr />
<div>The student table contains information about the students that receive disability services. A student record is created one time only. The student record is considered the master or parent record. The disabilities, accommodations, consent types, referrals, case notes, tasks, test scores, and class schedules are sub-tables or child records of the student record. The relationship is many children to one parent. In other words, the student record has many disabilities, accommodations, or case notes records related to it.<br />
<br />
The student record should not be deleted without first deleting all the child records related to it. Otherwise, the child records would be orphaned. <br />
<br />
[[SAM V1#Tables|Back to SAM V1 Tables]]<br />
<br />
==Status==<br />
<br />
The status field can be the value active, inactive, or prospective. It is used to determine if the student is using disability services.<br />
<br />
The status field can be reset to inactive for all students at the beginning of each term. Then, as service providers work with students, the status field would be changed to active. By doing so, it would be possible to determine which students are active for the current term. <br />
<br />
==Fields==<br />
<br />
The fields of the students table are:<br />
<br />
{| border="1" cellspacing="1" cellpadding="1"<br />
!Field<br />
!Description<br />
|-<br />
|Date Created <br />
|Date record was created.<br />
|-<br />
|Date Modified <br />
|Date record was last updated.<br />
|-<br />
|Student ID# <br />
|Unique ID# of the record.<br />
|-<br />
|Record Owner <br />
|User who owns the record.<br />
|-<br />
|Last Modified By <br />
|User who last modified the record.<br />
|-<br />
|Academic Level <br />
|Academic Level of student: Freshman, Sophomore, Junior, Senior, Graduate, etc.<br />
|-<br />
|Address <br />
|Address of student. Format is address, city, state and zip code.<br />
|-<br />
|Alternate Address <br />
|Alternate address of student. Format is address, city, state and zip code.<br />
|-<br />
|Alternate Email <br />
|Alternative email address of student.<br />
|-<br />
|Alternate Phone <br />
|Alternate phone number of student.<br />
|-<br />
|Alternate Phone Type <br />
|Type of alternative phone number: Home, Cell, Fax, etc.<br />
|-<br />
|Campus <br />
|The primary campus the student attends.<br />
|-<br />
|Date of Birth <br />
|Date of birth of student.<br />
|-<br />
|Email <br />
|Email address of student.<br />
|-<br />
|Enrollment <br />
|Enrollment status of the student: Enrolled, Graduated, Transferred, Withdrawn, etc.<br />
|-<br />
|Ethnicity <br />
|Ethnicity of student: Caucasian, African American, Hispanic, etc.<br />
|-<br />
|First Name <br />
|First name of student. First Name is required.<br />
|-<br />
|Gender <br />
|Gender of student: Male, Female, etc.<br />
|-<br />
|ID <br />
|Unique student identifier. This field could contain university identification number, social security number, or something similar. ID is required.<br />
|-<br />
|Last Name <br />
|Last name of student. Last Name is required.<br />
|-<br />
|Middle Name <br />
|Middle name of student.<br />
|-<br />
|Name <br />
|Formula field that is the concatenation of Last Name, First Name and Middle Name.<br />
|-<br />
|NEON Student <br />
|The NEON student that corresponds to the SAM student. A SAM student is created in NEON if the SAM student receives AMAC services.<br />
|-<br />
|NEON Student Data Out of Synch <br />
|Checkbox that is checked if the student data in NEON does not match the student data in SAM. SAM is considered the authoritative source. SAM and NEON student data must be kept in synch manually.<br />
|-<br />
|Notes <br />
|Notes regarding the student. The notes field is a cumulative field and date stamped with the date, time and user adding the notes.<br />
|-<br />
|Phone <br />
|Phone number of student.<br />
|-<br />
|Phone Type <br />
|Type of phone number: Home, Cell, Fax, etc.<br />
|-<br />
|Preferred Name <br />
|The name the student prefers to go by.<br />
|-<br />
|Print Accommodation Notification <br />
|Use this link to print the general accommodation notification letter for the student. The general accommodation notification letter does not include the instructor and course name.<br />
|-<br />
|Service Provider <br />
|The service provider assigned to the student.<br />
|-<br />
|Status <br />
|Student status: Active, Inactive, Prospective. Status is required. The default value is Active.<br />
|-<br />
|US Citizen <br />
|Checkbox to be checked if student is a citizen of the USA.<br />
|-<br />
|Why NEON Student Data Out of Synch <br />
|A list of fields where the SAM student data does not match the NEON student data. Identifies which fields needs to be addressed in order for SAM and NEON student data to match.<br />
|}<br />
<br />
'''Banner''' [[SAM V1:import|import]] information for SAMV1<br />
<br />
=='''PeopleSoft'''==<br />
<br />
To synchronize PeopleSoft data with SAM data, you will perform an [http://www.quickbase.com/help/default.html#importing_data.html import data] of a flat .txt or .csv file into SAM. The flat file is essentially the data file provided by PeopleSoft, but with an additional column pre-pended to each row that uniquely identifies the student record in SAM. The additional column is the unique SAM key field Student ID#. <br />
<br />
Either the Microsoft Access application ps2sam.mdb or the PeopleSoft to SAM Web Conversion Utility can be used to append the Student ID# to the PeopleSoft data file. <br />
<br />
With the addition of the Student ID# column, the import of data into SAM then becomes an update import and updates records in SAM rather than creating new records. If the Student ID# value in the data file row exists within SAM, then the imported row of data updates the existing record in SAM. If the Student ID# value in the data file row does not exist within SAM, then the imported row of data creates a new student record in SAM during the import.<br />
Source Data<br />
<br />
===Source Data===<br />
<br />
====<u>PeopleSoft</u>====<br />
<br />
The data file received from PeopleSoft is a Microsoft Excel file consisting of a row for each student.<br />
<br />
====<u>SAM</u>====<br />
<br />
In SAM, the structure of the student table contains most of the fields referenced in the PeopleSoft file, plus many more. There are fields for Student ID, First Name, Last Name, Address1, Address2, City, State, Zip Code, Email, Phone Number, Academic Level, and Business Plan. However, Student ID is not the key field in SAM. Instead, SAM contains a unique key field on each student record called Student ID#. It is an auto-assigned integer value that is meaningless other than uniquely identifying the student record. To locate or update a student record in SAM, you use the Student ID#.<br />
<br />
====<u>Mapping</u>====<br />
<br />
{| class="wikitable" border="1"<br />
|- <br />
! PeopleSoft File Column !! SAM Student Table field !! Notes<br />
|-<br />
| Student Group Effective Date || &nbsp; || &nbsp;<br />
|-<br />
| Student Group Status || Status || A = ACTIVE, I = INACTIVE<br />
|-<br />
| PeopleSoft ID || Student ID || &nbsp;<br />
|-<br />
| Last Name || Last Name || &nbsp;<br />
|-<br />
| First Name || First Name || &nbsp;<br />
|-<br />
| Middle Name || Middle Name || &nbsp;<br />
|-<br />
| Address || Address1 || &nbsp;<br />
|-<br />
| City || City || &nbsp;<br />
|-<br />
| State || State || &nbsp;<br />
|-<br />
| Postal Code || Zip || &nbsp; <br />
|-<br />
| Preferred Phone Number || Phone || Formatting removed<br />
|-<br />
| Alternate Phone Number || Alternate Phone || Formatting removed<br />
|-<br />
| Alternate Phone Type || Alternate Phone Type || &nbsp;<br />
|-<br />
| Email || Email || &nbsp;<br />
|-<br />
| Ethnic Grp || Ethnicity || &nbsp;<br />
|-<br />
| Gender || Gender || M = MALE, F = FEMALE<br />
|-<br />
| DOB || Date of Birth || &nbsp; <br />
|-<br />
| Cum GPA || &nbsp; || &nbsp;<br />
|-<br />
| Academic Level || Academic Level || &nbsp;<br />
|-<br />
| Plan Code || Business Plan || &nbsp;<br />
|-<br />
| ERRS DSSVD Code || ERSS – D Code || &nbsp;<br />
|-<br />
| ERRS DSSPS Code || ERSS – A Code || &nbsp;<br />
|}<br />
<br />
===Building the SAM Import File using Microsoft Access===<br />
<br />
A Microsoft Access application can be used to compare the PeopleSoft and SAM Student files and generate a flat .txt file that can be imported into SAM.<br />
<br />
Using the Microsoft Access application assumes the following:<br />
<br />
# The PeopleSoft data file will not contain the SAM Student ID#.<br />
# You are manually maintaining the Student ID in SAM.<br />
# If there is not a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will be inserted to SAM.<br />
# If there is a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will update the SAM row.<br />
<br />
The Access application contains the following objects:<br />
<br />
Tables:<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
| PeopleSoft || A link table to the PeopleSoft flat file.<br />
|-<br />
| Students || A link table to the SAM export student table flat file.<br />
|}<br />
<br />
You want your tables to be link tables so that all you need to do is replace the underlying files to refresh the table data.<br />
<br />
Queries:<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
|Matched Query || A query that joins PeopleSoft to SAM using Student ID that selects all PeopleSoft rows and only the SAM rows where there is a match. The output columns are the SAM Student ID# and the columns from the PeopleSoft file that map to the columns in the SAM student table. The status column is changed from A or I to ACTIVE or INACTIVE. The phone number columns have formatting removed. The gender column is changed from M or F to MALE or FEMALE. These are the rows that need to be updated or imported in SAM using the PeopleSoft data.<br />
|}<br />
<br />
Macros:<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
| Matched Query Export || A macro that runs and exports the match query.<br />
|}<br />
<br />
====<u>Process</u>====<br />
<br />
The following process assumes the following:<br />
<br />
* The PeopleSoft file is called peoplesoft.xls.<br />
* The SAM student export is called Students.txt.<br />
* The Microsoft Access application is called ps2sam.mdb.<br />
* The match query output file is called Matched Query.xls.<br />
* The files and Microsoft Access application reside in folder called peoplesoft.<br />
<br />
=====<u>Step 1</u>=====<br />
<br />
# Open the PeopleSoft file peoplesoft.xls in the folder peoplesoft.<br />
# In SAM application, use Customize, Import/Export, and export the student table as a tab-delimited file called Students.txt in the folder peoplesoft. Note that you must change the file extension from tsv to txt.<br />
<br />
=====<u>Step 2</u>=====<br />
<br />
# Open ps2sam.mdb<br />
# Run macro Matched Query Export<br />
# Save file in folder peoplesoft and call file Matched Query.xls.<br />
# Quit ps2sam.mdb<br />
<br />
=====<u>Step 3</u>=====<br />
<br />
# Open the file Matched Query.xls.<br />
# Review the file and ensure that a pending student does not already exist in SAM with a blank or different Student ID. Perhaps the student is listed in SAM with the student ID of lastname + firstname but in the PeopleSoft file their 9 digit ID number is listed. <br />
# If the student is already in SAM, you need to update the SAM Student ID and start over at step 1. If not, a duplicate SAM student record will be created if you import the query file.<br />
# Save the Matched Query.xls file as a tab delimited .txt format file. This is necessary because QuickBase cannot import an Excel file but can import a tab delimited text file.<br />
<br />
=====<u>Step 4</u>=====<br />
<br />
# In SAM application, use Customize, Import/Export, and import into the student table the Matched Query.txt file. Check the box that states the first row is a list of field names. The import should state that the import is an update import. Be careful to review the fields that the data will import into and ensure that the columns are in the correct order. Student ID# should be the first columns followed by the columns in this order: Status, Student ID, Last Name, First Name, Middle Name, Address1, City, State, Zip, Phone, Alternate Phone, Alternate Phone Type, Email, Ethnicity, Gender, Date of Birth, Academic Level, Business Plan, ERRS – D Code, ERRS – A Code.<br />
# You are not required to import all columns, but you must select to import the Student ID#. This import will update SAM student records with the PeopleSoft data.<br />
<br />
===Building the SAM Import File using the Web Utility===<br />
<br />
A web utility can be used to compare the PeopleSoft and SAM Student files and generate a flat .csv file that can be imported into SAM.<br />
<br />
The web utility assumes the following:<br />
<br />
# The PeopleSoft data file will not contain the SAM Student ID#.<br />
# You are manually maintaining the Student ID in SAM.<br />
# If there is not a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will be inserted to SAM.<br />
# If there is a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will update the SAM row.<br />
<br />
====<u>Process</u>====<br />
<br />
The following process assumes the following:<br />
<br />
* The PeopleSoft file is called peoplesoft.xls.<br />
<br />
=====<u>Step 1</u>=====<br />
<br />
# Save the PeopleSoft file peoplesoft.xls as a CSV file named peoplesoft.csv.<br />
<br />
=====<u>Step 2</u>=====<br />
<br />
# Log into the SAM application.<br />
# On the dashboard, in the toolbox, click on the PeopleSoft to SAM Conversion Utility link.<br />
<br />
=====<u>Step 3</u>=====<br />
<br />
# Attach the peoplesoft.csv file.<br />
# Select the option that you want to create a file to be imported into SAM that will update existing SAM student data as well as create new students not currently in SAM but listed in PeopleSoft.<br />
# Click the submit button. <br />
# Save the file studentimport.csv to your computer.<br />
<br />
=====<u>Step 4</u>=====<br />
<br />
# In SAM application, use Customize, Import/Export, and import into the student table the studentimport.csv file. Check the box that states the first row is a list of field names. The import should state that the import is an update import. Be careful to review the fields that the data will import into and ensure that the columns are in the correct order. Student ID# should be the first columns followed by the columns in this order: Status, Student ID, Last Name, First Name, Middle Name, Address1, City, State, Zip, Phone, Alternate Phone, Alternate Phone Type, Email, Ethnicity, Gender, Date of Birth, Academic Level, Business Plan, ERRS – D Code, ERRS – A Code.<br />
# You are not required to import all columns, but you must select to import the Student ID#. This import will update SAM student records with the PeopleSoft data.<br />
<br />
===Further Reading===<br />
<br />
[http://www.quickbase.com/help/default.html#importing_data.html Import Data from Outside QuickBase]</div>Ben