Thinking toward an inventory of instructional technology equipment

8 Feb 2001
I talked with Carole Bailey about existing data and procedures and learned some vital facts:

What we have here is a classic case of need for a collaboration to build the tool --a relational database-- that will connect up the known bits, incorporate new bits when they are added, remove deleted bits when they are retired, and enable us to ask and answer questions about what's where, when and by whom it was purchased, who is responsible for support, repair records, maybe even usage statistics, etc. Such a database is a practical necessity to manage what we have and to make informed decisions about what will be purchased, and it should be built right. The collaborators will need to include at least the following: What's needed to accomplish this design of a knows-all tells-all database? Again, a classic collaboration problem: donated resources and time and energy can't do it. People need to be assigned to tasks as part of their jobs, and manpower has to be allocated to accomplish the data-gathering and -entry, the writing of the code to connect existing bits and pipe results to end users, and the testing and deployment of the completed project.  Much of it could be done during the summer with student labor (a talk with Tom Whaley would be the first step in mobilizing that).

9 Feb
Carole tells me that Tom Contos is willing to fund part of the process of amassing the necessary data (via student hours during the summer), since he's been charged with the task of evaluating space and therefore needs the same information we're after, including instructional technology. As Carole noted, there are actually more constituencies who need this information than we'd originally thought.