Each year, I provide a report to the board that provides a high-level view of our technology program, through the lens of particular projects completed, underway, or planned. This will certainly not be the most riveting content I’ve posted to the blog, but for those of you who are interested, I’m posting a summary of that report here.
The 2016-17 school year was one of transition in the Iowa City Community School District’s Office of Technology & Innovation. As we move into winter of 2017-18, we have completed a number of major projects and still have significant initiatives underway or in planning stages. Our departmental performance metrics have generally improved slightly, though I’m excited to see how our work in terms of specific initiatives and in targeted locations will manifest itself in the coming year’s technology program evaluation. Continue reading Technology Annual Report
We experienced a number of issues yesterday morning with students being unexpectedly forced to change their passwords; we avoid this type of unanticipated password change requirement due to its clear, negative impacts on instruction. We believe that we have resolved this problem as of 10 AM yesterday morning, and have begun reviewing our policies to ensure that this does not occur again.
On a related note, we’ll be beginning work next week to update our password policy to ensure that we’re safeguarding our students and staff while making sure that accounts are accessible and easy to use. This work will be driven by newly released standards from the federal government’s National Institute of Standards and Technology (NIST); you can read the full Digital Identity Guidelines here. For a nutshell version of some of the changes between the newly-released guidelines and previous recommendations, check out this article.
I’ll be posting more information as we move ahead with the process of updating our policy.
An update to the Chrome browser caused an alert to appear when people are trying to use district webmail, along with several other district sites, in Chrome. The updated Chrome browser flags all secured (HTTPS) websites that don’t have a certificate that Google considers to be valid as unsecured.
The site will still work if you click advanced and then proceed, and is in fact encrypted and secure. We’re working on updating our security certificate with a new registrar that will remove this error in Chrome.
If you continue to have trouble opening webmail or other district sites in Chrome, please switch to Firefox or Edge, or use Microsoft Outlook to access your email.