Nicolas Pastorino - REST + recommendation, consume the right content, anywhere - IPC11

REST +Recommendation: consume the right content, anywhere

REST +Recommendation: consume the right content, anywhere Nicolas Pastorino - nfrp@ez.no Director Community - eZ Systems @jeanvoye - http://share.ez.no

REST + Recommendation: consume the right content, anywhere International PHP Conference 2011 - Mainz - October 10th Nicolas Pastorino - nfrp@ez.no#ipc11 Director Community - eZ Systems @jeanvoye - http://share.ez.no

Our agenda :

Our agenda :Multichannel emotion

Our agenda :Multichannel emotion REST

Our agenda :Multichannel emotion RESTExtensible REST API

Our agenda :Multichannel emotion RESTExtensible REST APIContent recommendation

Multichannel : emotion 3

Online content touchesyou,

Online content touchesyou, it spurs emotionsanywhere, on anydevice

You are consumingcontent, all the time

Multichannelcontentdistribution is“emotionsanywhere”

Pre-requisites to multichannel distributionNicolas Pastorino - IPCse11 30/05/2011 8

Pre-requisites to multichannel distributionSeparation of layoutand content at the 1content source level Nicolas Pastorino - IPCse11 30/05/2011 8

Pre-requisites to multichannel distributionSeparation of layoutand content at the 1content source levelDo not compromise onuser experience 2 Nicolas Pastorino - IPCse11 30/05/2011 8

Pre-requisites to multichannel distributionSeparation of layoutand content at the 1content source level “The Superman Effect” Aral Balkan, DPC11Do not compromise onuser experience 2 Nicolas Pastorino - IPCse11 30/05/2011 8

Pre-requisites to multichannel distributionSeparation of layoutand content at the 1content source level “The Superman Effect” Aral Balkan, DPC11Do not compromise onuser experience 2 “There is a lot of effort going into improving customer experience. It is key to get consistency across different channels so their experience does not vary” Jim Daviesni Nicolas Pastorino - IPCse11 30/05/2011 8

Pre-requisites to multichannel distributionSeparation of layoutand content at the 1content source level “The Superman Effect” Aral Balkan, DPC11Do not compromise onuser experience 2 “There is a lot of effort going into improving customer experience. It is key to get consistency across different channels so theirHave a single source experience does not vary” Jim Daviesniof content 3 Nicolas Pastorino - IPCse11 30/05/2011 8

Pre-requisites to multichannel distributionSeparation of layoutand content at the 1content source level “The Superman Effect” Aral Balkan, DPC11Do not compromise onuser experience 2 “There is a lot of effort going into improving customer experience. It is key to get consistency across different channels so theirHave a single source experience does not vary” Jim Daviesniof content 3 “Publishers usually cant afford a dedicated editorial team per channel” Nicolas Pastorino - IPCse11 30/05/2011 8

Are 3rules of thumbenough ?

Are 3rules of thumbenough We’re ? hardly off the ground. Let’s dig further...

SingleContentSource / CMS

Monetized Content StreamsSingleContentSource / CMS

Monetized Content Streams Mobile ApplicationsSingle / Smartphones, TabletsContentSource CMS

Monetized Content Streams Mobile ApplicationsSingle / Smartphones, TabletsContentSource CMS Push 3rd party CRM, ERP Content Newsletters

Monetized Content Streams Mobile ApplicationsSingle / Smartphones, TabletsContentSource CMS Push 3rd party CRM, ERP Content Newsletters Print Legacy publication chains

Monetized Content Streams Mobile ApplicationsSingle / Smartphones, TabletsContentSource CMS Push 3rd party CRM, ERP Content Newsletters Print Legacy publication chains Social Media

"Multichannel media consumers have higher levelsof engagement than those present in only onechannel.The more one watches TV, listens to the radio,spends time online, etc., the more advertising theyconsume.This shows that multichannel contentdistribution will also have an important impacton the publishers revenue structure. It willevolve to become a competitive, critical, enablingtechnology for marketing communications."

Having a REST ? :)

Having a REST ? :) We are not there yet, let’s dig further

“Media companies as well as consumer brands mustrecognize that adding mobile to the multichannel mixdoes not mean creating a mini-channel. Thosebuilding mobile strategies should recognize that: • Mobile is not just about shrinking the desktop experience, • The user environment is an element of the (mobile) experience, • Mobile users are not simply a subset of online users – some are new.”

Least CommonDenominator :

Least CommonDenominator :a REST API

Those were the functional basics to increase your REACH through multiple channels

Those were the functional basics to increase your REACH Now through come the multiple technical channels bits

REST 16

REpresentationalStateTransfer

REpresentationalStateTransferREST is a set of principles that define how Web standards, such asHTTP and URIs, are supposed to be used.• Give every “thing” an ID• Link things together (“HATEOAS”) (cf David Zuelke’s keynote)• Use standard methods• Resources with multiple representations• Communicate statelessly

REpresentationalStateTransferREST is a set of principles that define how Web standards, such asHTTP and URIs, are supposed to be used.• Give every “thing” an ID• Link things together (“HATEOAS”) (cf David Zuelke’s keynote)• Use standard methods• Resources with multiple representations• Communicate statelessly h"p://www.infoq.com/ar4cles/rest-‐introduc4on h"p://en.wikipedia.org/wiki/Representa4onal_State_Transfer

REpresentationalStateTransfer h"p://www.infoq.com/ar4cles/rest-‐introduc4on h"p://en.wikipedia.org/wiki/Representa4onal_State_Transfer

REpresentationalStateTransferKey goals of REST include:• Scalability of component interactions• Generality of interfaces• Independent deployment of components• Intermediary components to reduce latency, enforce security andencapsulate legacy systems h"p://www.infoq.com/ar4cles/rest-‐introduc4on h"p://en.wikipedia.org/wiki/Representa4onal_State_Transfer

Extensible REST APIat the core of the eZ Publish CMS 19

At the core of the eZ Publish CMSExtensible REST API REST as a core featureNicolas Pastorino - IPCse11 30/05/2011 20

At the core of the eZ Publish CMSExtensible REST APIDedicated front-controllerNicolas Pastorino - IPCse11 30/05/2011 21

At the core of the eZ Publish CMSExtensible REST API REST setup REST eZP REST request FC eZ Publish web-‐requestNicolas Pastorino - IPCse11 30/05/2011 22

At the core of the eZ Publish CMSExtensible REST API Mapping content into resourcesNicolas Pastorino - IPCse11 30/05/2011 23

At the core of the eZ Publish CMSExtensible REST API Makes data availableNicolas Pastorino - IPCse11 30/05/2011 24

At the core of the eZ Publish CMSExtensible REST API Makes data reusableNicolas Pastorino - IPCse11 30/05/2011 24

At the core of the eZ Publish CMSExtensible REST API Content is essentially liberatedNicolas Pastorino - IPCse11 30/05/2011 25

At the core of the eZ Publish CMSExtensible REST API URI patternNicolas Pastorino - IPCse11 30/05/2011 26

At the core of the eZ Publish CMSExtensible REST API Just a token to trigger your rewrite rule Call + GET Host / Preﬁx / Provider / Version / params ezpRestPreﬁxFilterInterfaceNicolas Pastorino - IPCse11 30/05/2011 27

At the core of the eZ Publish CMSExtensible REST API Preﬁx Just a token to trigger your rewrite ruleProvider ezpRestPreﬁxFilterInterfaceVersionNicolas Pastorino - IPCse11 30/05/2011 27

Prefix filterezpRestPrefixFilterInterfaceCurrent providerCurrent parsed version valueNicolas Pastorino - IPCse11 30/05/2011 28

Versioned APIclass ezpRestRouter extends ezcMvcRouter{ public function createRoutes() { // ezpRestApiProvider $routes = array( new ezcMvcRailsRoute( /content/node/:nodeId/listAtom, ezpRestAtomController, collection ), new ezcMvcRailsRoute( /content/node/:nodeId/list, ezpRestContentController, list ), new ezcMvcRailsRoute( /content/node/:nodeId, ezpRestContentController, viewContent ), new ezcMvcRailsRoute( /content/node/:nodeId/fields, ezpRestContentController, viewFields ), new ezcMvcRailsRoute( /content/node/:nodeId/field/:fieldIdentifier, ezpRestContentController, viewField ), new ezcMvcRailsRoute( /content/object/:objectId, ezpRestContentController, viewContent ), new ezcMvcRailsRoute( /content/object/:objectId/fields, ezpRestContentController, viewFields ), new ezcMvcRailsRoute( /content/object/:objectId/field/:fieldIdentifier, ezpRestContentController, viewField ), new ezpRestVersionedRoute( new ezcMvcRailsRoute( /foo, myController, myActionOne ), 1 ), new ezpRestVersionedRoute( new ezcMvcRailsRoute( e/foo, myController2 or myControlerWhichExtendsmyController, myBetterAndScalingAction ), 2 ), ); return ezcMvcRouter::prefix( /api, $routes ); }} Nicolas Pastorino - IPCse11 30/05/2011 29

Versioned APIezpRestVersionedRoute Version makes the notion version a part of the routing decisionNicolas Pastorino - IPCse11 30/05/2011 30

At the core of the eZ Publish CMSExtensible REST API Build your own ﬂavor, extend the interface(s)Nicolas Pastorino - IPCse11 30/05/2011 31

Extending the interface REST providersNicolas Pastorino - IPCse11 30/05/2011 32

Extending the interfaceezpRestProviderInterfaceNicolas Pastorino - IPCse11 30/05/2011 33

Overview of hooksthe places where you can go wild.

Nicolas Pastorino - IPCse11 30/05/2011 35

Route setup - Exampleclass ezpRestRouter extends ezcMvcRouter{ public function createRoutes() { $providerRoutes = ezpRestProvider::getProvider( ezpRestPrefixFilterInterface::getApiProviderName() )->getRoutes(); $routes = array( new ezpMvcRailsRoute( /fatal, ezpRestErrorController, show ), new ezpMvcRailsRoute( /http-basic-auth, ezpRestAuthController, basicAuth ), new ezpMvcRailsRoute( /login/oauth, ezpRestAuthController, oauthRequired ), new ezpMvcRailsRoute( /oauth/token, ezpRestOauthTokenController, handleRequest), // ezpRestVersionedRoute( $route, $version ) // $version == 1 should be the same as if the only the $route had been present new ezpRestVersionedRoute( new ezpMvcRailsRoute( /foo, myController,myActionOne ), 1 ), new ezpRestVersionedRoute( new ezpMvcRailsRoute( /foo, myController,myActionOneBetter ), 2 ), ); return ezcMvcRouter::prefix( /api, array_merge( $providerRoutes, $routes ) ); }} Nicolas Pastorino - IPCse11 30/05/2011 36

Extensible REST APIKey features 37

Key featuresExtensible REST API Content resourcesNicolas Pastorino - IPCse11 30/05/2011 38

Key featuresGET /[api]/v1/content/object/ <objectId>/fields HTTP/1.1Nicolas Pastorino - IPCse11 30/05/2011 39

Key featuresfields/<fieldname> type (datatype string) identifier (attribute identifier) value (string representation of data) id (object attribute numerical ID) classattribute_id (class attribute numerical ID)Nicolas Pastorino - IPCse11 30/05/2011 40

Key features GET /[api]/v1/content/object/ <objectId>/field/ <FieldIdentifier> HTTP/1.1Nicolas Pastorino - IPCse11 30/05/2011 41

Content RecommendationYooChoose, eZ Recommender Engine 42

A tough selection needs tobe made amongst the infiniteamount of content published

A tough selection needs tobe made amongst the infiniteamount of content publishedWhichone is myslope ?

A tough selection needs tobe made amongst the infiniteamount of content published

A tough selection needs tobe made amongst the infiniteamount of content publishedI only have 30minutes a day,which postsshould i read ?

A tough selection needs tobe made amongst the infiniteamount of content publishedDoesn’t itfeel like thissometimes :

One sometimes needs ahelping hand to choose theright slope to ride, the right content to consume

One sometimes needs a helping hand to choose the right slope to ride, the right content to consumeContentrecommendation

Content recommendationNicolas Pastorino - IPCse11 30/05/2011 47

Content recommendationTrack contentconsumptionNicolas Pastorino - IPCse11 30/05/2011 47

Content recommendationTrack contentconsumption + Learn content metadataNicolas Pastorino - IPCse11 30/05/2011 47

Content recommendationTrack contentconsumption + Learn content metadata = Content RecommendationNicolas Pastorino - IPCse11 30/05/2011 47

Cloud-based learning of behaviors using • Events “Viewing, Purchasing, Rating, Sharing” • Models Users who viewed A also viewed B • Stereotypes Affinity calculated against larger sets of content

Content recommendation Hybrid filtering Increasing recommendation quality by combining methods for qualifying behaviorsNicolas Pastorino - IPCse11 30/05/2011 49

Content recommendation Hybrid filtering Increasing recommendation quality by combining methods for qualifying behaviors Content-based filtering  “Content like this” ~Nicolas Pastorino - IPCse11 30/05/2011 49

Content recommendation Hybrid filtering Increasing recommendation quality by combining methods for qualifying behaviors Content-based Collaborative filtering filtering  “Content like this”  “Customers who were interested in this product also bought …” ~Nicolas Pastorino - IPCse11 30/05/2011 49

Content recommendation Hybrid filtering Increasing recommendation quality by combining methods for qualifying behaviors Content-based Collaborative Community- Stereotype- Context-based filtering filtering based filtering based filtering filtering  “Content like this”  “Customers who  “Customers like you  Recommendation  Recommendation were interested in also bought …” combines content depends on this product also cluster with affinity location, time, bought …” vectors mood, environment … Rock ~ ~ Pop R&BNicolas Pastorino - IPCse11 30/05/2011 49

Content recommendation Hybrid filtering Increasing recommendation quality by combining methods for qualifying behaviors Content-based Collaborative Community- Stereotype- Context-based filtering filtering based filtering based filtering filtering  “Content like this”  “Customers who  “Customers like you  Recommendation  Recommendation were interested in also bought …” combines content depends on this product also cluster with affinity location, time, bought …” vectors mood, environment … Rock ~ ~ Pop R&B + A/B testing + near cold-start recommendationsNicolas Pastorino - IPCse11 30/05/2011 49

Content recommendationI/O through RESTNative connection with any HTTP-enabled client( simple with PHP, native extension for eZPublish CMS )Cloud-based : scalesDifferent methods for event tracking : JS, built-inthe CMS, Nicolas Pastorino - IPCse11 30/05/2011 50

Famous Last Slides 51

RECAPMultichannel emotion

RECAPMultichannel emotion REST

RECAPMultichannel emotion RESTExtensible REST API

RECAPMultichannel emotion RESTExtensible REST APIContent recommendation

Find me on Twitter : @jeanvoyeRate this talk : http://joind.in/3852Slides available soon at http://slideshare.net/jeanvoyeeZ Communityhttp://share.ez.noeZ Publish Community Projecthttps://github.com/ezsystems/ezpublishhttp://share.ez.no/downloadhttp://share.ez.no/get-involved Thank you !YooChoose, recommendation enginehttp://www.yoochoose.comeZ Systems & eZ Publish Enterprise Editionhttp://ez.no

http://share.ez.no	91
http://lanyrd.com	14
http://paper.li	10
http://us-w1.rockmelt.com	1
http://a0.twimg.com	1

Nicolas Pastorino - REST + recommendation, consume the right content, anywhere - IPC11

by Nicolas Pastorino on Oct 10, 2011

Accessibility

Categories

Upload Details

Usage Rights

5 Embeds 117

Statistics

Nicolas Pastorino - REST + recommendation, consume the right content, anywhere - IPC11 Presentation Transcript