One of the products that I currently manage is the Utah Enterprise Employee Portal (EEP). EEP uses Novell's Portal Services product. There are two broad issues with this product that I wish to address in this entry.
First, EEP is an enterprise project by definition. With the recent announcement of the future CIO/DCIO/ACIO structure and the description of the procedure for enterprise projects, it is obvious that this product should be number 11 on the governor's list of 10 projects. As such, it needs to be presented during cabinet council, and I am working towards that end. I think that visibility will do the product some real good, and hopefully it gain the full support of the governor and the cabinet.
Second, an Enterprise Employee Portal should be the content aggregation point for all content useful to employees. Its purpose would be defeated if employees had to continue to go hither and yon to get information, or depend on email broadcasts for it. We have several really great sources of content that belong on the portal. Much effort is exerted by many different people in different agencies to gather information. That effort and the implied ownership of the content has, in the past, been a barrier to centralizing it all into one location. With the advent of RSS (some say that means "Really Simple Syndication" but it really means "Rich Site Summary") and the compatibility of the Novell Portal Services product with RSS, there really isn't anything stopping us from allowing content owners to continue creating and owning content and at the same time making it available for inculsion in the portal. Basically I agree with Windley's view in his document on this topic. I will be pushing in this direction.
2:08:19 PM 
|
