Data Journal is the latest iteration of my long-running quantified self project. This iteration of the whole Life Tracker/Personal Data Warehouse. It’s not technically a total re-write of my previous project, but it’s pretty darn close.
Tldr
- Data Journal is a system for capturing, maintaining, & using event-based data
- Data Journal is a set of data shapes (i.e. regular objects) & tools for operating on them
- A
DataJournal
is comprised of arrays ofEntry
s andDef
s, where:
- A
Def
is a definition of a known key/value pair that may exist onEntry
s- An
Entry
is an event that happened in a give time period, containing zero-to-many keys/value pairs described byDef
sDataJournal
s can be:
- merged together without duplication
- modified (via
transaction
s)- queried (via
query
s)- The PDW is a system for managing multiple
DataJournal
s, stored across disparate databases and/or files
A few more details:
- The Data Journal code is not class-oriented.
- All data shapes can be serialized to and parsed from JSON without data loss
- No “instances of class” are required, everything is based on regular objects
- Classes are used as namespaces for related functions
- A
DataJournal
is comprised of an array ofEntry
s and an array ofDef
s- Metadata properties of elements (i.e.
Entry
s andDef
s) start with an underscore
- Metadata properties of elements (i.e.
- A
Def
defines known key/value pairs that may exist onEntry
s- A
Def
must contain_id
,_updated
, and_type
keys Def
s may have other keys as wellDef._id
values cannot start with an underscore
- A
- An
Entry
is a record of something that happened at some point in time- An
Entry
must contain_id
,_updated
, and_period
keys - An
Entry
may have other keys as well - An
Entry
typically contains one or many entry “points”, which have an associatedDef
- An entry point is a key/value pair on an
Entry
whose key is aDef._id
- An entry point is a key/value pair on an
- An
- Merging two or more
DataJournal
s will only keep one copy of each element based on its_id
, in the case where multiple copies exist, it will only keep the one with the largest_updated
value (i.e. the newest one is kept) - Data Journals may be written to (via
transaction
) or read from (viaquery
) using regular objects- A
Transaction
may update elements viacreate
,replace
,modify
, ordelete
create
- will always create & not look for existing data with the same
.
- will always create & not look for existing data with the same
replace
- if the
_id
is not in theDataJournal
, will create it - if the existing
_id
in the journal is older, will fully replace it - if the existing
_id
in the journal is newer, will not affect it at all
- if the
modify
- if the
_id
is not in theDataJournal
, will create it - if the existing
_id
is older, it will retain any keys not explicitly overwritten by the modification - if the existing
_id
is newer, will not affect it at all
- if the
delete
- will always mark the matching element
_id
as_deleted = true
- will always mark the matching element
- A
Query
is an object full ofEntry
-filtering parameters
- A
- Other utility classes operating on
DataJournal
s do exist, but are decoupled from each other and the Data Journal code does not depend on them.- Examples:
Summarizer
,Validator
,Overviewer
,Aliaser
, and a host ofTranslator
s andConnector
s which allow for reading/writing from static files and databases, respectively
- Examples: