Data Model

The data model consists of the following items

• DiaryActivities (not the Android UI-Activities, that's why we prefix the name with Diary)
  • name
  • color
  • id (_ID)
  • aliases (in case the name is not obvious and the same activity should be found by different names)
  • hierarchical structure (link to parent)
  • required conditions
  • activation conditions (with probability)
  • (?actions like set ringtone volume?)
• Conditions (to autodetect activities, planned by nyi)
  • name
  • id (_ID)
  • type (location, acceleration, WLAN, BT, time, calendar entries, NFC)
  • parameter (e.g. SSID for WLAN)
• Diary
  • id (_ID)
  • Activity entry (start + stop time)
  • Manual log (text/image linked to an activity)
• Locations (only filled if configured, planned but nyi)
• did (foreign key for diary entry)
• location
• Templates (planned, but nyi)
  • id (_ID)
  • Activities with Conditions, but they are not active
  • on adding of a new activity the templates shall be searched for a fitting template and the template conditions to be suggested but values to be filled.

An additional idea might be to add tags. E. g. the activity "planting" could have a tag attached for linking it to "potato" or "tomato", while the activity "harvesting" could share the same tag...