What TKG Analytics Requires Before an Upload
Some uploads are turned down before any file is stored. This page lists every reason that happens, what you see, and what clears it.
The point of turning an upload down is that the alternative is worse. A score file is matched to your roster to work out which teacher and which school each score belongs to. When the roster cannot answer that, the scores are dropped and nothing tells you: the upload reports success, and the numbers simply never appear. Rather than let that happen, TKG Analytics checks first.
When you press Finish and the upload is turned down, a popup titled Your upload was not saved tells you why. For a problem in your files it lists each one on its own line. For one of the district-wide reasons below, it points you to the panel on the page.
Nothing is stored when an upload is turned down. Fix what the popup lists and upload the same files again.
Your district's rollover is underway
What you see: on the uploaders where you choose an assessment, and on the Student Information System uploader, the upload form is replaced by a panel saying uploads are paused during the rollover.
Why: a rollover changes your calendar, your school list, and your users. Until it is approved, an upload would be filed against settings that may still change, and if we send the rollover back to you for edits, the school year an upload landed in could move underneath it. Uploads that name their own year rather than choosing an assessment, such as SLAIF and MDE Impacts, are not affected and keep working, because a rollover cannot move the year they name.
What clears it: finish and submit the rollover, and wait for it to be approved. This includes a rollover you have already submitted and one we have sent back to you.
This one pauses SIS uploads too
Most reasons on this page leave the Student Information System uploader open so you can fix your roster. Three pause it instead: a rollover, because your roster is being rebuilt for the new year; onboarding, which gives you the wizard's own uploads in its place; and a paused roster feed, which is its own section below. If your roster also needs attention while a rollover is underway, open a ticket rather than waiting.
See also: After You Submit a Rollover
Your district is still being onboarded
What you see: the upload form is replaced by a panel pointing you at the onboarding wizard.
Why: onboarding imports your roster and your history, and submitting it runs that whole import again. Anything uploaded through the File Uploader in the meantime would be overwritten by that import.
What clears it: finish onboarding. This pauses the Student Information System uploader along with everything else, but the onboarding wizard's own uploads keep working the entire time, so send your roster there instead.
See also: After You Submit Onboarding
Your roster feed is paused
What you see: on the Student Information System uploader only, a panel saying roster processing is paused. Every other uploader works as usual.
Why: we pause the nightly roster feed, for one district or for every district at once, when there is nothing to collect, most often over the summer. A roster uploaded while it is paused would sit there unprocessed, so that one upload is turned down rather than left looking like it landed.
What clears it: nothing, for score files. Your state and score uploads are unaffected by the pause, which matters over the summer, when the feed is usually paused and the state files arrive. If a roster does need loading while the feed is paused, open a helpdesk ticket and we will resume it for you.
One of your SIS files is missing or empty
What you see: a panel naming the file, saying we cannot match uploaded scores to your roster.
Why: five files make up your roster: schools.csv, students.csv, teachers.csv, enrollments.csv, and schedules.csv. If one never arrived, or arrived with nothing in it, the roster is incomplete, and scores for the students it should have described are dropped.
What clears it: send a full set of the five files. You can upload them yourself through the SIS Data Upload page, and the block lifts as soon as they land. The Student Information System uploader is never blocked by this reason, so you have a way to fix it. It is paused during a rollover and during onboarding; a rollover is the case where you should open a ticket instead of waiting.
See also: SIS Files
Your SIS files arrived late or out of step
What you see: the form still works, with a warning above it and a checkbox beside the Finish button. Finish stays disabled until you tick it.
Why: the files are here and readable, so the upload may well be fine. But if your roster has not refreshed in a while, students who enrolled since then are not on it, and their scores will not import. This is a judgement you are better placed to make than we are, so you make it.
What clears it: tick the box to confirm you understand. The upload then goes through, and a confirmation email goes to you, your Superintendent, and your Point of Contact, recording what the roster looked like at the time. Sending a fresh full set of SIS files removes the warning entirely.
A single roster file sent on its own becomes your newest file, which puts the other four out of step. Send all five together.
See also: SIS Files
We have no roster data for the period you are uploading
What you see: a panel saying we hold no enrollments for that period, or no schedules for your district.
Why: enrollments say which teacher taught which student which subject, in a given period. Schedules are how we attribute scores for students in self-contained classrooms, and how acceleration is counted. Without the enrollments for the period an assessment covers, there is nothing to attach its scores to.
This most often comes up for a district that started with us partway through a year, where the roster never covered one of the earlier periods.
What clears it: send SIS files that cover the period you are uploading. The Student Information System uploader is never blocked by this reason either, so you can send them yourself. If the period is in the past and you cannot produce a roster for it, open a helpdesk ticket and we will work out what is possible.
See also: SIS Data Format
Your calendar was never advanced for the new school year
What you see: a panel saying your calendar still ends in the previous year and no rollover has been started.
Why: when you pick an assessment to upload against, the list you choose from belongs to whichever school year your calendar says you are in. If the calendar was never moved forward, that list is last year's, and scores uploaded against it are filed into a school year that has already finished.
What clears it: start your rollover, which includes advancing the calendar. Uploads that name their own year rather than choosing an assessment, such as SLAIF and MDE Impacts, are not affected and keep working.
See also: Rollover Calendar
Your benchmark ranges are not set up
What you see: a panel telling you to configure benchmark ranges first.
Why: your district scores benchmarks against its own cut scores rather than the vendor's. Without those ranges there is nothing to turn a score into a performance level, so every uploaded score arrives with no level attached.
What clears it: configure your ranges on the Benchmark Ranges page.
This reason only turns down the uploads that file scores against an assessment you pick. SLAIF, MDE Impacts, and your SIS files are not affected by it.
See also: District Defined Custom Cut Scores
Your midterm ranges are not set up
What you see: a panel telling you to configure midterm ranges, or a warning on the assessment you picked.
Why: the same reason as benchmark ranges, for midterms. A midterm scores against your midterm ranges, and importing without them produces no performance level for any row.
What clears it: configure your ranges on the Midterm Ranges page.
See also: Midterm Ranges
You have no assessments set up for this year
What you see: a panel telling you to add an assessment definition first.
Why: every score file is filed under the assessment it belongs to. With none defined for the current year, there is nothing to file it under.
What clears it: add an assessment on the Assessments page.
A benchmark score file cannot be used
What you see: a popup titled Your upload was not saved, listing each problem on its own line and naming the file it is in. A file inside a zip is named together with the zip, for example MS_MAT5_EXPORT.csv in benchmark1.zip. Every problem in every file is listed at once.
Why: these are files the import would read and then drop every score from, or would score wrongly. Turning them down while you are still on the page is better than finding the scores missing days later.
This applies to ELS and Mastery Connect benchmark uploads. Midterm files are checked when you confirm their columns; see the District Assessment Walkthrough.
| Message | What clears it |
|---|---|
| file is not a file type this upload accepts. | Upload .xlsx files for ELS, or a .zip or .xlsx for Mastery Connect. |
| file is larger than this upload's limit. | Mastery Connect files are limited to 250 MB and every other upload's files to 25 MB. The drop zone says so as soon as you add the file, before any of it is sent. Split the upload into smaller parts. |
| file has no score files, or file is not a score file. | A Mastery Connect upload needs at least one score export (_EXPORT.csv or _district_export.xlsx) or class report (_ClassReport.xlsx). Item analyses alone are not enough. See Uploading Your Mastery Connect Assessment Files. |
| file could not be read. | Upload the file as your assessment provider sent it, without opening and re-saving it. |
| file has no student ID column, score column or subject we can find. | The file is not the export we read, or its columns were renamed. See the column chart for ELS or Mastery Connect. |
| file has no students we recognize. | None of the file's first 200 student IDs is on your roster: the file may be another district's, or its ID column holds something other than MSIS numbers. |
| file has no rows with a student ID. | Every row's student ID is blank. Download the export again, or check that its student ID column is filled in. |
| file has no scores. | Every student row's score is blank. Download the export again once your assessment provider has posted the scores. |
| file has no performance levels we can read. | Where the performance level sets a student's level, none of the file's values is one we accept. Your assessment provider may not have posted levels yet. This never applies to a District Defined district. |
A file with only some rows missing a score, a student or a level is not turned down. Those rows are not imported, and the rest are.
Mastery Connect files that the import does not read, such as PDF reports, report workbooks and item response files, are skipped without a message.
Who these checks apply to
Everyone, including TKG Analytics support staff. An upload we make for you is filed against the same roster as one you make yourself, so letting ours through would drop exactly the same scores, and we would be the last to notice it had happened.
If something on this page is stopping work that cannot wait, open a helpdesk ticket and say so. Some of these are ours to clear, such as approving a rollover, and for the rest we will work out with you what is possible.