Introduction


This Tutorial discuss the different data architecture supported by EachScape:

From the Source of the data (a 3rd party CMS, EachScape Cloud Collection, a data feed (RSS, XML, JSON,...) to the way the data is stored on the device.


Controlling how source of data are processed for consumption by the app is extremely important.

We do our best to explain, if you have questions reach out to the community with the QA at the end of this article.


Overview


EachScape supports multiple source of data:

  • 3rd party CMS
  • EachScape Cloud Collection
  • Data Feeds: RSS, XML, JSON
  • Tabular Data

On the Device, Data is stored in 2 different ways:

  • As a Live Feed (Often called Remote Data source)
    • An Internet connection is required to display the data.
    • In that case the data is stored 'as it' the feed comes directly from your server as is stored on the device as it. 
  • In an SQL Database. (Often called Local Data source)
    • NO Internet connection is required to display the data.
    • You can change the contents of On Device SQL DB at a specified time, if there is a data connection, then the app will update the contents that are pulled into the app.
    • In that architecture EachScape processes the data from any or the source above and stores it into a SQL Lite Database. That Database is then sent to the device and the apps can query that locally stored database.
 
Data are stored in 2 different ways on device: 
Live Feed or SQL DB

When you create a new Data Source and Select Data Feed, you are offered with these 2 choices


Either of these On Device architecture have their Pros & Cont.

Experience will best help you determine what architecture is optimal for you application.


In most cases the simplest approach which is to connect your feeds directly into your applications.  That is the Live Feed (Remote Data Source) architecture.

We recommend using Live Feed (Remote Data Source).

 

 


 2 Ways to Store Data on Devices

  1. Live Feeds

 

  1. SQL DB



1. Live Feeds

 

A data connection is required to access the data.

 

Example of Data feed: http://feeds.bbci.co.uk/news/rss.xml

In that architecture the Feed (RSS, XML, JSON) goes directly from any CMS (WordPress, Drupal, EachScape Cloud Collection, ..) to the App. 

Configurations

For a Data Feed

  • What     : Data feed (RSS, XML, JSON) coming from a CMS (WordPress, Drupal, The Platform, ..) 

  • Where  :  In Data management system - under the Connect tab -

  • When   :  When you add the Feed.

  • TUTORIAL: Configure a feed as Live (Remote): Connect a Data Source (RSS, XML, JSON).


For a Cloud Collection

  • What     : Cloud Collection as a Live Feed.

  • Where  :  In Data management system - under the Connect tab -

  • When   :  When you configure the Cloud Collection

  • TUTORIAL:  Configure a Cloud Collection as a Live Feed (Remote):  Live Feed or On Device SQL DB from a Cloud Collection

 

 

2. SQL DB

In that configuration EachScape server creates a SQL Database and send that DB to the Device.
 The Database is locally stored on the device.
 

No data connection is required to access the assets.

Configurations


For a Data Feed

  • What    : Data feed (RSS, XML, JSON) coming from a CMS (WordPress, Drupal, The Platform, ..) 

  • Where  :  In Data management system - under the Connect tab -

  • When   :  When you add the Feed.

  • TUTORIAL: Process Data Source as an On Device SQL DB


For a Cloud Collection

  • What    : Cloud Collection as a Live Feed.

  • Where  :  In Data management system - under the Connect tab -

  • When   :  When you configure the Cloud Collection.

  • TUTORIAL:  Configure a Cloud Collection to create an On Device SQL DB: Live Feed or On Device SQL DB from a Cloud Collection


SUMMARY

This schema is here it help you understand the different architecture and some of their Pros &Cont.

 


Learn More
-  Process RSS, XML, JSON as a SQL Database
 -  Process RSS, XML, JSON as a Live Feed
-  Live Feed or On Device SQL DB from a Cloud Collection