OECD.POLICIES T4 AS A PLATFORM FOR

INNOVATION

T44U Nov 2013

douglas.paterson@oecd.org & nicolas.vahlas@oecd.org

T4 at OECD

• www.oecd.org in production with T4 since August 2012

• > 190K content items (160K English, 30K French, Spanish, German, Russian, ..), but mirrored to different parts of the site; 40K media items

• >260K pages

• Over 300 web editors trained in use of Back Office

• Documents created/month: 1500

• Documents modified/month: 2400

• Visits per month: 1.3M

• Unique visitors per month: 840K

• Page Views per day: 130K

OECD T4 platform

Pub server

Pub (backup)

BO pre-prod/training

Web servers

Back Office servers

Publish Transfer

www.oecd.org

Web editors

Trainees

Irish Times, Nov 21

Irish Times, Nov 21

OECD.Policies: Guided policy environments

Family of online platforms to share policy evidence and

expertise, covering all phases of the policy life-cycle

Next..

• Deep dive into EDU GPS site

• Questions

EDUCATION GPS

NETWORK MODELLING What are we talking about?

EDUCATION GSP

• Oriented Network of Topics

• Topic Nodes:

– Hold metadata

– Are used to categorize / group contents

• 3 Types of Links between nodes:

– Cluster link i.e. link to parent within the same cluster

– Other parent link i.e. link to parent outside of cluster

– Horizontal link i.e. non hierarchical link

NETWORK MODELLING – WHAT?

NETWORK MODELLING How do we represent it in Site Manager?

EDUCATION GPS

… in Site Manager, quite naturally,

• Topic Nodes become sections

• Topic clusters become section trees

• Links become contents

• … and types of links become content types

NETWORK MODELLING – HOW?

… a bit more detailed:

• All links in the network are characterized by:

– A source Node or Section: implicit i.e. where the link content is.

– A target Node or Section: implicit or explicit depending on the type of link.

– Metadata on the link itself: mainly title and weight

NETWORK MODELLING – HOW?

• 3 Content Types, one for each type of link

– Cluster link holds only link metadata: the link itself is materialized by the section hierarchy

– Other Parent link holds metadata + link to a parent section outside of the cluster

– Horizontal link holds metadata + link to a section somewhere in the network

• 1 Content Type to hold the Node metadata: title, description, position (X,Y) …

NETWORK MODELLING – HOW?

NETWORK MODELLING – HOW?

OUTPUT THE NETWORK What are the necessary artefacts?

EDUCATION GSP

• 3 types of JSON files:

− The nodes (nodes.json) i.e. a list of all the nodes of the network with all their metadata

OUTPUT THE NETWORK – WHAT?

− The links (edges.json) i.e. a list of all the links between the nodes along with their metadata.

OUTPUT THE NETWORK – WHAT?

− The topics (equity.json) i.e. one files per topic containing the actual contents to be displayed when the user clicks on a node.

OUTPUT THE NETWORK – WHAT?

OUTPUT THE NETWORK How do we produce the necessary artefacts?

EDUCATION GSP

• Tricky part:

– nodes.json file is mixing section information and content information in the same file.

– edges.json file is mixing explicit link information based on content properties and implicit link information based on section hierarchy

– topic.json files are a mix of several contents of different types

• All JSONfiles need to be:

– Dynamically generated based on the network

OUTPUT THE NETWORK – HOW?

• We had to implement our own navigator: OECD Section Navigator.

• It takes:

– A section ID

– A depth (-1 means all)

– A content type ID (-1 means all)

– 2 Mustache templates: 1 global template and 1 named template which is used recursively by the global template.

• It output the sections and their contents recursively using the Mustache templates.

OUTPUT THE NETWORK – HOW?

• nodes.json

{{#contents}}

{

"featured": {{Featured}},

"id": "{{id}}",

"parentId":

{{#parent}}"{{id}}"{{/parent}}

{{^parent}}null{{/parent}},

"positionX":

{{#positionX}}{{positionX}}{{/positionX}}

{{^positionX}}null{{/positionX}},

"positionY":

{{#positionY}}{{positionY}}{{/positionY}}

{{^positionY}}null{{/positionY}},

"title": "{{name}}",

"educationLevelTags":

{{#educationLevelTags}}

[

{{&educationLevelTags}}

]

{{/educationLevelTags}}

{{^educationLevelTags}}null{{/educationLevelTags}},

OUTPUT THE NETWORK – HOW?

• edges.json

{{#contents}}

{

"sourceTopicId":

{{#Link to section}}"{{id}}"{{/Link to section}}

{{^Link to section}}

{{#parent}}"{{id}}"{{/parent}}

{{^parent}}null{{/parent}}

{{/Link to section}},

"targetTopicId": "{{id}}",

"weight": {{Weight}},

"description": "

{{#Description}}{{Description}}{{/Description}}

{{^Description}}null{{/Description}}

",

"type": "{{contentTypeId}}",

"contentId": {{contentId}}

},

{{/contents}}

OUTPUT THE NETWORK – HOW?

THE REST … … is usual Site Manager stuff

EDUCATION GSP

CONCLUSION

Using Site Manager we were able to:

– Model a complex data structure into Site Manager

– Provide our end user with a back-office for this data structure

– Easily write custom navigator in order to produce the needed JSON files

– Deliver a highly interactive and dynamic website to our clients with little effort and time

EDUCATION GPS