Building a semantic enterprise content management system v2


Published on

How we built a practical ontology-driven corporate intranet portal
in the cloud in three months using off-the-shelf technology. Presented at SemTechBiz London, September 20th 2012.

Published in: Technology, Education
  • Be the first to comment

Building a semantic enterprise content management system v2

  1. 1. Building a Semantic EnterpriseContent Management System from Scratch How  we  built  an  ontology-­‐driven  corporate  intranet  portal in  the  cloud  in  three  months  using  off-­‐the-­‐shelf  technology SemTechBiz  London,  September  20th  2012 Ron  Michael  Ze-lemoyer,  Chief  Innova6on  Officer,  Fynydd @ronmichael  ・
  2. 2. Introductions
  3. 3. Mobile & Desktop Apps Web Apps & Servicesfynydd          :in-­‐id  -­‐  noun Semantic Knowledge Management1.    a  word  of  Welsh  origin   meaning  mountain. User Interface Design2.    a  company  of  big  thinkers,   innovative  problem  solvers   and  doers. Systems Architecture Reporting & Analytics
  4. 4. How we got here “TranslaDonal   @thomson medicine  meets  the   reuters #kolexperts semanDc  web” @jwindz #sla2009 #semtech @candp @ronmichael #stardog Cambridge @fynydd @usbank #semtechbiz Steve  Jobs Crea;vity  is  just  connec;ng  things.
  5. 5. Semantic enterprise content management represent recognize respond  to   meaning  of  content goals  of  users
  6. 6. Design principles
  7. 7. Tame your content Pablo  Picasso Every  act  of  crea;on  is   first  an  act  of  destruc;on.
  8. 8. Design for a great user experience useful& usable& desirable& valuable& findable& accessible& credible& Peter Morville’s User Experience Honeycomb
  9. 9. Don’t reinvent the wheel Henry  Ford I  invented nothing  new. I  simply  assembled   the  discoveries  of   other  people.  Had  I   worked  fiCy  or  ten   or  even  five  years   before,  I  would  have   failed.  So  it  is  with   every  new  thing.
  10. 10. Be agile CUSTOMER INDIVIDUALS+ COLLABORATION INTERACTIONS over  contract  nego;a;on over  processes  and  tools WORKING   RESPONDING SOFTWARE TO  ollowing  a  plan over  f CHANGE over  comprehensive  docs The Agile Manifesto
  11. 11. Keep moving Lexus Anything  not is  moving  bac  moving  forw ard   kward.
  12. 12. Implementation
  13. 13. Architecture dotNetRDF
  14. 14. Ontology • Define  your  goal:  increase  findability • Build  simply  and  as  you  need  it • Sell  stakeholders  on  its  future  value • Provide  simple  management  tools
  15. 15. Ontology Manager Customer Template Individual   Employee Contributor Procedure Content Person News Thing Product Business   Account Savings   Location Personal   Account Business   Account Savings  Account Branch State Personal   Region Savings  Account
  16. 16. Browse • Research  and  curate  top  level  menus • Generate  dynamic  sub  menus • Generate  related  content  links • Create  friendly  URLs  
  17. 17. BrowseCurated   menus Push-­‐down mega-­‐menu Breadcrumbs Dynamic   related  links
  18. 18. Search • Start  with  autocomplete • Use  a  “snap-­‐to-­‐grid”  approach • Make  it  contextual  and  adap;ve • Go  above  &  beyond  expecta;ons
  19. 19. Search User  input Context Content   SPARQL OperaDons SQL metadata Ontology LINQ Content data Public Secret AnalyDcal datasets sauce data Results  &  suggesDons
  20. 20. Authoring • Encourage  “modular”  content • Don’t  require  authors  to  be  ontologists   • Build  a  great  editor   • Balance  manual  &  automa;c  tagging  needs
  21. 21. Authoring
  22. 22. Start building! • Tame  your  content – Semtech  can’t  fix  bad  content   • Design  for  a  great  user  experience – Make  authoring,  browsing  and  searching  fun   • Don’t  reinvent  the  wheel – Use  exis;ng  vocabularies,  frameworks,  code  and  experts • Be  agile – Build  incrementally  &  itera;vely,  especially  ontology • Keep  moving – Plan  and  budget  for  constant  improvement
  23. 23. fynydd.comDon’t  forget  your  towel.