The first script I ever used was one which would send the results of a form to someone other than the person submitting it. I found it online, changed the email address, and made it work. That looks pretty simple now, but it started me on a journey which has led me to my current place in learning programming.
We have started using scripts (which are bound to Google spreadsheets, calendar, forms, etc.) to take the results of a form (set up as a way for instructors to enter their professional development for the semester), create a copy of a template, replace all information in <<>> with information from the form, move it into a shared folder (one shared with the teacher's supervisor), share the document with the teacher (view rights only), and email a link to the document to the teacher.
This was the first project we used to integrate the automation power of Google Scripts. We have since created an automated transportation request (auto-creates) an event on the bus/van/etc. calendar. We have also moved to a Google Sheets gradebook (from an Excel template), with automated progress reports.
But it takes so long!
Like every other kind of technology I have ever used in the classroom, yes, it takes a lot of time. However, all of the time you invest on the front side (development) you will get back probably two-fold on the backside. Time spent doing paperwork is reduced to nearly nothing. I remember the first school I worked at had a person who taught part time and the other part of her job was tracking professional development. This first script would have eliminated that entire part of her job. Not that I am in favor of people losing their jobs, but maybe that person could focus more on instruction? Or remediation?
If you would like to connect more about this topic, I'm happy to do so. You can connect through about.me/jbowie. If I can help you with anything, please let me know!
Post a Comment