ctc091906

h3. *College Technology Committee*

*Tuesday, September 19, 2006 2:30 P.M.*
*HTC1-124 - Teleconference Room*

h3. *Meeting Agenda*

I. Welcome & Introductions

II. Announcements & Reports 

III. Current Topics
* Technology Assessment Taskforce
* GCC Website
* Flowchart of Technology Departments
* Smartboards
* Hybrid-Online Courses
* Wiki Student Accounts
* Process for Software requesting, approving and implementing

IV. New Issues

h3. *Minutes*

I. Everyone introduced themselves and James welcomed the group.

II. The following reports were given:

_Marla Desoto:_ is increasing bandwith expensive? maybe we cough up some of our own cash? - even though we dont have a budget line dedicated for it?;

_Scott Kozak:_ what will it take to accomodate an increasing demand? to stay on the "cutting edge" we need to develop a strategy and a plan that doesn't limit students; like the DPUP (Data Projector Upgrade Plan) was collaboratively developed to stay ahead of the curve and allocate resources effectively to answer all the needs;

_KC:_ we have a full pocket of money to fund the DPUP because of the bond; however, in the case of operational dollars and the bandwith discussion, funding is expected to go down and this will be a factor to consider;

_James Abraham:_ we will schedule a meeting in two weeks (an all call CTC meeting) to explore the options.

KC continued with his report saying that Rich Lang would be going back to District in the next few days. He stated that Rich has done a fabulous job here and is going to be missed. Other topics included the newly revised [GCC Help|http://help.gc.maricopa.edu/] page that includes a view of open workorders. Everyone was encouraged to use the page to check on the status of workorders they have called into the Helpdesks. KC referred to a printed handout of recent open eGCC workorders. Also distributed were handouts on budget figures from the [Network Redesign Project|http://wiki.gc.maricopa.edu/display/docs/Home#Home-ProjectDefinition] and the initial [GCIS Executive Summary|http://gcis.gc.maricopa.edu/] acknowledging the TAT Report findings and recommendations.

*Innovation Center - Jim Daugherty* updated everyone about the shortage of staff in the dept due to maternity/paternity leaves, and ongoing network projects. He asked everyone to please be patient when calling to the Innovation Center for assistance.

III. The following topics were discussed:

*TAT Update* \- it was noted that since their report had been published, the TAT committee was no longer actively meeting. It was noted that no formal recommendations were mentioned in the report re: the approximate $200,000 set aside (at the request of VP Sherman; see dl-gc memo titled Penultimate CRC recommendation from CRC Chair Gary Calderone dated November 2, 2005). The question was raised as to whether a recommendation would come from Administration; it was noted that CRC had also committed to reconvening to evaluate any recommendations re: spending as a result of the TAT findings. Please see the [CRC Recommendation 2006-2007|http://ns.gc.maricopa.edu/crc/CRC0607.htm] document.

*GCC Website* \- James asked about the progress of the Website Advisory Committee (assembled during the Spring semester at the direction of then Interim President Jean Abel to focus page layout/content on recruitment/retention of more students). It was noted that there is a group from A&R and Marketing working on the main page and student portion of the site, and their work will be made available for review soon; however, that hasn't happened yet, so for now we are continuing with what already exists. It was noted that the comitttee seemed to have changed focus and stopped meeting; a recommendation was relayed that the committee should get together to come to a consensus to move forward; by December 31, 2006 we need to have a new site ready to go.

_Other comments and recommendations made:_
_Marla:_ recommends revisiting the layout design that Bobby Sample presented to the CTC in April '06 since it was well received. She suggested Bobby's work be considered when determining a course of action.

It was noted that Marketing has created microsites for its own purposes of recruitment - maricopachoices.com - and all ten colleges have supported that.

_KC:_ stated that the college's main web server needed to be restructured as part of the network redesign project. He mentioned that there should be an agreement from the college on how things are organized - he cited 350 individual directories with no one pruning or maintaining continuity, and as a result, it has overgrown over the past 15 years. He indicated that the new web directory structure should keep in line with what is being done with the shared course folders. He stated that GCIS would like to come forward with a directory structure recommendation to whatever group will be reviewing this topic.

_Marla:_ recommended a new websteering subcommittee of the CTC be formed. Marie Villarba, Marla Desoto, Jim Daugherty, Jeremy Bessee and BJ Jacobs volunteered as the initial members. They will involve the existing campus web groups and committees as well as department webmasters. It was noted that department webmasters are supposed to be representatives to the CTC, but there hasn't been substantial support/participation in this. A suggestion was noted that maybe webmaster responsibilites should be passed on to another department employee willing to attend and become involved in CTC if current webmasters indicated that they did not have time/desire to do so.

*Flowchart of Technology Departments* \- the question was raised about how to route problems/issues through the Technology departments (GCIS). KC stated that the Helpdesks are the primay point of contact. All calls are logged as workorders and routed (and/or escalated) to the appropriate technical area for resolution. It was noted that routing information through the Helpdesks is a strategic intake process that is vital to the resolution of error reports, and the follow-through of GCIS customer service. Also, the [GCC Help page|http://help.gc.maricop.edu] provides a way to view up-to-the-minute progress on workorder requests. A comment in response to KC's remarks was noted: "there is no accountability that way".

*Smartboards* \- Jim D. stated that demos are available in the Faculty Connection Center (FCC) and the Innovation Center; the small one is checked out at the moement, but the big one is in HT2-149. If you would like one for your department, remember to include it in the budget request for this year. They are not terribly expensive - about $1,000. Just a reminder that department budget requests are due by Friday, September 29.

*Hybrid/Online Courses* \- Jim D. says they are in the process of finding a person to provide leadership, planning and continuity, and are getting ready to fill a position titled Hybrid/Online Coordinator. For details about the position, please contact Jim. It was noted that Mike Aragon's online student start page is being updated; faculty will need to make sure their content is current by contributing to the page. For assistance with updating information, please contact Mike.

*Wiki Student Accounts* \- John Kakritz responded to questions about the status of wiki server development by saying that he was not sure of the order of the college's priorities and deferred to those still directly involved in the network redesign project. KC stated it has been troublesome to integrate the Confluence software that runs the wiki with Active Directory; however, he expected to have it done before the end of the semester. Part of the issue is the need to reinstall the software from scratch. Toni [McClory] stated that she needed to be able to plan on this resource for next semester - will it be available? Roger Siggs responded that, to date, the wiki has been a pilot project, and expectations have not been cleary set - nor a strategic plan set in place. Marla and Toni reiterated that they just needed to know when...

*Software Process* \- it was noted that a process does exist to request, approve, and distribute/install software; however, the mechanisms across support areas seems disconnected. Part of the problem remains that there are extremely limited resources to implement a seamless solution at this time. A draft of the internal workflow to process software does exist on the wiki: [SoftwareProcessing].

*REMINDERS*

*The Next Regular CTC Meeting* is scheduled for Tuesday, October 16th at 2:30pm in the HT1-Teleconference Room.

*Be on the look out* for the next special CTC meeting to discuss bandwidth, and updates from the CRC about TAT recommendations.