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.

 

eLog UI library is now available at GitHub

We have recently significantly updated eLog libraries and started releasing the code through GitHub. Currently we opened the eLog UI part at (https://github.com/eLifeLogTeam/elog) for the public. The eLog server part, which now includes the updated key-value store and the event pattern mining CEP engine, is available to eLifeLog.org members. If interested, please join the community. 

eLifeLog API under development

We decided to progressively open the eLifeLog APIs. What we are working on is the documentation (http://www.elifelog.org/lab/elog_doc/). Please check it time-to-time to help us for improvement. A formal release will include the compelete set of source codes for lifelogging clients and servers. We expect that you can build your own lifelog Apps with a very short lines of codes. This documentation is the preview of undergoing works.

2nd eLifelog API release schedule and news

We've been working hard to develop a next generation eLifeLog APIs and services. As its start, our eLifeLog.org host is moved to the new one hoping to get a better performance for document management and code distribution. By any chance, if you have accessed eLifeLog.org using a fixed IP address, please change them to the new one.

The time zone issue in using federated tables is resolved.

A timestamp field included in the federated table definition to link remote tables in the cloud is not affected by the local time zone setting in the user query (See last two queries in below examples.) Thus it has been recommended to use a UNIX timestamp field instead. Today we released new table definitions to resolve this incovenience. The trick is using VIEWs atop federated tables.  Now you can use the image_UTC_timestamp field without troubles if you set the time zone properly (See first two of below examples).

Pages

Subscribe to Front page feed