|
|
|
|
|
"It is more important to know what sort of
patient has a disease that what sort of disease a patient has." Sir William Osler |
|
|
|
|
|
PETTT seeks to enhance the effectiveness of the
University of Washington's faculty and thus of the institution itself, by
creating a campus framework to promote the thoughtful
exploration, development, assessment, and dissemination of
next-generation technologies and strategies for
teaching and learning. |
|
|
|
|
|
Source: http://depts.washington.edu/pettt |
|
|
|
|
Respond to learner expectations and information
needs |
|
Technology in the service of good teaching |
|
Instructional goals and needs should drive
applications of technology |
|
Development should be part of the workflow, not
extra-ordinary |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Site Value |
|
Analysis |
|
Survey |
|
Feedback Email |
|
QuickPoll |
|
|
|
|
Conducting logfile analysis |
|
Conducting online survey |
|
Conducting interview with |
|
developer |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Good data design from the ground up |
|
|
|
|
|
Article Title |
|
Description |
|
Pages |
|
Subheadings -> Page titles |
|
Topic sentences -> Description |
|
Body text -> Keywords, search terms |
|
|
|
|
Consistency |
|
Ease of use |
|
Accessibility |
|
Visibility to search engines |
|
|
|
|
20-50-300: Text formatting guidelines |
|
XML: Extensible data format |
|
Zope: Content Management System |
|
4XSLT: Centralized stylesheet processing |
|
|
|
|
|
20-50-300 |
|
Each article has multiple pages |
|
For each page: |
|
≤20 word topic sentence |
|
≤50 character title |
|
≤300 words in body text |
|
Note: These limits were targeted for Inktomi |
|
|
|
|
|
Set limits based on search engine “robot”
preferences |
|
Too many/few words = Spam |
|
More pages = More relevance |
|
Improves: |
|
Ease of reading & searching |
|
Modularity |
|
As search engine ranking improves, hits will
increase |
|
|
|
|
|
|
|
|
|
|
|
XML allows usage of 20-50-300 |
|
Allows descriptive coding of data |
|
<article type=“disease” title=“Rheumatoid
Arthritis”> |
|
<description> … </description> |
|
<page type=“symptoms” title=“Symptoms of
Rheumatoid Arthritis”> |
|
<keywords> … </keywords> |
|
<description> … </description> |
|
<paragraph> … </paragraph> |
|
… |
|
</page> |
|
<page> |
|
… |
|
</page> |
|
</article> |
|
|
|
|
|
Modular |
|
Separates data from formatting |
|
Standards-compliant (W3C) |
|
Inherently Meta-data friendly |
|
Extensible, customizable |
|
|
|
|
Reduces complexity |
|
Increases consistency |
|
Allows implementation of standards |
|
Permits management by multiple content providers |
|
|
|
|
|
Open source |
|
Constant improvement |
|
Online community support, free |
|
Modular and Expandable |
|
Powerful scripting and external methods using
Python |
|
XSLT parsing with 4XSLT |
|
Web interface |
|
|
|
|
|
|
XML to HTML Conversion using: |
|
XML stylesheet templates (XSLT) |
|
XSLT Parser (4XSLT, Xalan, etc.) |
|
May also serve other protocols (WAP) |
|
Python-based |
|
Easily incorporated into Zope through external
methods |
|
|
|
|
|
|
Convey a relative advantage over existing ways
of doing things |
|
Are compatible with expectations, experience and
needs of faculty |
|
Reduce complexity associated with new
technologies |
|
Are triable in that they can be experimented
with on a limited basis |
|
Are widely observable to the campus community |
|
|
|