Home of MIS2000 - We Speak Migrant


Author: Kevin Donn

Welcome Indiana!

Indiana has been our worst kept secret. Usually when we bring a new state on, I wait to send out a wecome post until we've got them all connected up with MSIX and somewhat stable. But Indiana is a special case because they're still using their old system for their MSIX connection and that may continue for quite a while yet. So I'm going to go ahead and give a belated but no less enthusiastic welcome to Emily Salinas, Adrian Martinez, and last but not least Valerie Beard who is out with her new baby right now. Adrian has probably set a record for giving me the most really thoughtful Suggestion Box entries in such a short period. Several of his ideas have already been added, and one will be going out soon. I'll probably cover it in the next post. So anyway, Wecome Indiana!

"... in your next release"

Many of you have heard us say something like, "This will go out in your next release." Whenever we do some kind of enhancement or change for your state, we'll typically "check it in" which makes it ready to be shipped out. But it may be days, weeks, or sometimes even months before it will actually show up in your production system. So you might not always know when to go looking for whatever the change was. But if you go to your MIS2000 web application, you can always see the current release date of your system. Many of you use the MIS2000 web application every day, but if you're not familiar with it, you can just go to <your state>.msedd.com to see it. For example, in Alabama you'd go to al.msedd.com. Or in Minnesota, it would be mn.msedd.com.

Field Level Change Logging

I know over the years I've found myself occasionally saying, "With more digging, I think I could work out exactly..." This usually arises after I've been asked to figure out how a student or a COE got to be the way it is. For all of the desktop and tablet machines that periodically upload, we've always had very good evidence left around about who changed what when in the form of transaction files. Everything that came in from the field could only come in through these files, so whatever happened had to be contained in them somehow. It often took a good bit of digging, but we could pinpoint exactly what happened. But for changes made directly on the state system, we couldn't depend on this mechanism since the state doesn't upload to itself. But at the state level, we always had good backups that we could rely on to let us see when things changed, and since there are very few people who have direct access to the state, we could usually work out what happened ...

Using COEs as Student Lists

This is another suggestion that came to us from Adrian Martinez in Indiana. He wanted a way to add Services for all the students on a COE. It had never struck me before, but every COE is essentially itself a list of students, so why not just expose all the functionality we currently have for Student Lists for COEs? Kind of obvious but I'd never considered it before. If you want some more blog posts on the evolution of Student Lists over the past few years, look here and here.

Email Subscription

Stay connected and receive email updates with new MS/EdD blog posts.

Authors List

Jeff Gaiche 165 9
Marcy Bolt 104 5
Kevin Donn 2050 88

Most Recent Posts

Welcome Indiana!
6/30/2020 8:02 AM | Kevin Donn
"... in your next release"
6/8/2020 3:42 PM | Kevin Donn
Field Level Change Logging
5/18/2020 4:07 PM | Kevin Donn
Using COEs as Student Lists
4/27/2020 4:29 PM | Kevin Donn
Autologout Completely Rewritten
4/6/2020 4:07 PM | Kevin Donn
Added Preferred ID to Student List Export
3/16/2020 3:18 PM | Kevin Donn
Copyright © 2020 Management Services for Education Data