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