% messaging dashboard
% Jonas Smedegaard
% Denmark, December 2012
Overview
- Background - Open standards tools
- Dashboard
- Data
- Enhancing data
- Feeding Dashboards
- Personalizing your dashboard
- Challenges
Background - Custom tools or open standards tools
Background - Custom tools
- Owners can innovate
- Others run behind, maybe innovate bits but on owners' mercy
- Innovation not really needed: incentive is weak
- Leads to stagnating innovation: mono culture
Background - Open standard tools
- Anyone can innovate
- Those innovating lead
- Innovation is power: incentive is high
- Leads to lively innovation
Dashboard
- shows personal "tip of the iceberg"
- needs data already organized (not a magic bullet!)
- proposes sensible grouping of organized data
Data - Types of material
- Articles (blogs, reports, news columns, ...)
- Activities (tweets, presence hints, ...)
- Media (audio/vide recordings, slide compositions, sketches, ...)
- Agents (persons, organisations, ..., robots, crowds?)
Data - Sources
-
Open public (and private?) hubs (blog aggregations, ...)
-
Closed data silos (Facebook, Google, ...)
-
Organizational resources (filesystems, mails, relations, ...)
-
Select personal resources (presence, relations, bookmarks, ...)
-
! Understand and embrace the power of copyleft
Data - Interesting stuff
Reasons why something should appear at "top of the iceberg".
- New
- Popular
- Due
- Inspiring
- ...
Data - streams (not pieces)
- Not just the movie web page
- Not just the event behind the movie
- Not just the broker of the movie
- Not just the discussion around the movie
- The channels of web pages, events, brokers, discussions, etc.
Enhancing data
- Semantics often missing, esp. for most local data
- Must be dead convenient
- Be loose - tags not folders, share generously
Enhancing data - tagging
- Pick a tag, and apply to many resources
- Get a batch of suggestions, and approve/reject
- Work fast and sloppy - verify later and collaboratively
Enhancing data - channeling
Feeding Dashboards
Personalizing your dashboard
Challenges - technical
- Channel into closed data silos (not just get data out!)
- Channel into local data (without loosing privacy!)
- Require least possible tagging (harvest enough automated)
- Reason clever enough on harvested semantics (avoid silly suggestions!)
- Build robust code (not fall into the LAMP or mockup traps)
Challenges - perception
- Closed tools "feel" better (why switch?)
- Closed data silos "feel" supportive (why avoid them?)
- Dashboard "feels" boring (populism is a powerful drug!)
- I "feel" innovative on my own (why share excessively?)
The End - Use the source, Luke
|
