Professional Documents
Culture Documents
XML2004 v0
XML2004 v0
XML2004 v0
v
for a Campus Calendar Network
Allison Bloodworth
Project Manager
e-Berkeley Program Office
University of California, Berkeley
abloodworth@berkeley.edu
Standards Investigated
iCalendar (RFC 2445)
Source of our repetition rules
SKICal
Influenced our Admission Info section
DE- Document Analysis (con’t)
Calendar types selected for evaluation
Academic Departments
Academic Colleges/Schools
Research Centers
Libraries
Museums
Athletics
Personal Calendaring Systems
Administrative Departments
Student Groups
Analyzed 23 calendars in all
A representative sample of the domain
Kept analyzing new calendars until “law of
diminishing returns” told us when to stop
Used 80-20 rule to focus efforts
DE - Component Analysis
Creation of a “Consolidated Table of
Content Components”
DE - Component Analysis
(con’t)
Harvesting & Consolidating Components
Need metadata to capture the meaning &
business rules of each component because the
name is not “self-describing”
Calendar
Name of data element in calendar
Our semantically unambiguous name (glossary)
Composite Name (groups of related elements, e.g.
DateTime)
Description
Data Type
Possible Value
Default Value
Etc.
Harvesting took on average 2 hours per calendar
DE - Component Analysis
(con’t)
Glossary
Our simplified version of a controlled vocabulary
Ensure that every component is semantically distinct
by weeding out homonyms & synonyms
Ensure that we break elements down to an
appropriate level of granularity for our context
of use
Paper Prototype
UCD – Iterative Design Process
Interactive Prototype
UCD – Iterative Design Process
Findings from Usability Testing
Application Layout
Paper prototype
Latest Design
Terminology
Post vs. Publish
Event Contact
Features
Export
Calendar Transforms
Event Instance
Institute of East Asian Studies calendar
Original (http://ieas.berkeley.edu/events/)
Our transformation
Letters & Science calendar
Original (http://ls.berkeley.edu/events/)
Our transformation