Open Content & Live Content Cloud (LCC)

Interrupt at any time, ask questions. We are here to learn you more about Open Content and Live Content Cloud (LCC).

Navigation:
Next section     : [space-bar].
Previous section : [shift] + [space-bar]

At the end of each section you have navigation buttons :
 - Next section
 - Previous section
 - Back to Agenda
            

Agenda

Presentation of who we are

Cinque Terre
Cinque Terre

Hans Bringert

Hans has been with Infomaker since May 2013.

Mainly works with Open Content together with Tim Terlegård

Jacob Tallberg

Jacob has been with Infomaker since 2015.

Mainly works with LCC (previously LCA) together with Jimmy Bernljung.



What is Open Content

Open Content is a content agnostic store for digital material. Any digital material can be stored in Open Content. Normally xml-metadata files are used to describe the content uploaded and properties are extracted from the metadatafiles using XPATH 2.0 expressions.

The installed Open Content is described in a Support Page this page holds information which parts of Open Content are installed on which server, version and how to start/stop it. Also how to find logs for the different services.

Open Content as a black box
  • Long-time archive
  • Back-end for web-, tablet- and mobile publishing
  • Integrated with Newspilot and Everyware
  • Integrate with any presentation layer
  • XLibris search and admin UI

The parts of opencontent are :

Frontend :

The different parts will be described below



Open Content Frontend Server

Open Content "Frontend server" consists of a Wildfly Application Server which holds implementation for the Open Content Rest API . A Webserver for XLibris and Open Content Admin UI is also running on the front end server. Open Content with one frontend server


Open Content Scaling Frontend Server

Open Content "Frontend server" can be scaled behind a load balancer. Normally we scale the frontend servers for web publishing Open Content servers. Scaling is done automatically depending of the current traffic situation.
Open Content scaled frontend server


Open Content Backend Server(s)

Open Content "Backend server"execute services such as the Search Index (Solr), Indexing and a MySql Database. These services can be executed on same server or in a mix of severs.
Open Content scaled backend server

Solr is the search engine used in Open Content backend, it uses Lucene, teh serach syntax is the same as the Lucene syntax



Open Content Storage

Open Content can use normal disk as storage or AWS S3. If you want I can show the file structure of an S3 bucket.
Open Content storage


Open Content AWS setup

A typical AWS Open Content setup looks like this.
Open Content storage
The Public Open Content is serving web publishing, and the content is replicated to it by a filtered replicator which only replicates article and images from the Archieve Open Content which stores all digital material produced in for example Newspilot. It is possible to share the same S3 store for both Open Content Servers.


Open Content Configuration

Configuration leadin

Configuration is done in the admin UI of Open Content

In Open Content content is grouped into content types. You define how to map content into the different content types. The main part of the configuration is how to defina property names and extract propety values using XPath extractors.

Indexfields are used to store the properties in Solr.



Open Content Replicator

Replication is used when content needs to be copied or moved to another Open Content. Replication is performed with a special service called Replicator.

The replicator is an "application/service" which can be configured to replicate objects between two different Open Contents

Possible to use filters if only a specific type of contents should be replicated.

Also possible to set to use preview instead when replication this way the preview image will be replicated instead of the high resulotion Image

Errors during replication can be tracked, retryable errors can be replicated automatically.

The different types of replication can be performed:

  • Full replication with query
  • Incremental replication
  • Batch replication
  • Partial replication
  • Eventlog replication

Demo of the replicator in action, installed on my machine (localhost). Must be connected to VPN.


Open Content Upload

Upload is a vital part of Open Content. Used by Newspilot NOC and Replicator. Easy to use by any system.

Upload to Open Content is done using HTTP multipart request. Instructions how to use curl to upload content can be found in our Wiki here

Some small curl scripts will show how to upload three different types of content, Article, Image and Page also show how to perform delete using curl.

Article dd5087ec-2b45-4ecb-9ce1-a49eccd02b1c
Image   ec21387c-1f29-43d4-bfbf-173e6812ead1
Page    d66d4aa8-fa62-40cd-9e86-5297e8b93c3a
                                

Check that the content items exists, use this query:

uuid:dd5087ec-2b45-4ecb-9ce1-a49eccd02b1c OR uuid:ec21387c-1f29-43d4-bfbf-173e6812ead1 OR uuid:d66d4aa8-fa62-40cd-9e86-5297e8b93c3a
                                

Delete them using :

./delete-article.sh
./delete-image.sh
./delete-page.sh
                                

The delete script can you find here if you want to test it!

Upload them using :

./upload-article.sh
./upload-image.sh
./upload-page.sh
                                



Finnish Stemming

We have installed Finnish stemming in Solr used by Open Content. This is an optional feature that can be turned on for a specific installation. In the alma-demo solr Finnish stemming is installed.

Demo instructions:

NOTE:

To be able to perform this demo we need to connect to Hämeen Sanomat VPN.
This means that only the computer connected to VPN can access the Hämeen Sanomat XLibris

We will use to XLibris clients to perform this demo XLibris Hämeen Sanomat (no stemming) and Alma-Demo XLibris (with stemming)

If an article contains the word "talo", then there will be a hit whenever any of these words are in the query:

  • talo
  • talossa
  • taloon
  • talosta

If an article contains the word "kuohuviiniä", then there will be a hit whenever any of these words are in the query:

  • kuohuviiniä
  • kuohuviini
  • kuohu
  • viini

Another example to test is "kortesaari"

Example query in both XLibris:

kuohuviiniä AND (uuid:8398cd0b-629a-47cf-8ab2-0287b999cad2 OR uuid:5c30e10f-afa9-420a-b163-5dcc1a787b1f)

Finnish stemming is activated on index fields of type "text". If the index field is of type "string" or "string_lowercase" no stemming is applied.



Open Content Notifier

Notifier can be used to release cache, or send notifications to LCA/LCC. Possible to use Notifier for any http POST receiving server. Register the url towards which the notification details should be sent

Notifier is described in our wiki here

If you want to see what a notification looks like in RabbitMQ



Live Content Cloud

LCC is used when you want push data to subscribers. For example used in apps for live update of already downloaded content.

The different parts of Live Content Cloud is :

  • Infocaster
  • Query Streamer
  • Native Pusher

LCC


Infocaster

Infocaster API
Laboration tool see here


Query Streamer

Query Streamer API


Native Pusher



Logotype of Infomaker

Powering publishers

Infomaker arbetar med lösningar för publicering, arkivering och distribution av innehåll åt marknadens största mediehus och tidningar. Med över 250 kunder i Sverige, Norge, Finland och Holland, och mer än 20 års branscherfarenhet, kan vi erbjuda våra kunder det allra bästa när det kommer till publicering, oavsett om det gäller print eller digitalt.

Vårt redaktionella system Newspilot har varit journalisters och redaktörers arbetsredskap i snart 15 år. Till detta kopplar vi Open Content, molnbaserade arkivlösningar, E-papper, Nyhetsappar, Writers och Dashboards. Allt för att göra vardagen enklare för dem som skapar nyheterna, och upplevelsen starkare för den som tar del av dem.

En försmak av vårt universum

Våra tekniska produkter och tjänster underlättar produktionen för hela det redaktionella publiceringsflödet - från skrivande stund till slutanvändaren.
App-plattform

Skapa din nyhetsapp på nolltid tack vare vårt vältestade modulsystem. Personalisera lite eller mycket, möjligheterna är oändliga.

E-papper

Snabbt, smidigt och med exceptionellt skarp upplösning. En ny, förbättrad, läsupplevelse för era läsare!

Newspilot

Marknadens bästa redaktionella verktyg för planering och publicering till både print och digitalt.

Open Content

Vi tar hand om ditt innehåll, lagrar och vårdar det i molnet - alltid tillgängligt när du behöver det.

ew
Everyware

Vart som helst, när som helst med Everyware. Publicera till alla dina kanaler genom en knapptryckning.

wr
Writer

Ditt skrivverktyg för publicering i digitala kanaler. Infomaker Writer är öppen för att integreras med exempelvis Newspilot eller andra redaktionella system. Du rör dig sömlöst mellan olika program och system för en optimal användarupplevelse.

12 000
Users

are using our systems every day

15 000
Articles

are written in our tools today

7 000 000
Readers

do we deliver news to every day

50+
Employees

and more to be