Wednesday, November 01, 2006

New Source Posted

The bug fixes and changes noted in the messages below have been uploaded with the new source package. You can find the whole thing at Check out the readme and the posts below for changes.


I'm working on a link to generate a report for each unit. Ideally, a single link to the president (or root) unit would link to the whole set of reports of units, goals, and objectives, all with the proper style sheet applied. This way you could release the reports without giving access to IGOR. Like for example to an accreditor.

Customizing the Look of the GUI

The institutional effectiveness graphical user interface (GUI) doesn't have to look like the out-of-the-box IGOR setup. You can change the background color, font, and font color. The /cgi-bin/config/ file now includes lines like these:

# Set Background Color
# use C-type hex notation, like 0xFF0000 for red (0 = zero)
$IEbgcolor = '0xECE9D8';
# set font = Times New Roman, Arial, Courier
$IEfont = "Arial";
# set color of text
$IEtextcolor = '0x666666';

You can try other fonts than the ones listed, but results may vary according to what is loaded on the client machines.

Working with the Org Tree

If you have used the Create Organizational Tree to set up a year's organization and later find that you need to modify it, here's how to do it.

Adding a new unit If you want to add a new unit node onto the tree, then first create the group from the IGOR administrative screen. Add members to the group. Then go into the GUI, click on the unit that the new one will be subordinate to. Use the Add Subordinate Unit to select the group you created. Click 'Accept' to add it.

Moving a unit If the org chart gets rearranged or you want to move an objective from one goal to another, you need to use an auxillary function accessible only to a system administrator. Telnet to the server, cd to the /cgi-bin/igor directory and run perl It will prompt you to enter node numbers. These can be found in angle-brackets in the top left of the GUI window. For example <510>. Unit numbers always end in zero, goals in 1, objectives in 2. You can use this utility to move more than one node at a time. Note that you can easily create illogical arragements, with a unit subordinate to an objective, for example. This isn't recommended.

Copying a node You may want to create a template for an academic unit, consisting of set goals and objectives that are required. Once this is created, you don't want to have to repeat that process for each unit. You can use /cgi-bin/ instead. The script will prompt for node numbers. A very powerful way to use this is to copy the prior year's goals and objectives (without results) to the new year.

Example To set up a new year that looks like the old one, except for the results and actions part of the objectives (the only part that definitely won't roll over from year to year), do this:
  1. Make sure the years table contains the new year--you'll need to access the table directly in SQL do add it if not. Check out MySQL administrator for a free tool to do this.
  2. Use the Create Organizational Tree to stub a tree for the new year. To do this, delete everything except the root node (normally the President's unit). Be SURE you're on the new year so you don't delete anything important, and create it.
  3. Now have the system administrator copy (using everything under the root node for the expiring year into the new year. The prompts you'll see when you run IE_cp will take care of the details. All you need is the node number of the old root node and the same for the new one. These are easily obtained from the GUI. Click on the unit and look at the number in angle brackets, top left in the report window on the right side.

Bug Fix for Permits

Problem: The group administrators couldn't edit the mission for the group.

Solution: Added the capability. Group administrators will still not be able to DELETE the whole group, thus nullifying their own existance.

Files: The only file affected was /html/IGOR/ie.swf.

SQL Change

The most recent fixes (see last post) included the ability to lock years. In order to do this I added a column called 'Locked' to the Years table. Here's the code:

That's a zero, not an oh above. The locked value is 1 for any year that you no longer wish to have IE data entered for on the GUI. It won't affect the file repository--you'll still be able to archive files for prior years (it's always a possibility that someone will finally dig those minutes out and send them up to IGOR).