Interesting thread in response to the Michagan news:
Poor Management, Not Poor Portal [Was: U. Mich Portal Project Closes]
http://list.unm.edu/cgi-bin/wa?A1=ind0204&L=jasig-portal#14
I quote in full the concluding item from Tim Aucremann:
> The campus portal is 'The Great Aggregator'. Imo, there's gotta be someone
> holding the center - someone who is there 24/7 keeping the ducks aligned
> and the vision warm. And this goes beyond making sure the cables are
> plugged in and the packets are humming. Who's the mayor of portalville?
>
> The UMich portal closing points up the importance for *a* campus IT body
> to act in an IT coordinative way across all the varied elements needed for
> portal success - especially when it's a portal trying to get off the
> ground. Without knowing UMich details, moving faculty support and
> administrative computing outside of the core IT organization may have been
> part of its undoing.
>
> Resources from across all IT are needed to make a portal happen. One
> conjectures this is more difficult the more these resources are
> distributed or without a central organizing group. I agree, Zed, project
> management issues definitely come into play - starting at the macro level.
>
> Since many of us are eating, sleeping and breathing our way to
> portalocity, it would be interesting (to me anyway) for JA-SIG discussion
> to expand into the project management, policy, and collaboration issues.
> Are there organizational or team structures that don't lend themselves to
> portaling? And yep - the standards discussion comes to play here too.
> From a kritical angle - are there conditions necessary for portal success?
Paul
--
The Library, Tyndall Avenue, Univ. of Bristol, Bristol, BS8 1TJ, UK
E-mail: [log in to unmask] URL: http://www.bris.ac.uk/
|