Add Google Fit data into Log

• determine tags/scope for register this type of information
• be possible to add into Log a Google Fit data by choosing a time space
• create a routine to sync between existent logs

Generation new Log

• be possible to choose which templates parts will be used to create new log
• be possible to choose which group of templates will be use to create new log

• Adding an book reading registration:
• • Actual Page
• • Notes from reading so far
• • General Review
• • Book Registration
• • • ALL ISBN fields
• • • Cover if not present

Add to Log Google Maps Location History Data

• determine tags/scope for register this type of information
• be possible to add into Log a Google Map Location History data by choosing a time space
• create a routine to sync between existent logs

Add scripts for create and check personal directory of Logs

• determine mininal structure of directory to store all Logs data.
  • must include text logs space
  • must include audio logs space
  • must include image logs space
  • must include video logs space
• check if exist these spaces, create them if not.

Create an interface for management of OPML playlist for podcasts

Create minimal structure for electron interface

Include a integration between Google Tasks and Lifelog.

1. Every sync, will be created a note with a lista of "to-do" (check mark - [ ] ) for a tasks that should be done on that day.
2. If is ticked from Tasks app/google mail will be update on the note as done ( - [ x ] )

On this version the reverse is not possible for the better understading which state é mandatory or where will be possible compares the date of note and date of task list.

reference: https://developers.google.com/tasks/quickstart/python

** Package ** are the minimal unit deal by the system, like 'daily packages' that represents a virtual compressed directory containing all files linked into that day, ex: 02_08_2023.llpkg (life log extension).
Acceptance criterias:

• Should be compressed
• Should contain a header with the version as this package was created
• Should contain a timestamp representing the date and time of package creation
• Should be encrypted with the key of the creator