When data just can't import into the system the import logs will generate errors. Errors should be looked at, however, not all errors are bad.
An error indicates that something was wrong with the data and it was not importable. It is important to realize that an error means that the record was not imported.
What are some examples of errors?
- A row of data is missing required information.
- Data is being provided in the wrong format (dates, integers, etc.)
What is the significance of errors?
- If your imports generate any errors, they can cause some major issues.
- Remember that data errors cascade down to other imports.
- Imagine your course ID did not import because of an error.
- The course ID will cause master schedule records not to import.
- The master schedules not importing will cause roster records not to import.
- Now your students are missing classes on their schedules.
Data logs MUST BE REVIEWED.
Do all errors need to be resolved? No. Sometimes errors are a good thing. Many times in a master schedule a section is tied to a "place holder" teacher. The records don't import because the teacher doesn't exist. This is OK. You don't need to resolve this. When you update your master schedule in your SIS and assign a real teacher to the section, the data will resolve itself.
Logs do not need to indicate 0 errors and 0 warnings as long as you know what the errors or warnings are telling you.