Developing a script Taxonomy

edWilsonPic_HeadAndShoulders_2_InchAs we have been busy at the TechNet Script Center with our migration to a blog, and bringing the TechNet Script Center Gallery on line, I have been giving a lot of thought to organizing the keywords / tags that are used to provide quick links to groups of topics. The problem is the world of scripting is huge. Forget for a minute the dozens of scripting languages, but consider the sheer number of things that can be “scripted.”

For those of you who might not know, a script is computer code that is not compiled. This means that it can be easily written in something as simple as Notepad—it is a plain text file with a special file extension. Most people never see file extensions because they are hidden by default in Windows Explorer. But a VBScript has a vbs file extension that causes Windows to execute the code in the file instead of displaying it in Notepad. A Word document has a doc (or docx) file extension that tells Windows to open the file with Word.

Anyway, many things on a computer can be scripted. For example, I can write a script that will create a Word document. This in itself might not seem too exciting, unless you think about running a script to find information such as the name of the computer, the programs that are installed on the computer, the amount of free disk space on a computer, the amount of memory installed in the computer, and the speed of the Central Processing Unit (CPU) for the computer. If you would like to write that information in a Word document it will save you a little bit of time. Suppose that you need that information from each of the 50,000 computers on your network because you are planning to upgrade to Windows 7 … now you can see that it would take a considerable amount to do all of this stuff manually.

Here is the problem … how do I file the above script that gathers the computer inventory information and writes it to a Word document? I can file it under WMI (which will be the technology used to gather the information from the computer) I can file it under Word because I write to a Word document, I can file it under Word document, because it creates a Word document, I can file it under Word.Application, Word.Document, Word.Range … and other such obscure things because those are the Objects I will need to create in my script to make the “magic” happen.

I recently read a book with the name of “Glut: Mastering Information through the Ages” by Alex Wright in this book, Mr.  Wright talks about how different societies wrestled what is sometimes referred to as information overload, or the information glut. How do you develop a taxonomy to organize, to categorize, or to systematize information retrieval?

At the TechNet Script Center what I have been doing is creating a Script Center Taxonomy (SCT) or perhaps Script Center Advanced Taxonomy (SCAT) that applies to the Hey Scripting Guy! blog, and the TechNet Script Center Gallery, this organization pattern is replacing five different methods of organizing the same information. It is a bigger project than I originally thought, and I have to take into account the legacy systems that were set in place nearly a decade ago. But it is also fun work. Oh, by the way, the information gathering script I talked about that writes upgrade information to a Word Document, I would probably file it under Desktop Management / Basic Computer Information.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s