COPS Expert Group Wardenburger Hof 31. Jan. 2012

COPS Expert Group

Wardenburger Hof

31. Jan. 2012

Agenda

Seite 2

08:30 – 08:45 Welcome / Warm UP

08:45 – 09:00 Definitions „Let‘s speak one language“

09:00 – 09:30 Introducing & Explanation Systemarchitecture

- Analogy of COPS2 and COPS3- COPS 3 Components

09:30 – 10:30 Logic of COPS 3

- Shift of processes by COPS-Framework Modules- Inheritance (Master > Default > Customer)

- LayoutMaster

- Auto-Teaser

- Asset-Handling

10:30 – 10:45 Coffee Break

Agenda

Seite 3

10:30 – 12:30 Useful Helpers

- Update Script- Content Classes- Content Class Sharing- Asset Manager- Subnav Teaser- Attribute Teaser- Loadbalancing Sites- COPS Tools (Operator / Translation)- IPS TxtR

12:30 – 13:15 Lunch Break

13:15 – 14:15 Omniture Session

14:15 – 14:30 Next Steps

14:30 – 14:45 Timelines

Agenda

Seite 4

14:45 – 15:30 Future Development


15:45 – 16:00 Wrap Up

16:00 – 17:45 AOB (Any Other Business)- Open Round- Question & Answers

19:30 – Open Bowling

Agenda

Seite 5





09:30 – 10:30 Logic of COPS 3


- LayoutMaster

- Auto-Teaser

- Asset-Handling


Definitions – Let‘s speak one language

Seite 6

To understand what we are talking about…

We start to document „Definitions“

Handout for your reference

Agenda

Seite 7





09:30 – 10:30 Logic of COPS 3


- LayoutMaster

- Auto-Teaser

- Asset-Handling


Introducing & Explanation Systemarchitecture

Seite 8

The RedDot analogy between COPS 2 and COPS 3 in terms of:

• Physical-Structure

• Project-Structure

• Workflow „Set up customer“

• Workflow „Update customer“

Seite 9

Physical-Structure of COPS 2

- Mixed System• 7 real Server• 3 virtual Server

- Virtual Server from COPS 3

- Serverjobs seperated

- Maintained by eCommerce

Introducing & Explanation Systemarchitecture - Analogy of COPS 2 and COPS 3

Seite 10

Physical-Structure of COPS 3

- 7 virtual Server (live now)

- 7 publication Server

- 8 virtual Server prepared to go live

- 1 Mass-Storage „LOON“ Device for all Server

- Serverjobs combined

- Maintained by internal IT-Department


Seite 11

Project-Structure of COPS 2

- 1 Default Project for (nearly) all Countries & Languages

- Structure changes in Default affects all Countries & Languages

- All customers need a RedDot Project

Almost 600 RedDot projectsto maintain


Seite 12

Project-Structure in COPS 3

- Global Master

- Master-Default Structure

- 1 Default Project for each Country & Language

- RedDot Project isn‘t necessary to serve a customer


Seite 13

Workflow „Set up customer“ - COPS 2


• Share ContentClasses• Create & Share AssetFolder

• Ex-/Import from Default

• Copy empty Cover• Delete Language-Variants

Seite 14

Workflow setup customer in COPS 3


• Delete content

• Share ContentClasses

• Copy Default

Seite 15


Workflow „Update customer“

Introducing & Explanation Systemarchitecture

Seite 16

COPS 3 Components

• In terms of Physical

• In terms of Software

Seite 17

Introducing & Explanation Systemarchitecture - COPS 3 Components

Physical Components

7 Virtual RedDot Server

5 Virtual COPS-Framework Server

2 MySQL Databas Server

Seite 18

Introducing & Explanation Systemarchitecture - COPS 3 Components

Software Components

Segmenting of Server

Flexible in terms of scaling & switching

Agenda

Seite 19





09:30 – 10:30 Logic of COPS 3


- LayoutMaster

- Auto-Teaser

- Asset-Handling


Logic of COPS 3

Seite 20

Shift of processes by COPS-Framework Modules

• Parser and Reverse• Plugins and Assets• Web• Build and Sync

Inheritance (Master > Default > Customer)

• Inheritance• Updateprocesses• with or without RedDot-Project?

LayoutMaster

Auto-Teaser

Asset-Handling

Seite 21

Logic of COPS 3 – Shift of processes (COPS-Framework Modules)

Parser and Reverse

- The Parser-Module parse & validate the published content and write it into the database

- The Reverse-Module returns Default Content of a requested Page in RedDot

Seite 22

Plugins and Assets

- The Module Plugins deliver COPS-Framework Tools and Informations to RedDot, like „Asset-Manager“ or „Price-Handler“

- all Assets (images, CSS and other media elements) are stored on COPS-Framework (10.1.102.125)


Seite 23

Web

- Customer Preview after RedDot, before live

- 1:1 how it goes live e.g. with prices and hide pages

http://10.1.102.125/web/85001773


Seite 24

Build and Sync

- Release Customer pages to the Content Server

- 1:1 as it‘s on the Web-Module except the Domain settings

- Synchronize IPS Templates


Seite 25

Logic of COPS 3 - Inheritance (Master > Default > Customer)

Inheritance

- No Inheritance in RedDot

- Inheritance only from COPS-Framework till live (Web Module, Build Module)

- CSS, Operator-, KeyAccount-, Attribute-Teaser-Setting don‘t inherit from Default

Seite 26

Updateprocesses

- Structure: emtpy pages reference key & global name only

- Content: all filled elements on each page


Seite 27

RedDot Project – with or without it?

RedDot Project Pro‘s Con‘s

with

completly flexible & free in terms of structure

completly flexible & free contentwise

have to take care of default changes

updates could be necessary

depends on more than 1 system

without

fast & easy way to go online

always „up to date“

structure belongs to default

content belongs to default

Accelerate & Slim Processes

More independently

Reconfigurable


Seite 28

Logic of COPS 3 - LayoutMaster

- Same Structure & different Content

- Useful for Customers in different Countries or Languages

„Amazon DE“ is LayoutMaster for „Amazon UK“

Seite 29

Logic of COPS 3 - Auto-Teaser

- Automatically generated Teaser

- Easy saved if a product is set to hide

Seite 30

Logic of COPS 3 - Asset-Handling

No longer publishing of Assets from RedDot –

only Path & Filename

Faster Publicationprocess

Multisided editable: RedDot, COPS Tools, FTP

Centralized Default images • slim Operator Directories

Fast replacement by overwrite Assets only at one location

Agenda

Seite 31





09:30 – 10:30 Logic of COPS 3


- LayoutMaster

- Auto-Teaser

- Asset-Handling


Agenda

Seite 32





14:15 – 14:30 Next Steps

14:30 – 14:45 Timelines

Useful Helpers - Update Script

„There is a page on Budni that we don‘t have in our default. How can we get it?“

„We do not have the new disney teasers. How can we get them?“

„Our whole greetingcards section is still christmassy, can you change that?“

Seite 33

Seite 34


Update ScriptStructure & ContentUpdate ScriptStructure & Content

Master Project GermanyMaster Project Germany

Master Project NetherlandsMaster Project Netherlands Master Project SpainMaster Project Spain

start

Seite 35


Functional workflow update script

1. Check if object in target project exists

2. Create or update object in target project

Object can be a whole page, a teaser or just a carousel slice!

Seite 36


Update Script StructureUpdate Script Structure

Default ProjectDefault Project

start

Seite 37


Useful Helpers - Content Classes

What is a content class?

teaserteaser carouselcarouselmain pagemain page

and many more ...

Seite 38

master globalmaster global

master de_DEmaster de_DE

default de_DEdefault de_DE

mueller de_DEmueller de_DE

All projects inherit global content classes.

master de_ATmaster de_AT master fr_FRmaster fr_FR

default de_ATdefault de_AT default fr_FRdefault fr_FR

fnac fr_FRfnac fr_FRhartlauer de_AT

hartlauer de_AT

Seite 39

Useful Helpers - Content Class Sharing

master de_DEmaster de_DE

default de_DEdefault de_DE

mueller de_DEmueller de_DE

Master projects can have individual content-classes.

Seite 40


mueller de_DEmueller de_DEChild projects can have individualcontent-classes.

Seite 41


Only accessible within RedDot

Seite 42

Useful Helpers – Asset Manager

Now accessible within RedDot and Operator-Tool

Seite 43


10.1.102.125

RedDotRedDot FrameworkFramework

• no need to syncronize

• direct live access

Seite 44


Two Directories

/images /assets

/global

/de_DE

/fr_FR

/85001773

/85024155

/85001320

Seite 45


/images/fr_FR/keyvisual.jpg

/images/global/online-lessons.jpg

/assets/85001773/promo_calendar.jpg

Seite 46


Seite 47

Useful Helpers – Subnav Teaser

Define where to show it

insert as many teasers as you want

Seite 48

Useful Helpers – Subnav Teaser

Example: Christmas „Delivery Times“

Default Mail Customer Default POS Customer

Seite 49

Useful Helpers – Attribute Teaser

define two variants in one project

define attribute value for each variant

appropriate variant will be shown incustomer project

Seite 50

Useful Helpers – Attribute Teaser

http://10.1.114.120:888/cms

COPS 2

COPS 3

logged in users

logged in users

server ipserver ip

Seite 51

Useful Helpers – Loadbalancing Site

Operator-Tool„Control Center for project specific tasks“

Translation-Tool„Translating text resources quickly“

Seite 52

Useful Helpers – COPS Tools

Operator-Tool

Seite 53


Operator-Tool

3 main features

11 create new projects

Seite 54


Operator-Tool

Creating new projects

Seite 55


Operator-Tool

3 main features

11

22

create new projects

editing css directly

Seite 56


Editing css directly

Operator-Tool

Seite 57


Operator-Tool

3 main features

11

22

33

create new projects

editing css directly

project specific functionality

Seite 58


Project specific functionality

Operator-Tool

Seite 59


not individualized individual startpage individual project

always sync allpages automatically

not syncing specificpages automatically

never sync pagesautomatically

Seite 60

Useful Helpers – Blacklist

Translation-Tool

publishedpublished translatedtranslated

Seite 61


Translation-Tool

Worst-case scenario

translatetranslate

returnreturn

editedit

publishpublish

returnreturn

Translation-Tool

RedDot

Seite 62


Translation-Tool

Solution

11 Complete return only after initial translation

22 Only return single pages after initial return

Seite 63


Agenda

Seite 64





14:15 – 14:30 Next Steps

14:30 – 14:45 Timelines

Agenda

Seite 65





14:15 – 14:30 Next Steps

14:30 – 14:45 Timelines

Agenda

Seite 66





14:15 – 14:30 Next Steps

14:30 – 14:45 Timelines

Next Steps

Seite 67

Next Steps

Seite 68

Agenda

Seite 69





14:15 – 14:30 Next Steps

14:30 – 14:45 Timelines

Timelines

Seite 70

Translation done

Master done

Language default done

Switch Off Microsite

Set Up defaultCustomerprojects

Set Up Affiliates

Set Up individual Customerprojects

Prepared Photokina

2012 2012 2012

Timelines – Status of Translations

Seite 71

AT – ready

UK / USA / CA – ready

PL – ready

CZ – ready

SL ??

SK ??

DK ??

NOR ??

SWE ??

FIN ??

IT ??

FR– ready

NL – ready

BE ??

HU ??

ES ??

RO ??

LIT ??

CH

Agenda

Seite 72



15:45 – 16:00 Wrap Up



Future Developments

Seite 73

• Finder for• Cewe-photobook• Gifts• Greeting Cards

• Display of prices in a graphic

• Split of Main CSS into seperate CSS files

• Integration of Services – • Design Service• Seminar / Videotutorials / FAQ-Client

• SEO Landingpages

• SPOT – Web SelfService

• Some New Products

• Redesign of categories

• Mobile apps

Agenda

Seite 74



15:45 – 16:00 Wrap Up



Agenda

Seite 75



15:45 – 16:00 Wrap Up



Agenda

Seite 76



15:45 – 16:00 Wrap Up



Documents

COPS Expert Group Wardenburger Hof 31. Jan. 2012