00:07: What are sis Imports?

00:09: With sis Imports. You can. Import sis

00:13: data with CSV files are automatically import via the canvas API

00:17: import CIS data. With IMS Enterprise specification.

00:20: XML zip files import CIS data with Banner

00:24: grade exchange results, XML create an automated data integration

00:29: with canvas

00:31: The sis import page supports a few formats for standard Imports.

00:34: To Canvas instructure formatted CSV or zip file of

00:38: csvs IMS Enterprise specification XML zip or

00:43: Banner grade exchange results XML.

00:46: A standard import only processes changes that are specifically listed in the upload

00:50: file and is an efficient way to upload a few records.

00:54: For example, if a student enrollment was listed as active in a prior import,

00:58: but not present in the current enrollment, no change will take place to the student

01:02: enrollment. The enrollment will remain active until marked as deleted

01:06: or completed in a standard import or is marked as not present in a full

01:10: batch update for the term where the course is listed.

01:14: During the beginning of a term horse enrollments change regularly submitting.

01:18: A standard import frequently helps keep enrollments current in an account.

01:23: When uploading sis data with CSV files, you may import an individual

01:28: CSV text file or you may compress multiple files into a single

01:32: zip file to bulk import data.

01:34: If you are using the instructor for math for importing files, the files should

01:39: be in the following order users accounts terms horses,

01:43: sections, enrollments and logins.

01:48: Canvas supports full batch updates for each import type.

01:51: This option will only affect data that has been involved in a previous CIS

01:55: job, either created by a previous import or referenced by a

01:59: sis job. After a sis ID was manually added Manually created

02:03: courses with no sis ID. For example, won't be deleted, even

02:07: if they don't appear in the new sis import.

02:11: For enrollments. This option means the linked user and course sections

02:15: require CIS. A canvas record will be deleted if it

02:19: is not included in the current import file.

02:23: This option can delete large data sets without any prompt or warning for confirmation

02:27: and effects data created in previous sis Imports.

02:31: Full batch updates are useful if Your Source, cysts

02:35: software, doesn't have a way to send delete records as part of an import and you need to

02:39: remove a fair portion of the imported data you want to be sure your current

02:43: enrollment and data set are consistent with your CIS enrollment and core data.

02:47: Your sis doesn't track changes to course state or enrollments for students

02:52: and or teachers you want to delete courses that you have migrated to Canvas

02:56: from another LMS.

02:59: If you want to run a batch against all terms in the same import, you can enable multi-term

03:03: batch mode, This mode can only be enabled in the API and

03:07: requires a change threshold as noted in the sis import format documentation.

03:13: Canvas supports user interface oui overrides through sis

03:17: Imports. When a user makes changes to certain data fields in canvas.

03:21: Eg a user's name, this change is sticky.

03:25: And as set as the new default, Selecting the override UI

03:29: option allows canvas to override any sticky data updated in the canvas UI.

03:34: Otherwise attempting an import with conflicting data would be disregarded

03:38: in the existing user data would not be changed.

03:41: To view the full list of sticky data fields, see the CIS, imported format

03:46: documentation, This option may be useful, if You

03:51: forgot to restrict user options and accounts settings such as allowing users

03:55: to change their names. Delete their institution assign email, address

03:59: Etc and you want to run an update to be sure they are in sync.

04:04: Note that this will not impact the user's display name, if they change it.

04:08: Only the full name and sortable name would be changed.

04:11: You allowed them to change their names, above example on purpose,

04:15: but want to periodically sink with your current data.

04:18: You want to maintain control over the names of users and courses.

04:22: Or if you know a name change occurred for a user or course.

04:27: Process as UI changes. This option overrides changes that have

04:31: taken place in the UI, as sticky data all data acts as if the changes

04:35: were actually manually updated in the UI.

04:39: This option may be useful, if You don't want subsequent

04:43: Imports to overwrite the data, you are currently importing.

04:47: Clear, we changed State. This option, removes the stickiness of all data

04:51: that exists in this import future Imports with this data will not indicate

04:55: any data in the uis. Sticky.

04:58: This option may be useful, if You accidentally check

05:02: the process as UI changes option and you need to fix the affected data.

05:06: You forgot to remove the ability for users to rename themselves course,

05:11: names or remove the institutional email and you want to clear the stickiness of

05:15: the UI changes that have occurred

05:18: This guide covered sis Imports.