Getting a Handle on District Technology Assets
By Miguel Guhlin
"If we don't change direction soon," wrote Professor Irwin Corey, "we'll end up where we're going." Which makes one wonder: in bringing technology into schools, do we ask where we are going to end up with all this?
I had the occasion to reflect on the constant pace of change a few months ago. But, before I share with you that story — which is the beginning of this tale — I'm going to go straight to the end. You need to know about it if you're a technologist in public schools and lack lots of money. It's appropriate that we begin with the end in mind.
The End of the Story
In early September, several of us — directors and an associate superintendent — were planning our annual campus asset tracking (CAT) survey, a.k.a. Campus Access Survey (since we did not want to offend Fixed Assets, we changed the name). We faced several key challenges, including:
  1. The District needed to have more data about equipment, software, and its use than Fixed Assets Department was collecting. Existing fixed asset systems were too limited and there was no centralized processing of equipment that comes into the District. Let me say that differently. New equipment coming into the District goes straight to the campus — bypassing the District — and is then tagged at that location by a secretary assigned the duty. This system made it possible for the campuses to buy equipment with no oversight from the District.
  2. Computer assets were moved from room to room and there was no uniform room numbering scheme. As such, the most we could know was that equipment was at the campus but not where it was. The campus staff knew what the room number was, but not the District. In other words, the room numbering scheme made sense only to campus level staff, yet they had no way to see what they had in one place.
  3. How could we move our Campus Enhancement Program — all about matching campus purchases of equipment with an equal amount from the state technology allotment (the only game in town now that TIF/TIE funding is gone) — to a Web-based process?
  4. Establishing a dialogue in the form of information exchanges was important. As assets moved, were added to or removed because of obsolescence, campuses needed a way to keep the District in the loop for long-term technology planning.
  5. Collected data was stored in separate locations, unrelated to each other. In other words, what impact did the number of assets have on the LOTI level? How could anyone know if no one knew what they had?
  6. Superintendents, principals were asking, "How many computers do we actually have? How does that number match up to the number of teachers in the District?
So, you can see, this last question is what really started the ball rolling on this massive data collection effort. As Curriculum & Instruction, the Instructional Technology Office brought more Web-centric (e.g. Web-based gradebook, digital video and more) and handheld assessment applications into the District, it became necessary to know exactly who had a computer and who did not. This became fundamental need in preparing reports for the superintendent. After all, how could we justify the statement, "Our teachers lack the equipment necessary to achieve LOTI Level 1 or 2, much less the target technology level of the STaR Chart and LOTI — level 4."


external image ctr.jpg
**Click on picture to enlarge**
The end of the story is really the beginning. In our effort to collect massive amounts of campus asset tracking data, campus contact information for our campus technology representatives and moving administrative staff, campus technology enhancement program, and digital video distribution system passwords as well as bring together STaR Chart data and LOTI data, we ended up with what is now called the Campus Technology Representatives (CTR) Data Center.
CTRs are volunteers from each campus that shuttle messages back and forth from monthly meetings. The District lacks the funds to pay for full-time Campus Instructional Technologists (CIT). Utilizing free database tools (e.g. PHP/MySQL) and Macromedia Dreamweaver, I built the CTR Data Center to centralize a wide variety of data. Relating all this data was actually easier with PHP/MySQL than it was with Filemaker Pro, the tool we had been using. And remember, I do not know how to program or code HTML. Relating various data to a campus was important and the key to success.
The Middle: It's All About Relationships
I arrived in my district in 2002 to discover the first campus asset tracking (CAT) survey, created using Filemaker Pro. We had to have the data because the only other option was to send people to campuses to physically count the technology, and these were people whose time was better spent working on the instructional applications of technology.
Although Filemaker Pro was fantastic, it wasn't long before we had almost 40 separate databases, accessible via the Web. We were working with data in what my supervisor called "silos." What he meant was that Human Resources had one set of data, DataWarehouse had another, and Finance still another. The problem with this approach is obvious now — we end up with separate sets of data that do not relate to each other and grow inaccurate with time.
I had databases to collect CAT Survey data, the Campus STaR Chart data (which at the time did not allow districts to see what had been submitted unless they knew the campus password), frequently asked questions, and much more. Many other functions were still done with paper, and again, when asked about our teacher to computer ratio, the best we could offer was a guesstimate. Yet, Filemaker Pro was the only program I knew that could be used as easily.
As you may know, Filemaker Pro is a powerful database program, much easier and more forgiving than MS Access. One of the key features that endured through versions 4-6 was its ability to share data through custom Web pages one could design using CDML, a special language. This was a key feature because it meant that I as well as many of the folks I taught how to do this at TCEA State Conferencesdid not have to learn how to program PERL, PHP, or whatever other arcane language interacts with Web databases.
When version 7 of Filemaker Pro came out, this feature was no longer available. I would have to learn XML, and this was too much like programming. Then, someone suggested, perhaps MySQL would work? As I pondered this monumental shift (has your cheese been moved lately? Then you'll know how I felt) in early September, my supervisor asked, "So, what's our computer to teacher ratio?" Worse, with so many new technologies in the District, the Filemaker-based version of the Campus Asset Tracking survey was inadequate. It failed to capture the data needed. I had every incentive to start over using a new tool.
With the help of some of my team — notably, Greg Rodriguez and Jim Baldoni — I learned the basics of using Dreamweaver's PHP connections to MySQL databases to create Web-enabled databases without programming. The process was not unlike that of Web-enabling MS Access databases. The Campus Asset Tracking Survey is six sections long; campuses can complete and save one section at a time. While this is standard for the Web these days, remember, Instructional Technology is not about programming and does not have $80K programmers on staff. And, if we did, they probably would not be used to collect asset tracking data needed for instructional decisions, STaR Chart, LOTI, Campus Enhancement Program, etc. What also made this successful is that our District Initiatives and Special Projects Director and staff were also able to query data using SQLYog (read sidebar), export the data, and build elaborate reports in MS Excel, their tool of choice.
The Beginning: Not Giving Up
What a powerful experience this has been. It only took me two or three days, finding or being shown the right resources like the ones in the sidebar, to get everything going...but it also helped me to appreciate starting over. I resisted the desire to quit and not learn. I resisted the desire to tell myself, "Miguel, you're getting too old to start over." And, I'm better for the experience.
So, even though I didn't like the fact that Filemaker stopped working the way it once did, I'm grateful for the fact that it did. Otherwise, I would have kept going the way I was going...and maybe that would have landed me somewhere I didn't want to be — one of those old fuddy-duddies who can't do anything, waiting to retire because they don't think they can, or want to, start over, even if that is what retirement means — starting over.
Email: Miguel Guhlin

Getting Started with PHP/MySQL
Tutorials:
Windows Software:
  1. WAMP Server: Easy setup of Apache server, PHP and MySQL on Windows.
    Cost: Free
  2. SQLYOG : Allows you to interact with the database using Structured Query Language (SQL), as well as make backups of your SQL tables.
    Cost: Free
  3. Macromedia Dreamweaver MX: Allows you to build web forms that interact with your MySQL databases and tables. The 2004 version of Macromedia Dreamweaver features better PHP interface.
    Cost: approximately $150
Macintosh Software:
  1. MAMP Server: Easy setup of Apache server, PHP and MySQL on on Macintosh OS X
  2. CocoaMySQL: Allows you to interact with the database using Structured Query Language (SQL) statements.
    Cost: Free
  3. Macromedia Dreamweaver MX: Allows you to build web forms that interact with your MySQL databases and tables.
    Cost: approximately $150
MySQL Tools Available for Both Windows and Macintosh:
Books:
While you can never have enough books, I recommend having these especially. Think of them as a $60 tranquilizer when you're ready to pull your hair out (a normal feeling when Web-enabling databases, no matter which database you use).
||
Title
||
Author
||
Cost
||
ISBN#
||
||
SQL Pocket Guide
||
Gennick, Jonathan
||
$10
||
0-596-00512-1
||
||
SQL Queries for Mere Mortals
||
Hernandez, Michael J. & Viescas, John L.
||
$50
||
9 780201 433364
||