MetaNav: Managing Audiencebased Navigation for Plone

1
MetaNavManaging Audience-based Navigation for
Plone

• Cris Ewing
• Radiology Web Services
• Department of Radiology
• University of Washington
• Seattle, Washington, USA

2
The Problem
3
Unique Challenges
4
Complex Hierarchies
5

• 14 Academic Sections
• 12 Research Units
• 5 Clinical Sites
• Byzantine Administrative Structure

6
Wide Variety of Constituents
7

• Patients
• Students/Residents/Fellows
• Prospective Students
• Job Seekers
• Referring Physicians
• Staff
• Faculty
• Researchers

8
Decentralized Control
9
Complex Websites
10
(No Transcript)
11
Whats a Webmaster to do?
12
we separate contentfrom presentation
13
why not separate contentfrom navigation?
14
flexible manageable
15
provide logicalnavigation structures
16
preserve illogical (but politically
entrenched)hierarchical structures
17
(apologies to scott adams)
18
many possible strategies
19
Audience-Based Navigation
20
identify constituencies
21
individualized navigation
22
identify tasks
23
Patients
24

• Make an appointment
• Change an appointment
• Prepare for a procedure
• See the results of a procedure
• Talk to a radiologist
• Get directions to a clinic
• Get information about a bill

25
Faculty
26

• Find my call schedule
• Find the Resident/Fellow call schedule
• Work on the PACS system
• Author or Edit a teaching file
• Check HR Policies and Procedures
• View Protocols

27
6-10 tasks per constituency
28
links to actual content
29

• Patients
• Make an appointment
• Harborview Clinic Scheduling Nurse
• Roosevelt Clinic Scheduling Nurse
• UWMC Scheduling Nurse
• SCCA Scheduling Nurse
• VA Scheduling Nurse

30
But isnt that cumbersome?
31
MetaNav
32
simple
33
plonish
34
(No Transcript)
35
folder-based hierarchy
36

• Navigation Root (folder)
• Constituency Button (folder)
• Task Category (folder)
• Content Link (item)
• Task Link (item)

37
content creatorsknow their audience
38
let them build the system
39
Global Navigation tab
40
(No Transcript)
41
(No Transcript)
42
(No Transcript)
43
(No Transcript)
44
But how do I maintain control?
45
navigation manager role
46
(No Transcript)
47
Three workflow states
48
Pending
49
Published
50
Pending Removal
51
Links removed are still there
52
can be re-activated
53
or deleted entirely
54
But its so ugly!
55
Easily Skinnable
56
(No Transcript)
57
two categories(top and side)
58
multiple navigation schemes
59
Audience-BasedandTopical
60
Information For . . .andInformation About . . .
61
How do we know its working?
62
analytics-ready
63
google analytics
onclickjavascripturchinTracker(metanav/button/
topic/link)
64
MetaNav builds the path for you!
65
easily integrated into TAL
66
evaluate click paths
67
tune your system
68
actual usage patterns
69
(apologies to scott adams)
70
MetaNav is available now
71
http//plone.org/products/metanav
72
Credits
73
Conceived and Commissioned byUW Radiology Web
Services
74
Created byWebCollective, Seattle WA
an employee-owned cooperative that builds
websites with a purpose Content management,
Values-based Design, Open Source, Systems for
Collaboration, SEO, Social Networking.
75
questions? comments? ideas?
76
UW Radiology Web Services http//www.rad.wash
ington.edu (live in January) Cris Ewing
(cewing_at_u.washington.edu)
WebCollective http//webcollective.coop
Brian Gershon (briang_at_webcollective.coop)
Bryan Wilson (bryanw_at_webcollective.coop)