May 2008 Archives

Day Summit - Support 5/29/08

| 0 Comments | 0 TrackBacks
Bob Kelton, Executive Sponsor
Day Support


Support Tiers
1. basic issues - trained key users will provide support
2. disfficult issues - support team - daycare
3. product issues - R&D

Support Improvements
  • executive sponsor
  • improvement iniative for daycare

Eren Aydin
North American Support Lead
eren.aydin@day.com

dev.day.com/kb


  • tripled support agents
  • top quality resources
  • dedicated support lead

Day Summit - Social Networking 5/29/08

| 0 Comments | 0 TrackBacks
Lars Treiloff

Social Networking Features
activity feed - allows you to track what happens on social network (friend feed)

Collaborative Features
Blogging
Calendaring
forums and discussions (digg)
chat rooms -  meebo
image uploads
video uploads
private messages
favorites and appreciation
tagging

Day collab will add above features to add value to content

upcoming features
application platform - facebook, bebo
internetwork connections - connect social netowrks


widgets -

Social networks -
intensify and enhance user generated content
visitor loyalty
new visitors though 3rd oarty network integration
increase page views
40% of mobile traffic is to social networks
reduce spam and abuse thru online reputation magmt

behind firewall...
collab techniques can help:
  • across org chart
  • org chart does not reflect social reality
  • ad-hoc networking
  • across  depts
  • younger generation joining the workforce
Dont: build standalone socialnetwork - do: leverage existing
Dont: create viral only apps   do: make apps social
Dont: require extensie data from users - do: leverage existing content
Dont: lock in users and content - do: encourage mashups and apis

bad social apps have no api
mediocre social apps add api later
good social apps have complete api
superb social apps are buil on top of their own api

apps using twitter for customer data

DAM
image and video upload file sharing and conversion
Advanced collab
blogs, wikis calendaring
CQ5 WCM
widgets, open social apps (internetwork connectivity), sling
photo, slideshow,
CQ5 Social Collab
Advanced collab and social networking capabilities
Web 2.0
  • user centered
  • open agile based on standards
  • simple and lightweight
  • decentralized, distributed and participatory
web 1.0 created by scientists -
web 2.0 created by society

Rich User Experience
Web as a platform
Content is the Intel Inside
  • edmunds - content is king, info becomes the key, not the infrastructure
  • syndicate don't dictate
  • standardize - software apis are no longer a lock-in point
Architecture of Participation
  • emusic
  • force of many - harnessing the power of users, info gets better and grows the more people that use it...
Software above a single device
  • pushing to devices
Lightweight Business Models
  • web 2.0 wcm is almost recession proof - good economic times, expanding business, in bad times, use web to reach different markets
End of Software Upgrade Cycle
  • continual innovation - always updating (launch and iterate) - with cq - release of discrete sets of functionality (OU flash component)
  • Operations must become core competency - availablility, load balancing, caching

Day's Enterprise 2.0 Products
  • CRX JCR Repository - basis of everything they do (JSR 170/283 API)
    • jackrabbit/jcr connectors
  • CQ WCM - CQ DAM - CQ Social Collab
Freedom within a Framework
  • wcm, dam, social collab on a global scale
  • global brand management
  • productivity
Content where it lives
  • flexible content integration
  • jcr standard and secure
Integrated and agile
  • industry leading products and platforms
  • Day will not force being locked in
CQ DAM
Innovative AJAX interface
  • starts with simple search box
CQ Social Collab
  • blog
  • wiki - versioning search
  • CQ Social Collab Calendar



Day Tech Summit - Kodak Gallery 5/28/08

| 0 Comments | 0 TrackBacks
An atypical  but effective implementation of cq
Damon Brennen

Challenges
  • CQ installed, but not fully implemented
  • Project Team Turnover
  • Mgmt on to the next new thing

How we overcame those challenges

  • babysteps

Timeline

  • pilot
  • procrastinator campaign
  • full campaign with cms
  • 90% of bc slots managed by Day (small changes, few new pages)
  • extended biz users
  • business as usual end of rollout

Published over 900 slots

  • all us
  • target
  • canada
  • eu
  • easyshare software
  • all avail meta slots
  • all advertising/headers and meta slots

 

Marketing

  • workflow removed bottleneck
  • reduced publishing promo speed
  • test, update, site content landing pages - ability to "play around"
  • eu stays in sync with us

Choose a template based on slot size

create a page with slot id

 

Strengths

  • easy to use
  • easy to maintain
  • small project team

 

Day Tech Summit - Supercharging Search 5/28/08

| 0 Comments | 0 TrackBacks
Patrick Kent - F5 Knowledge Base

Requiremenst
  • -stemming
  • ranking
  • synonyms
  • restrict by document type
  • preserve product databse mappings
  • search documents by release date

Driven by Lucene

Day had to write a custom interpretor between jcr and xpath that talks to lucene

Lucene's "Tricks"
Stemming -finds derivatives of the wors. Lucene on the fly finds the root text of the word and searches
Fuzzy Search -
Synonyms -  searches synonymns via word net - but cannot map multi-word synonymns.  F5 implemented google style suggestion


Tweaking crx search config
workspace.xml



 

The Designory - Judy Tantana

launched infinit brand worldwide

usability for authors
-use cases
-test tasks
- survey

cq launch
organization
  • structure and operating guidelines for each region
  • clear distinction between global and regional control
Benefits
  • regions will provide their knowedge back into the system for use by other regions for system improvement
  • centralized development of infrastructure
    • allows all regions to have same baseline and capabilities
    • leverages global efforts across regiomms
    • less disparity between regions

First countries launched - China and Russia
  • 2 most difficult countries - character sets and content regulations
  • started small and grew, knowing  they'd have to go back and work infrastructure and development
Design -
  • based on us version
  • business-user friendly
  • recent us design and creative
  • provide as much as possible for users/authors
Business
  • per country cost reduced (support, maintenance and infrastructure)
  • enhancements benefit all countries
  • brand consistency
  • standardized reporting
Technical
  • flash based editing


Global Web Deployment - Infiniti

| 0 Comments | 0 TrackBacks
The Designory - Judy Tantana

launched infinit brand worldwide

usability for authors
-use cases
-test tasks
- survey

cq launch
organization
  • structure and operating guidelines for each region
  • clear distinction between global and regional control
Benefits
  • regions will provide their knowedge back into the system for use by other regions for system improvement
  • centralized development of infrastructure
    • allows all regions to have same baseline and capabilities
    • leverages global efforts across regiomms
    • less disparity between regions

First countries launched - China and Russia
  • 2 most difficult countries - character sets and content regulations
  • started small and grew, knowing  they'd have to go back and work infrastructure and development
Design -
  • based on us version
  • business-user friendly
  • recent us design and creative
  • provide as much as possible for users/authors
Business
  • per country cost reduced (support, maintenance and infrastructure)
  • enhancements benefit all countries
  • brand consistency
  • standardized reporting
Technical
  • flash based editing


OU Day Implementation

| 0 Comments | 0 TrackBacks
Had been using same site since 1995.- lots of out of date content and design, every site out doing their own thing - no unifying navigation, users had to reorient themselves every time they would hit different section of the site.

used a consultant team to review current site - have a new team reporting directly to president - web communication department was born
Redesign and rearchitect the site
challenges - buy-in and keeping project interest

campus partnerships
new components
good design
keep campus (esp stakeholders) in the know

Migration -
  • prioritized sites
  • migration should improve current sites
  • info arcitecture
  • analytics
  • usability
Wireframes
  • 10 templates with minor variations between each
Offer:
  • new design or modify and fit within wireframe
  • department or Partner agency can do it themselves
  • predesigned templates
Components
  • text image
  • dynamic flash -create movement/interest in site without having to do it themselves
  • tab block
Working on this
  • polling
  • comment
  • rss output
  • photo gallery - create thumbnails and set up gallery from media library
  • profile gallery (alumni)
     This would be great for subject specialists/public services
  • calendar - doing some great stuff with calendaring with different levels - can push up events to different department levels all the way up to campus-wide
  • forced alt text in media library
Accessibility
campus education
screen reader available in web comm office
google analytics - use for content and design decisions (screen res, etc)

note: look at museum of art

lessons learned
  • identifying requirements
  • design vs development
  • going live w/out redundancy ( any probs give bad pr to all users)
  • lacking define web requirements
Proud of
  • buy in, interest
  • creating and maintaining achievable schedule
  • documentation - before migrating - understanding responsibilities - bad design and bad content ae not allowed to migrate
  • usability testing - new issues, confirm decisions
  • system free to campus - building functionality with all departments
  • relationship with Day
similarity of language across departments

can we do "fake" rss with reference paragraph?







OU Day Implementation

| 0 Comments | 0 TrackBacks
Had been using same site since 1995.- lots of out of date content and design, every site out doing their own thing - no unifying navigation, users had to reorient themselves every time they would hit different section of the site.

used a consultant team to review current site - have a new team reporting directly to president - web communication department was born
Redesign and rearchitect the site
challenges - buy-in and keeping project interest

campus partnerships
new components
good design
keep campus (esp stakeholders) in the know

Migration -
  • prioritized sites
  • migration should improve current sites
  • info arcitecture
  • analytics
  • usability
Wireframes
  • 10 templates with minor variations between each
Offer:
  • new design or modify and fit within wireframe
  • department or Partner agency can do it themselves
  • predesigned templates
Components
  • text image
  • dynamic flash -create movement/interest in site without having to do it themselves
  • tab block
Working on this
  • polling
  • comment
  • rss output
  • photo gallery - create thumbnails and set up gallery from media library
  • profile gallery (alumni)
     This would be great for subject specialists/public services
  • calendar - doing some great stuff with calendaring with different levels - can push up events to different department levels all the way up to campus-wide
  • forced alt text in media library
Accessibility
campus education
screen reader available in web comm office
google analytics - use for content and design decisions (screen res, etc)

note: look at museum of art

lessons learned
  • identifying requirements
  • design vs development
  • going live w/out redundancy ( any probs give bad pr to all users)
  • lacking define web requirements
Proud of
  • buy in, interest
  • creating and maintaining achievable schedule
  • documentation - before migrating - understanding responsibilities - bad design and bad content ae not allowed to migrate
  • usability testing - new issues, confirm decisions
  • system free to campus - building functionality with all departments
  • relationship with Day
similarity of language across departments

can we do "fake" rss with reference paragraph?







Non-CMS Web Application Development

| 0 Comments | 0 TrackBacks
(Using JCR, REST & AJAX)
David Nueschelar

JCR- An API that allows you to access content bidirectionally from a content repository.
Content repository - best of database and file system combined - superset of all functions of relational database and file system.

  • Hierarchy
  • Sort order
  • Multi-value
  • Full-text search
  • Versioning
  • Access control
  • Unstructured content 
REST
Roy Fielding
REST over JCR
JCR - heavyweight, longterm stable, durable
Developer - wants a way to work with jcr in a quick, agile way
Apache Sling - rest webkit backed by jcr, sling.js & .jst

jsp, groovy, esp, ruby, scala

crx quickstart (download) - available at dev.day.com



Search This Blog

Full Text  Tag