GeorgetownUNIVERSITY

Some directions in (web) content management

Piet Niederhausen

University Webmaster

Georgetown University

Departmental web CM

Institutional web CM

Syndication

Individual CM

Departmental web CM

» Reduce cost of publishing (training, support)

» Enforce consistency within each site» Enforce best practices (usability,

interoperability)» Store content in a more reusable form» Focus departments on content, not

technology

Departmental web CM Institutional web CM

» Consistently capture, manage, present, and archive key institutional content e.g., courses, faculty, news, events

» Add institutional metadata e.g., topics, affiliations, people

» Connect related information to make content “explorable”

» Make current, authoritative data available for syndication

» Strong relationship to core business processes» Some relationship to “digital library”

Persons Courses

Class schedules

Syllabi

Publications

Research projects

Documents

Campusmaps

Buildings

Offices

Universitystatus

Events

Affiliations

University news

Announce-ments

Blogs

Calendars

Faculty profiles

Student profiles

Universitypages

Topics

RSS feeds

Depart-ments

Student orgs

GeorgetownUNIVERSITY

Some of the potential contentsurrounding a faculty member

Researchprojects

Researchresources

Academicdisciplines

CV

Publica-tions

CoursesMediaprofile

Depart-ments

Centers

Facultymember

Syllabi

Coursesites

Teachingportfolio

In thenews

Departmental web CM Institutional web CM Syndication

» Reuse web content in multiple locations, formats

» Make web content available in other forms e.g., email, RSS, podcasts, SMS

» Make institutional content available to departments; allow departments to “own” their presentation of institutional content

» Create new topical (non-departmental) content gateways

www University web sites

Department and division web sites

Syndication layer

RSS

Email

SMS

Externalcontent

Departmental web CM Institutional web CM Individual CM Individual CM

» Tools used by individuals in their work and scholarship to … Manage and share files Create or consume course content (LMS) Build portfolios Access personalized announcements, news,

events (portal, feeds) Network with colleagues, friends (social

networking)

GeorgetownUNIVERSITY

Potential shared infrastructure

» Shared storage, backup» Access to common functionality

Authentication, authorization, groups Rights management Version control Conversion between formats

» Service oriented architecture» Common metadata, markup» Best practices

Physical storage- Storage- Backup- Disaster recovery

File/storagemanagement

Object management- Content modeling- Metadata- Versioning- Rights management- Format conversion- Search

Applications- Content creation- Content consumption- Business logic

Authentication andauthorization

Content management projects mapMay 12, 2005

NetID

KeySiteBlackboardSharestreamWeb based file system

Premium EFS

Custom

Local OS

Local storage

Networked storage

Enterprise backup

Blackboard

Local OSLocal OS

Local storage

Custom

Local OS

VMWare host

SQL Server

Explore

Xythos

Local OS

n/a

Various web apps*

Local OS

Custom

Shibboleth Grouper

*Various applications that reside on UIS web hosting VMs. These share storage on a VM host but otherwise have local functionality. Examples include Angelica, KeyTalk.

uis-ss1

Digital library (incl.

ETDs)

Chuckwalla, DSpace,

and custom

Local OS

Local storage