Search Engines, Analytics and Semantics 
Developments In Analytics And Big Data
Who am I? 
•CEO of iO1 
•I have worked across Government and large enterprises for 20+ years 
•Wannabe Geek
This presentation 
•The focus will be on giving you an under standing of how to combine key areas using open source toolsto enhance your organisations knowledge management 
•Presentation is based on Invotra our intranet product we are working with the Home Office to roll out 
•Everything is available freely and built on open standards 
•You should be able to go away and build this by the end 
•Targeted at simple solutions that can be broadly adopted to encourage participation by experts (like you).
Why Open source? 
•Open is “usually” 
•Easier to integrate, Massively scalable 
•More componentised 
•Easier to fix -You can see the code 
•You can see what people are planning on doing in future 
•Free 
•Communities are fantastic, its easy to contribute 
•Please join
INTRANETS 
Discovering
Why intranets 
•An internal system 
•Unstructured and ad-hoc data 
•An everyday anytime tool for everyone 
•Different usages in nearly every scenario 
•Apart from the lunch menu ;-) 
•Rarely recognised for the knowledge it contains 
•A place for everything else i.e. Not covered by a line of business app 
•Made up of multiple systems (search, cms, semantics, analytics) 
•Its never the same
Areas the stack is focussed on 
•Saving minutes 
•Discovering knowledge 
•Handling staff turnover 
•Sustainable knowledge management 
•Extracting knowledge as opposed to defining a million reports 
•Properly personalised 
•Understanding context and capture knowledge not just data 
•Helping users to help organisations 
•Focussed Simplicity
CMS 
•Help people 
•Discover information / knowledge 
•Input information / knowledge not just data 
•Create relationships between information 
•Maintain information / Knowledge 
•Share 
•By being an interface to everything else 
•Essentially the users tool
Search Engine 
•Help people find 
•Better information and knowledge 
•More quickly 
•Tailored to your own requirements 
•Biased the way you want 
•Leveraging your knowledge 
•Find knowledge inside peoples heads by looking at what they write to infer what they know
Analytics 
•Instant feedback 
•Real world knowledge 
•Discover real usages 
•See patterns in data and usage 
•See usage impact factors 
•Do analysis on creation, this gives you insights into what's happening now 
•Analysis of versions
Semantic web 
•According to the W3C 
•"The Semantic Web provides a common framework that allows data to be shared and reused across application, enterprise, and community boundaries.
Base Model 
Create 
Add Semantics 
Store 
Analysis 
Discover
Models for adding semantic data 
•Forced on after input 
•Advanced Guesswork 
•Added during input 
•Users know what they meant 
•Forced on at display 
•Useful when dealing with intelligent UI’s
QUICKSHOWANDTELL
We need some text 
The standard enhance can detect cities such as parisand people like David Heath from the UK who works for the UK Department for Environment Food and Rural Affairs
Add it using a normal edit screen
Click annotate, stuff happens
User checks if this right?
What user gets
What the search engine can see
INTEGRATION 
Big Data
Linked Data Cloud
Connecting things
What we want
How we get it
Custom Vocabularies 
•Don’t start from scratch 
•Spend effort on modelling using Linked Data to save you hassle 
•Use search to extraction from existing data 
•Store your vocabularies in a source that is open ;-) 
•Allow users to tag content and analyse this against the content they are tagging to gain insights
What problems does all this solve? 
•Better quality answers to user questions/searchs 
•Giving users the ability to provide background to their content 
•Storing the information within the content so its shared easier between systems / departments 
•Retaining knowledge after authors have left Organisation 
•Giving organisations the ability to intelligently discover data
A STACK
The Semantic Web
Semantic CMS Architecture 
Thanks to the IKS project
Drupal has semantics built in
Pretty and open
Intelligent search
Semantics = Stanbol 
•Apache Stanbol'smain features are: 
•Content EnhancementServices that add semantic information to “non-semantic” pieces of content. 
•ReasoningServices that are able to retrieve additional semantic information about the content based on the semantic information retrieved via content enhancement. 
•Knowledge ModelsServices that are used to define and manipulate the data models (e.g. ontologies) that are used to store the semantic information. 
•PersistenceServices that store (or cache) semantic information, i.e. enhanced content, entities, facts, and make it searchable.
TOOLSFORENHANCING& SCALING 
Opensource
Extra’s
http://www.getopt.org/luke/
Q&A 
Fintan Galvin 
CEO 
iO1 Limited 
Twitter: Suncao 
Email: fintan@io1.biz

Harnessing search engines for KM

  • 1.
    Search Engines, Analyticsand Semantics Developments In Analytics And Big Data
  • 2.
    Who am I? •CEO of iO1 •I have worked across Government and large enterprises for 20+ years •Wannabe Geek
  • 3.
    This presentation •Thefocus will be on giving you an under standing of how to combine key areas using open source toolsto enhance your organisations knowledge management •Presentation is based on Invotra our intranet product we are working with the Home Office to roll out •Everything is available freely and built on open standards •You should be able to go away and build this by the end •Targeted at simple solutions that can be broadly adopted to encourage participation by experts (like you).
  • 4.
    Why Open source? •Open is “usually” •Easier to integrate, Massively scalable •More componentised •Easier to fix -You can see the code •You can see what people are planning on doing in future •Free •Communities are fantastic, its easy to contribute •Please join
  • 5.
  • 6.
    Why intranets •Aninternal system •Unstructured and ad-hoc data •An everyday anytime tool for everyone •Different usages in nearly every scenario •Apart from the lunch menu ;-) •Rarely recognised for the knowledge it contains •A place for everything else i.e. Not covered by a line of business app •Made up of multiple systems (search, cms, semantics, analytics) •Its never the same
  • 7.
    Areas the stackis focussed on •Saving minutes •Discovering knowledge •Handling staff turnover •Sustainable knowledge management •Extracting knowledge as opposed to defining a million reports •Properly personalised •Understanding context and capture knowledge not just data •Helping users to help organisations •Focussed Simplicity
  • 8.
    CMS •Help people •Discover information / knowledge •Input information / knowledge not just data •Create relationships between information •Maintain information / Knowledge •Share •By being an interface to everything else •Essentially the users tool
  • 9.
    Search Engine •Helppeople find •Better information and knowledge •More quickly •Tailored to your own requirements •Biased the way you want •Leveraging your knowledge •Find knowledge inside peoples heads by looking at what they write to infer what they know
  • 10.
    Analytics •Instant feedback •Real world knowledge •Discover real usages •See patterns in data and usage •See usage impact factors •Do analysis on creation, this gives you insights into what's happening now •Analysis of versions
  • 11.
    Semantic web •Accordingto the W3C •"The Semantic Web provides a common framework that allows data to be shared and reused across application, enterprise, and community boundaries.
  • 12.
    Base Model Create Add Semantics Store Analysis Discover
  • 13.
    Models for addingsemantic data •Forced on after input •Advanced Guesswork •Added during input •Users know what they meant •Forced on at display •Useful when dealing with intelligent UI’s
  • 14.
  • 15.
    We need sometext The standard enhance can detect cities such as parisand people like David Heath from the UK who works for the UK Department for Environment Food and Rural Affairs
  • 16.
    Add it usinga normal edit screen
  • 17.
  • 18.
    User checks ifthis right?
  • 19.
  • 20.
    What the searchengine can see
  • 22.
  • 23.
  • 24.
  • 25.
  • 26.
  • 27.
    Custom Vocabularies •Don’tstart from scratch •Spend effort on modelling using Linked Data to save you hassle •Use search to extraction from existing data •Store your vocabularies in a source that is open ;-) •Allow users to tag content and analyse this against the content they are tagging to gain insights
  • 28.
    What problems doesall this solve? •Better quality answers to user questions/searchs •Giving users the ability to provide background to their content •Storing the information within the content so its shared easier between systems / departments •Retaining knowledge after authors have left Organisation •Giving organisations the ability to intelligently discover data
  • 29.
  • 30.
  • 31.
    Semantic CMS Architecture Thanks to the IKS project
  • 32.
  • 33.
  • 34.
  • 35.
    Semantics = Stanbol •Apache Stanbol'smain features are: •Content EnhancementServices that add semantic information to “non-semantic” pieces of content. •ReasoningServices that are able to retrieve additional semantic information about the content based on the semantic information retrieved via content enhancement. •Knowledge ModelsServices that are used to define and manipulate the data models (e.g. ontologies) that are used to store the semantic information. •PersistenceServices that store (or cache) semantic information, i.e. enhanced content, entities, facts, and make it searchable.
  • 36.
  • 37.
  • 38.
  • 39.
    Q&A Fintan Galvin CEO iO1 Limited Twitter: Suncao Email: fintan@io1.biz