HomeStaff button Directions button Course buttonLinks buttonForms_ButtonSpotlight_GAETTC_NewslettersSchool System ServedETTC Centers button

School Systems Served

 

 

Technology Planning

Upcoming Meetings/Videoconferences
Session Location Day & Time
TBA TBA TBA

 

Videoconference Archives

Right-click and download the file to your computer. It plays with Windows Media Player.

Tech Plan Files

 

GSSIS

Upcoming Trainings
Session Location Day & Time Registration
TBA - TBA -

 
 

Cognos Training Manuals

ETL & GTID Materials and Q&A

A quick and dirty, soon-to-be-cleaned page about GSSIS and other state data projects. I feel certain this page will be revised often, since they're going to notify me whenever they change a document, etc. If you would like to be notified when it's updated, let us know.

Data Transmission, Current Standards:

Word Documents:

Powerpoints:

Answers to questions from GTID session:

1)  What is the official word on what timeline is for parallel operation? SY2006 or SY2007? What are the expectations on any state-data uploads in 2006? Is it just importing/exporting GTID?

(I asked this on Tuesday. I was told that basically this year is going to be fixing data, uploading some, but none of it the mission-critical stuff. Howard told a group 3 weeks ago otherwise, that GSSIS uploading would happen.)

Answer: GSSIS will become the system of record in SY2007.  Until then, districts will continue to use the data collection processes currently in place.  The focus of the districts will be to insure that their data is correct for the periodic data collections.  In addition to the periodic data collections, we will on approximately a monthly basis (between legacy collections), require extract data from the districts to the GSSIS Data Warehouse.  It is during these extracts that additional errors should be resolved.  By the time GSSIS becomes the system of record (July 1, 2006), data should be clean.

In a similar fashion, during SY2006, districts and schools will use the GTID system to assign GTIDs, download GTIDs into their local SIS, claim students, etc.  By the time GSSIS becomes the system of record (July 1, 2006), GTIDs should be assigned for all of a district’s students as a valid  GTID is a prerequisite for loading student data to the Data Warehouse.


2)  Code for modulus 11 to check manually inputted GTID #s?

A district wants to add code to their SIS to validate hand-entered GTID#s- can we get algorithms so they can do this?

Answer:  It is our expectation that districts will import GTIDs rather than manually entering them into the local SIS.  The Recommendations of Sub-Committee for Testing ID, dated August 26, 2004 describes the Modulus 11 calculation and is publicly available for download from the GaDOE web site.  However, there is no requirement for districts to perform modulus 11 checks.

3)  Electronic copy of 6a?

Somehow, I don't have one. May I please?

Answer:  This will be attached to the email.

4)  Why show record-errors in the bfn side of things?

When we did the upload of GTID requests, we do the '6## BFN' batch upload to show what a gross failure looks like. Not only does it tell you this, it also tells you line-by-line as if it were doing the full validation thing. They wondered why it showed that, too. There was a brief amount of panic on their parts.

Answer:  That is standard functionality of the application.  Identifying errors sooner in the process should not be cause for concern.

5)  SASI: push down GTID to systems? how? have to import at school level?

This one boils down to best practices for SASI, I think. Some of the SASI districts do not push down data to the schools- it only goes one way, from the school to the aggregator. So when you get your GTIDs back, how will you get them in?
  * If you push them from the aggregator to the schools- how?
  * If you import them at the school, do you have to break down the batch file to show only that school's students, or will it ignore the others?

Answer:  Once Districts download the GTID, it is left to the Districts to determine the best way to flow data to / from the school level.

6)  Is SSN required for uploads to GTID?

I think this is no, but I wanted an affirmation. Can I get an amen?

Answer:  Completion of the SSN field is strongly encouraged, but not required.  If the student does not have an SSN, we recommend placing the student’s 800 number in this field.  Use of this field will facilitate near match resolution and importing of GTIDs into the local SIS.

7)  Whose email address in school info?

When you show a school's info, it shows a number of things. How do they put values they want in there? Where is it getting pulled from?

Answer:  GaDOE will populate this using the email address data from the GaDOE portal.

8)  What's last Serial#?

I honestly can't remember where this was, but at one point, we got a data field that said 'Last Serial#'

Answer:  Difficult to answer without knowing where you saw this.  A screen shot would be helpful.

9)  How do we resolve mis-assigned GTID's or dupe assigned GTID's? what is the process?

Somebody's at a school, they think somebody is a new student instead of the one it's showing, and they make her a new GTID- how do we fix it 6 months down the line?

Answer:  GADOE has the capability to correct such a mistake through a System Administrator function.  This function is not available to districts.

10)  How much previous history is a student GTID search going to show?

When we did a search, we show one past school. Is that all it will show, or will it show the full history?

Answer:  Complete history is retained:  one row per GTID update.

11)  Is there going to be a way to upload no-shows & withdraws?

Answer:  Never before enrolled No shows should not be assigned a GTID.  When a new student enrolls in a GA public school for the first time, he/she should be assigned a GTID as part of the enrollment process.  Since only students who have enrolled can be withdrawn, they should have a GTID.

12)  [SIC]  Uploading withdrawn & enroll dates as means of auto-claiming?

Combined together. Basic problem is that Gwinnett is looking at lots of manual claim approvals. If they uploaded to GTID a file containing people they withdrew, and had no claim over, and somebody else uploaded that kid's GTID, it would just give it to them, no claim necessary.  Right now, it appears to work such that until a student is moved by new GTID info, he's, in effect, in perpetuity at a given grade & school.

Answer:  The current version of GTID functionality does not support the uploading of withdrawal and enrollment dates.

13)  What about intra-district claims?  End-of-year student updates and rollovers?

Change of school can trigger a claim.  Refer to “Determination of Whether a Claim is Required” diagram.
I was upset I didn't ask this question Tuesday.  I am presuming that if a district uploads GTID info that shows a person moving from school to school within the same district, no claims are filed.

Answer:  Not true.  Change of school can trigger a claim.  Refer to “Determination of Whether a Claim is Required” diagram in training materials.

Similarly, the end-of-year grade rollover for promoted students won't generate claims, right?
Based on the claim algorithm diagram, I'm not sure. It appears that rollovers are fine, as long as school doesn't change, and any change in school, period, creates a claim.

Answer:  By itself, change of grade will not trigger a claim.  Change of school is the entry point for Determination of Whether a Claim is Required.  Then a check is made for break in attendance (no claim if 2 or more years).  Finally, the boundary condition is checked (no claim if normal progression to new school based on grade range of new and former schools.)

14)  Does the GSSIS instigate a claim process?

District A doesn't update their GTID stuff once a student's in it.  Student leaves A, goes to B. They put in the value from A's transcript.  B uploads data to GSSIS. How does a claim get started that way?

Answer:  The GSSIS (Georgia Statewide Student Information System) is a whole system that consists of the GTID application and a Decision Support structure consisting of the Data Warehouse and Business Intelligence and Reporting tools.   The only application that permits the initiation of a claim is the GTID.  Conflicting data in the warehouse will not initiate a claim.