Difference between revisions of "SAM V2:Students"

From CIDI Wiki
Jump to navigation Jump to search
Line 136: Line 136:
=='''Banner Data'''==
=='''Banner Data'''==


There are two SAM tables that have data imported from Banner: '''student and class schedules'''.  The Banner data extract format can be either a [[http://en.wikipedia.org/wiki/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.   
There are two SAM tables that have data imported from Banner: '''student and class schedules'''.  The Banner data extract format can be either a [http://en.wikipedia.org/wiki/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.   


'''EACH DSP SHOULD SUBMIT A COPY OF THE STUDENT AND CLASS SCHELULES 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.
'''EACH DSP SHOULD SUBMIT A COPY OF THE STUDENT AND CLASS SCHELULES 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.

Revision as of 08:49, 20 April 2009

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.

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.

Back to SAM V2 Tables

Status

The status field can be the value active, inactive, etc. It is used to determine if the student is using disability services.

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.

Fields

The fields of the students table are:

Field Description
academic_level Academic Level of student: Freshman, Sophomore, Junior, Senior, Graduate, etc.
address1 Address line 1 of student.
address2 Address line 2 of student.
alt_address1 Alternate address line 1 of student.
alt_address2 Alternate address line 2 of student.
alt_city Alternate address city of student.
alt_email Alternative email address of student.
alt_phone Alternate phone number of student.
alt_phone_type Type of alternative phone number: Home, Cell, Fax, etc.
alt_state Alternate address state of student.
alt_zip Alternate address zip code of the student.
campus The primary campus the student attends.
city Address city of student.
date_of_birth Date of birth of student.
emergency_contact First and last name of emergency contact of student.
emergency_contact_phone Phone number for the emegency contact of the student.
emergency_relationship Relationship of the emergency contact to the student.
email Email address of student.
enrollment Enrollment status of the student: Enrolled, Graduated, Transferred, Withdrawn, etc.
ethnicity Ethnicity of student: Caucasian, African American, Hispanic, etc.
first_name First name of student. First Name is required.
gender Gender of student: Male, Female, etc.
id Unique student identifier. This field could contain university identification number, social security number, or something similar. ID is required.
last_name Last name of student. Last Name is required.
last_updated Date record was last updated.
middle_name Middle name of student.
notes Notes pertaining to the student. These are not case notes but additional information about the student.
phone Phone number of student.
phone_type Type of phone number: Home, Cell, Fax, etc.
preferred_ame The name the student prefers to go by.
sid Unique ID# of the record.
service_provider The service provider working with or assigned to the student.
state Address state of the student.
status Student status: Active, Inactive, Prospective. Status is required. The default value is Active.
updated_by User who last modified the record.
us_citizen Checkbox to be checked if student is a citizen of the USA.
zip Address zip code of the student


Back to SAM V2 Tables

There are two SAM tables that have data imported from Banner: student and class schedules. The Banner data extract format can be either a [1] 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 import data feature.

EACH DSP SHOULD SUBMIT A COPY OF THE STUDENT AND CLASS SCHELULES 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.


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.

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.


The SAM application contains the follow data elements for student:

Field Data Type Notes Possible Banner Feed
Student ID varchar Unique Student ID (ss #) yes
Status varchar
Last Name varchar yes
First Name varchar yes
Middle Name varchar yes
Preferred Name varchar The name the student prefers to go by
Address varchar yes
City varchar yes
State varchar yes
Zip Code varchar yes
Alternate Address varchar yes
City varchar yes
State varchar yes
Zip Code varchar yes
Email varchar yes
Alternate Email varchar yes
Phone Number varchar 10 digit number without formatting is preferred
Phone Number Type varchar Home, Cell, Fax, etc.
Alternate Phone Number varhcar 10 digit number without formatting is preferred
Alternate Phone Type varchar Home, Cell, Fax, etc.
Gender varchar Male, Female, etc. yes
Date of Birth date MM/DD/YYYY yes
Ethnicity varchar Caucasian, African American, Hispanic, etc. yes
US Citizen boolean yes/no
Emergency Contact Name varchar
Emergency Contact Phone Number varchar 10 digit number without formatting is preferred
Emergency Phone Type varchar Home, Cell, Fax, etc.
Campus varchar
Service Provider varchar
Primary campus student attends varchar
Academic Level varchar Freshman, Sophomore, Junior, Senior, Graduate, etc. yes
Enrollment varchar Enrolled, Graduated, Transferred, Withdrawn, etc. yes


Back to SAM V2 Tables

PeopleSoft

Instructions on Synchronizing PeopleSoft and SAM Student Data

To synchronize PeopleSoft data with SAM data, you will perform an import data of a flat .txt 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#.

The Microsoft Access application ps2sam.mdb is used to append the Student ID# to the PeopleSoft data file.

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. Source Data

The data file received from PeopleSoft is a Microsoft Excel file consisting of a row for each student.

SAM

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#.

Mapping

PeopleSoft File Column SAM Student Table field Notes Student Group Effective Date Student Group Status Status A = ACTIVE, I = INACTIVE PeopleSoft ID Student ID Last Name Last Name First Name First Name Middle Name Middle Name Address Address1 City City State State Postal Code Zip Preferred Phone Number Phone Formatting removed Alternate Phone Number Alternate Phone Formatting removed Alternate Phone Type Alternate Phone Type Email Email Ethnic Grp Ethnicity Gender Gender M = MALE, F = FEMALE DOB Date of Birth Cum GPA Academic Level Academic Level Plan Business Plan ERRS DSSVD Code ERSS – D Code ERRS DSSPS Code ERSS – A Code

Cross-Referencing or Building the SAM Import Files

The below process is used to pull PeopleSoft data into SAM. It assumes the following:

1. The PeopleSoft data file will not contain the SAM Student ID#. 2. You are manually maintaining the Student ID in SAM. 3. If there is not a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will be inserted to SAM. 4. If there is a match on Student ID between SAM and PeopleSoft, the PeopleSoft row will update the SAM row.

A Microsoft Access application is used to compare the files and generate two flat files that can be imported into SAM.

Microsoft Access Application

The Access application contains the following objects:

Tables:

PeopleSoft A link table to the PeopleSoft flat file Students A link table to the SAM export student table flat file.

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.

Queries:

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.

Macros:

Matched Query Export A macro that runs and exports the match query. Process

The following process assumes the following:

• The PeopleSoft file is called peoplesoft.xls. • The SAM student export is called Students.txt. • The Microsoft Access application is called ps2sam.mdb. • The match query output file is called Matched Query.xls. • The files and Microsoft Access application reside in folder called peoplesoft.

Step 1

1. Open the PeopleSoft file peoplesoft.xls in the folder peoplesoft. 2. 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.

Step 2

1. Open ps2sam.mdb 2. Run macro Matched Query Export 3. Save file in folder peoplesoft and call file Matched Query.xls. 4. Quit ps2sam.mdb

Step 3

1. Open the file Matched Query.xls. 2. 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. 3. 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. 4. 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.

Step 4

1. 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. 2. 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.


Back to SAM V2 Tables

Digger

Digger is the easiest import data that can be incorporated into SAM V1. Digger exports into an excel spread sheet which then can be imported into SAM V1.