About

The eLog library was initially developed as a research prototype and later published for lifelogging researchers in 2010 to help them easily analyze heterogenous data and complex visualization. It has been kept growing with the progress of mobile computing environments and recently its UI part is released with GPL v3 license for wider usage. The eLog UI library is optimized for mobile environment and can get easily integrated with existing Web services.

Who We Are

The original work was proposed by Pil Ho and later extended the work with collaboration with 28 researchers around the world who contributed their lifelogs, collaborated for lifelog analysis and share research results to build up an open lifelogging platform for the public. Pil Ho has been keeping the development updating the library following up the progress in mobile computing.

Updates

  • Nov. 2014: Change the web page skin using bootstrap.
  • Nov. 2014: Published elog UI library as GPL v3.
  • Oct. 2014: Version up eLog library and documentation.

 

Using the network storage to build up personal lifelogs

In this experiment, a linux-embedded network storage is used to extend its function to manage one's personal lifelogs. For the first experiment, 4TB My Book Live Duo was chosen due to its cheap price, SSH supports and good enough size to start lifelogging. This page will list up how a user can set up her personal cloud installing eLifeLog services on Live Duo for private lifelogging. Other network storages, if they support Linux, should be similarly supported using information in this lab.

Installation

First you have to buy it whether from Amazon or anywhere else, find a good deal and have it next to your home router. Follow the given setup instruction for initial installation. 

Technical Specifications to Know

Live Duo has a linux and things to know for system management are:

  • By default WD authorize to install packages from "debian lenny" and "squeeze" version
  • Package installation

Problems

Now you have a personal cloud but you will soon find an issue questioning whether this is a real private cloud or not because if you want to access your cloud, then you have to give all information to WD's service server. For instance if you want to browse photos at your home NAS server, then all data should be first uploaded to WD servers and then you access WD server (not your home cloud) to see the data which is probabily not what you pay for.

Modification

So people already have started to keep thier things under their hood. One problem of Live Duo's linux kernel is that any update of the WD firmware wipes out your own installed upgrades and new packages. WD perfomrs this update by swaping a file partition thus the delivered firmware (i.e. any update means reverting system parts, not user data, to the factory default) is not compatible with all upgrades you can make.

For eLifeLog services, a server should support (as of Augst 2013) APM (Apache+PHP+MySQL) and optionally Java for real-time CEP and additional packages for various media analysis. They are not completely embedded into the eLifeLog data due to its open architecture (and limited supports) to utilize existing technologies.

Start Installing What Nedded

Apache

Apache HTTP server is already there but to have more control and higher security follow this instruction to set up http web server. eLifeLog APIs work well both for HTTP and HTTPS.

PHP

PHP installation should follow this forum post. Don't go more than PHP installation.

MySQL

Install from Optware

 

OpenVPN

Now you want to access your private cloud from anywhere at anytime and do not resort to other free (but have to give away your personal data) gateway services. For this, install OpenVPN and register free dns service (ex. no-ip.org) . Also accordinly install client Apps or software to acccess your home cloud (For Mac, we used Tunnelblick). 

eLifeLog stuffs

Now you have a safe and a pretty secure private cloud (VPN + http). Visit eLifeLog source codes to install your lifelog managing software. No data will be transferred out of your private network from now on :)