Target:

Current Status

Desktop Management

Current issues:

• Quotas for personal home directories
• Quotas for departmental shared space
• policy and procedures on quota increases
• account retention
• agreement on the managed desktop
• migration plan
• communications plan
• agreement on what to use as NetID

Question about amount of space and charges--yet to be determined by Steering Committee

Question about roaming--and use of client software - AFS requires a client

Further information is on the IT project website, whereupdates are posted.

3. Web Architecture Project
In the past year, this group explored functionality requirements and reviewed and rejected some off-the-shelf software which was too expensive and didn't meet our requirements. We also looked at a home-grown product from Duke and at SCT Documentem, Luminus.

Carrie Gillotte gave an update (PPT presentation) on where we are with respect to the project to date: First, we discarded the Duke model because the technology wasn't quality we need for an enterprise wise production system, and we would have needed to re-do the technology. They also backed away from wanting to work with another school and talked about charging us.

As the Banner project wound down, we began discussions with SCT about portal project, which led to discussion about Documentum, content management system. We learned that other Banner schools also working on introducing content management. One advantage to this system is its connection to Banner.

We have decided to go forward with a pilot project for content management involving course information. This would invovle having a single source of code, single source of data in a database we would design. This will be connected to a work flow for the course approval process which will be built on CAS current work on online course approval process.

This phase will involve three steps: IT side under Carrie will look at this to ensure it is scalable to an enterprise-wide system; we will gather more information about course approval process in other units to be sure it will work for them; we will work to see how this can feed into the Provost's Office processes for graduate course approval.

The second phase will be to use the SCT software to write content objects that use the course data to feed into various web sites--department, catalog, course sites, etc. This will require us to determine what kinds of information need to be available in the course information object. We willset up a steering committee to work this out. It will have representation from academic units, provost's office, university relations, electronic publications, some technical representation. We will also need to develop templates for various uses of the data.

This project would be the proof of concept which may possibly/hopefully lead to improvement of process. It will actually give us a chance to rethink the course approval process and how we say things and describe things.

Overseeing this project will be a steering committee which will work with the ITU.

On the technical side: Bob Nakles will be the project manager and Kirsten DeLashmutt, ITU Technical lead.

Next Steps:
Dee will find a chair for the Steering Committee for the Content Management project and arrange for an initial meeting of the committee. Carrie will look at the CAS workflow product to determine if it can be scaled or needs to be written in different code.

Attending:
Joy Hughes
Anne Agee
Dee Holisky
Carrie Gillotte
Wally Grotophorst
Creston Jamison
Bob Nakles
Walt Sevon
Jean-Pierre Auffret
Lara Bushallow
Kirsten DeLashmutt
Jim Finkelstein
Cathy Hubbs
Paras Kaul
Roy Rosenzweig
Stan Zoltek

Guest:
Karen Gardner

-top-