1 / 49

(BLANK) Startup

(BLANK) Startup. regjeringen.no / government.no – where Topic Maps and Search govern the User experience. (Marta Prerovska – Head of web section) / Petter Thorsrud – Senior advisor Departementenes servicesenter / Government Administration Services Topic Maps 2007 – Oslo 21.03.2007.

calvine-jerom
Télécharger la présentation

(BLANK) Startup

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. (BLANK) Startup

  2. regjeringen.no/ government.no– where Topic Maps and Search govern the User experience (Marta Prerovska – Head of web section) / Petter Thorsrud – Senior advisor Departementenes servicesenter / Government Administration Services Topic Maps 2007 – Oslo 21.03.2007

  3. Goals for the presentation • Some background information • Metadata, Topic Maps and Search – and their mutual enhancement • Examples … • Challenges and solutions when handling 280.000 pages of legacy data • Status and success criteria • and hopefully some inspiration for others to cross the chasm…

  4. Goals for regjeringen.no (from Strategy document) Main goal: regjeringen.no should be the Government’s and the Ministries’ main electronic channel for communication with the public, allowing them to find information they need, without making personal contact Partial goals: • To assist in presenting the Government’s political issues • To facilitate the dissemination of information and documents from the Ministries – to enable public participation in democratic processes • To use technology for two way communication • To provide access to information about decisions and policies that create the foundation for the citizens’ rights, duties and possibilities • To offer information on activities in the ministries

  5. Target groups • The Public • Professional external users (including the Media) • Professional internal users Other target groups will find useful information, but are not given special priority All main target groups should be offered navigationand channels suited to their particular needs and knowledge level

  6. Odin 2006

  7. Odin (1995) 2000 – 2007 (RIP) Emphasis on the different Ministries • News and current matters – Ministry/Odin • Documents – Ministry/Odin • Organization/persons – Ministry • Topics – Ministry • Barriers between the Ministries – limited cooperation • The Government and the Prime Minister hardly visible Still – considering its age – a functional and quite impressive site

  8. regjeringen.no 2007 Emphasis on Topics, the Government/policies and the Ministries. - Stronger focus on the Portal • Topics –Portal/Ministry – common structure • The Government’s Big Issues– Portal/PMO • News and current matters – Ministry/Portal – related to Topics • Documents – Ministry/Portal – related to Topics • Organization/persons – Ministry • Navigation across Ministry boundaries (based on Topics)

  9. The process • Based on Strategy document • Initial focus on concept and user experience • Sufficient time for analysis and iterations in the concept phase • External experts/consultants involved – Dream team? • Close contact with Ministries • Final result according to goals and expectations (to a large extent)

  10. 3 parallel areas of development: Topic Maps Technology Stability Security Domains Hardware Lines Technology choices CMS Search engine optimization Performance Hosting Search and retrieval Databases Conversion Organization and content Content classification Training User forum Editor training Administration Reference group Open house Quality check Publishing Support Image editing Topics, keywords, Topic Map Text creation, approval routines Roles and rights System Development Integration Security Functionality Structure Database WAI standards Ease of use Interaction design Availability for all Conversion Import User testing Indexing Search engine

  11. (BLANK) Requirements and technology

  12. Metadata as foundation for regjeringen.no • Metadata necessary to handle content, topics and navigation • Publishing solutions (CMS) had limited possibilities • Possible solution: Add on module for metadata • Advantages of using Standards – Topic Maps - This is not a “Topic Maps driven” site…

  13. Metadata dimensions (facets) handled by the system • Document type – implicit • Topic – explicit (description of content) • Ownership – implicit • Time – implicit • Status (Current/expired – transfer to Document Archive) • Language (additional dimension) All relations between elements handled by Topic MapTopics (content) hierarchy – Documents – Org. units – Persons – Speeches/articles – Rules/regulations – …

  14. Additional requirement: legacy and future URLs • Old ODIN URLs based on docKey • Future URLs based on (predictable) Unique ID • Should link to EPiServer Page ID 280.000 web pages 30.000 “documents” http://odin.dep.no/fad/norsk/dok/regpubl/stmeld/071001-040002 http://www.regjeringen.no/id/STM200520060026000DDDEPIS http://www.regjeringen.no/nb/dep/fad/dok/regpubl/stmeld/20052006/Stmeld-nr-26-2005-2006-.html?id=201024

  15. Commercial, stable and supported products. Off the shelf solutions (??) EPiServer FAST TM Core CMS – Search Engine – Topic Map Engine

  16. EPiServer functionality • Content creation and editing • Handling of implicit metadata • Presentation • Rights, scheduling, alerts … • Common interface for other components

  17. FAST functionality • Free text search • Configured search – lists • Navigators for all search pages • Support for classification of content (?)

  18. TM Core functionality • Base for Topics navigation • Handles all associations and relations between elements • Handles URLs and IDs for legacy data and new documents

  19. Principles for Topics structure Topics: 400 + Keywords: 3000 +

  20. (BLANK) Now – some examples

  21. Search for personvern (privacy) Example: search for Personvern

  22. Appears to be an authoritative document on the topic Personvern Example: search result

  23. Topic page about Personvern • Email alerts, topic search • Topic navigation, associated laws/reg., useful links, external units, contact info Example: topic page Personvern • Selected article on Personvern

  24. Example: article about Personvern • External unit – responsible for the topic

  25. Example: Datatilsynet about/link to About Datatilsynet - with contact info and link to site

  26. Example: Back to Personvern – Topic search for Stortingsmelding • Search for Stortingsmelding

  27. Example: Search result - St.meld. 17

  28. Language versions Example: St.meld. Language versions

  29. Example: Search in St.meld • Search for personvernin the report

  30. Example: Search results in document • Chapter on personvern

  31. So far so good – but is this all? • Maybe we ’ll find something important on the Ministry’s front page? Example: Chapter in the Report • Note contextual navigation in complex document

  32. Example: Ministry front page • Special section on Information society for all

  33. Example: Special section on The information society for all • Chapter on Personvern…

  34. Enough ?? Example: Chapter on Personvern

  35. (BLANK) : Metadata classification supported by search/semantic analysis

  36. Metadata dimensions handled by the system • Document type – implicit • Topic – explicit (description of content) • Ownership – implicit • Time – implicit • Status (Current/expired – transfer to Document Archive) • Language (additional dimension) All relations between elements handled by Topic MapTopics (content) hierarchy – Documents – Org. units – Persons – Speeches/articles – Rules/regulations – …

  37. Metadata are fine – but who wants to handle them? Crucial to focus on the user experience – for end users and for authors/editors End users want alternative navigation forms, context sensitive, relevant links to Topics and Documents – based on metadata (but they don’t know it…) Authors/editors must add metadata – unwanted task • Implicit or automatic classification is preferred • Editor support: semantic analysis to suggest topics • Import: automatic classification

  38. Automatic classification of content – Intentions Topic (and Keyword) classification of legacy data and new content Two intentions: • Auto classification of import (AutoClassify) • Classification suggestions when publishing new content (AutoSuggest) Process: • Describe algorithms • Gather training set of documents • Tuning mechanisms • Evaluation of results • Repeat iterations • Reconsider algorithms?

  39. Automatic classification of content – Challenges • Document training sets of sufficient quality • Sufficient quantity • Representative documents • Documents covering multiple topics • Large documents contain text about “everything” • Top level Topics are very generic – not suitable for auto classification • Keywords are not included – yet • No aid for adding associations • Quality of algorithms – Search engine’s “intelligence”

  40. Automatic classification of content – status Big, hairy goals: • To classify all content by Keyword and Topic – automatically on import, support on creation Results at launch: • Topics are autoclassified – but not with sufficient quality (results are not shown) • Publishing support is of insufficient quality – and has no user interface • Keywords have not been implemented • But we’re not giving up!

  41. (BLANK): Results

  42. Results – regjeringen.no February 2007 (1) User experience • Vastly improved Search • Stemming, synonyms, navigators • Alternative navigation • Left menu, global, URL, right side navigation: Topics, associations, other… • Navigation in long/complex documents • WAI compliance improved • Visual appearance • All user groups find an enhanced experience

  43. Results – regjeringen.no February 2007 (2) Content • New content created around Topics • Old and new content is classified / tagged • More focus on politics and news • More images, pictures • Content available/visible across Ministry borders • All target groups find useful information

  44. Results – regjeringen.no February 2007 (3) Organization – people • 200+ authors and editors are using the system – and getting the job done • Committed and demanding – and happy – users • Training and support from central staff • Information – participation – commitment – training – documentation – support throughout the process

  45. Results – regjeringen.no February 2007 (4) Technology – systems development • Stable system – still a few bugs • User friendly – for all involved parties • Technology base for other systems • Intranets for Ministries • Existing portals and applications – will be ported • Plans for enhancements and further development • The system will never be complete and finished!

  46. Crossing the Chasm Source: mhtml:http://faculty.msb.edu/homak/HomaHelpSite/slides/Crossing%20the%20Chasm%20553-06.mht!CrossingtheChasm553-06_files/frame.htm/ Ken Homa – Geoffrey A Moore - Steve Pepper

  47. Success factors • Clear strategy • Involvement and commitment of users • Sufficient time for concept development and specification work • Mature technology (?) • Domain knowledge • Dream team • Enthusiasm and lots of hard work!

  48. Thank you foryour attention! marta.prerovska@dss.dep.no petter.thorsrud@dss.dep.no

  49. (BLANK) End

More Related