MMI Website 2.0 @
MMI Kickoff Meeting
Nan Galbraith, Katherine Joyce, Andy Maffei,
Al Plueddemann, Danielle Fino
Woods Hole Oceanographic Institution,
23/24-October-2006
My Goals for next 2 days
• Inform MMI team members of the approach we
are taking with website redesign
• Gain endorsement for the approach we have
chosen
• Identify a team of MMI participants to play an
advisory role for web redesign
• Get feedback on the work we have done so far
(mostly will be done during day 2)
Day 1 - Monday
(Strategy)
An Overview
Website Design Process
(how we’re gonna do it)
Define the Objectives:
MMI Mission
• To promote the exchange, integration and use of
marine data through enhanced data publishing,
discovery, documentation and accessibility.
• More on the proposed Mission, Goals and
Audience statements can be found at
http://marinemetadata.org/info/aboutmmi/plannin
g/website/techteam/webupdate/
• Please provide feedback
Define the Objectives:
MMI Goals
• Provide information and guidance on emerging
standards and tools in oceanographic metadata
• Provide value-added reviews and documentation of
tools, standards, and projects related to management
and use of marine science data and metadata.
• Build community among people interested in collection,
archiving and dissemination of marine science data and
metadata
• Provide access to tools to solve specific problems in
marine metadata interoperability
• Become the “go-to place” for marine metadata
information
Define the Objectives:
MMI Audiences
• Scientists - provide guidance for integrating metadata
into marine science datasets and ease the task of
publishing data
• Data managers and data processors – provide
guidance on tools, standards, best practices
• Technologists – provide tools, information on
standards, a venue to describe or test their projects, a
community, demonstration projects
• Agencies and managers - provide a view of trends,
ideas, and projects within the marine data community
• Students – provide information on best practices and
new trends in marine metadata
Current Site Analysis:
User Survey
Current Site Analysis:
User Survey
Current Site Analysis:
Statistics
Visits by Month
25000
20000
15000
Visits
10000
5000
0
• Highpoints
Aug-05 Sept Oct Nov Dec Jan Feb Mar April May June July Aug-06
– Visits are going up (total = 180,000)
– More visits during week than on weekends, more at day instead
of night [means folks coming from work -- not like myspace]
– Visit duration is short (80% stay for only 0-30s, this is unusually
high but this might be bots)
– Lots of page views per visit (7, also possibly bot-related)
– .edu visits seems low, something to track after redesign
– Top pages shows technical audience (other than “what is
ontology”
– Total MMI site members is increasing. This is important
Current Site Analysis:
Top Pages
• 1) Homepage - 15,762
• 2) What is an Ontology? – 9,241
• http://mmiproj.whoi.edu/awstats-
www.marinemetadata.org/2006/awstats.www.marinemetadata.org.urldetail.html
• 3) Login page – 8,324
• 4) Search – 8146
• 5) Cyndy Chandler’s “newly added item test” - 5408
• http://marinemetadata.org/Members/cchandler/Testing/addItem.050729/atct_topic_
view
• 6) topic.2004-12-07.455281303 (user = aisenor) – 4763
• 7) http://marinemetadata.org/2005/08/cf – 4271
• 8) http://marinemetadata.org /2005/08/gcmd-keyw – 4227
• 9) RSS feed for events – 3848
• 10) Guides – 3430
• 11) General Information – 3309
• 12) Manager Feedback Form, Plone plugin - 3008
• 13) Projects (http://marinemetadata.org/examples) – 2852
• 14) http://marinemetadata.org /2005/08/gcmd-inst – 2768
• 15) Events – 2691
Comparative Analysis
Comparative Analysis
Project Plan Milestones
• Preliminary (Optimistic) Project Milestones
– Project Start (7/1/2006)
– Maine MMI Kickoff Meeting (10/23/2006)
– Initial Wireframe (12/4/2006)
– User Interface Design Complete (1/16/2007)
– Plone Implementation Plan Complete
(1/22/2007)
– New Website Released (3/30/2007)
• These will all need to be updated, and
schedule baseline will be set after this
meeting
Project Plan Chart
Site Map
Building the new website
• Engage website partners
– Identify both funded and volunteer groups
– Work together for coherent progress
• Teams
– Need the expertise of both the Guides team and Tech team
• Site Dynamics
– Consider elements of an editorial process
– Plone workflow: when are items published?
– Information architecture: where to put things?
– What process guides decisions on content/organization?
• Plone product review
– Evaluation of new products
– What features and products are working well for us?
MMI Website Breakout
(Tuesday)
A Working Session
Website Development Process
Navigation, why is it important?
SurveyMonkey Questions
http://www.surveymonkey.com/s.asp?u=129832714313
• Discussion Notes:
Website Project Plan
• Discussion Notes:
Website Block Structure
• Discussion Notes:
Comparative Analysis
Comparitive Analysis
• Discussion Notes:
Current Site Analysis:
Statistics
Visits by Month
25000
20000
15000
Visits
10000
5000
• Highpoints 0
Aug-05 Sept Oct Nov Dec Jan Feb Mar April May June July Aug-06
– Visits are going up (total = 180,000)
– More visits during week than on weekends, more at day instead of night
[means folks coming from work -- not like myspace]
– Visit duration is short (80% stay for only 0-30s, this is unusually high but
this might be bots)
– Lots of page views per visit (7, also possibly bot-related)
– .edu visits seems low, something to track after redesign
– Top pages shows technical audience (other than “what is ontology”
– Total MMI site members is increasing. This is important
Current MMI Website Statistics
Current MMI Website Statistics
Current MMI Website Statistics
Current MMI Website Analysis
Statistics (August 05-06) Visits by Month
• Discussion Notes:
25000
20000
15000
Visits
10000
5000
0
Aug-05 Sept Oct Nov Dec Jan Feb Mar April May June July Aug-06
Content:
How do the guides best fit in?
• Discussion Notes:
Content:
Editorial Process
• Proper design will provide a clear location
for content to go
• Menus should remain consistent
• Need a process for reviewing new content
• Different authorities at different levels
Editorial Process
• Discussion Notes:
Roles of other project
participants in new webdesign?
Who? What?
Nan
Luis
Karen
Website Advisory Team
(one model)
• Team composition
– Use the current technical advisory team or create a new one(?)
– Add someone with experience in web design?
• Team work
– Work done by leader adding items to tech committee agenda
– Provide regular updates to tech comm on web redesign work
– Review decisions on web issues with broad impact
– Advise MMI executive team on website status and needs
• Team authority
– Team leader able to pull together necessary people to
accomplish sub-tasks and report back to tech team
Content Editorial Process
• Open Discussion
• Discussion Results:
– This will be an open discussion about editorial process
Plone Considerations
• Design work done independent of plone, but use names
in Plone stylesheets
• Port frontend to a Plone “product”
• Possible plone addins
– Help Center product might help with online guides. Has TOC,
etc.
– ATVocabulary plone product has OWL support, needs looking at
– Captcha provides additional security
– Webstats Manager provides better statistics