Web Advisory Group (WAG) Implementation Plan

ITC

10/19/04

Markus Stobbs

Background

• 2001 – WAG Strategic Plan approved by ITC• 2004 – Many strategic goals have been accomplished

• Centralized Web Hosting of over 40 d/p sites• Gatekeeper Authentication• UCAR Search Engine• People Search• Mailman Email Lists• This Week @ UCAR• F&A Web Applications

• We need an implementation plan going forward

Process

• Open monthly WAG meetings to brainstorm• WAG Implementation Plan Subgroup• WAG Survey of 80 division directors and developers• Series of WAG meetings to prioritize projects and

refine plan• Analyzed WAG network of relationships• For each project, created Description, Rationale,

Elements, Potential Solutions, Potential Implementers, Effort

• Further details will be fleshed out by each project plan

Relationships

ITC

WAG WEG

SCD

reports reports

advises implements

Other Implementers

Implementers

Implementer Focus Audiences served

WEG Science side apps, hosting All

F&A/IT Business side apps, hosting Employees

SCD/OIS SCD apps, hosting Employees, external users

UCAR Comm Content, editorial All

EO Content, instruction Ed, public

WORD Content, advisory All

Domain Experts

• COMET – instruction• DMWG – scientific data• DPC (DLESE) – metadata catalogs• GIS Initiative – GIS• Unidata – metadata catalogs• WORD – content

Top Priority Projects

• Test Environment• Search Engine Optimization• Next Generation Authentication

& Access Control• Metadata Directories & Catalogs• Collaborative Portals• Content Management System

Test Environment

• A test cluster will mimic the configuration of the WEG production cluster as closely as possible in order to provide a reliable environment for testing websites, web applications, and software upgrades before moving them onto the production cluster.

Search Engine Optimization

• Optimize Verity Ultraseek engine preferences • Publish best practices guidelines on optimizing

content for search engines and expiring outdated content

• Review and update host index list• Redesign search results interface for more

effective information display• Experiment with Google web service for indexing

our public pages

Next Generation Authentication

• Planning for a transition to a next generation authentication system such as Kerberos should include thorough research into web integration

• Web Requirements– single sign on– backward compatibility with existing Gatekeeper– integration of authentication services into websites & web apps

Access Control

• Granular access control would enable system administrators to set user and group access privileges for specific web content and services

• Would require a central directory of UCAR employees, members, and collaborators

• Needs to be integrated with Authentication solution• A user should be able to progressively refine their

identity and preferences, and have that feed all the UCAR websites they access

Metadata Directories/Catalogs

• Metadata directories have proven very useful for cataloging datasets and we recommend this approach be applied to other types of high value web resources such as:– ASR, scientist profiles, projects, posters,

instruments, applications

Collaborative Portals

• Using a portal framework, we would offer numerous web-based tools for project teams to collaborate and share project resources

• Tools would include:– document repository, project mgt, discussion

boards, collaborative documents

Content Management System

• Content repositories

• File transport

• Version control

• Edition management

• Web page creation and update via simple forms for non-developers

• Symptom - numerous “404 page not found” errors

See the Entire Plan

• www.ucar.edu/wag/imp

• Projects By Audience• Highlights

– Annual Scientific Report web application– Form-driven Scientist Home Pages– Support Center

Top Priority Projects

• Test Environment• Search Engine Optimization• Next Generation Authentication

& Access Control• Metadata Directories & Catalogs• Collaborative Portals• Content Management System