devdocs/specs/core-log-business.txt

@@ -1,13 +1,15 @@
 Business history log
 
 FROM CASE 79
-A central event log used to track major changes to business objects and major events of significance in AyaNova.
-??Has some sort of checksum or verification so we can tell it wasn't fucked with (too hard to implement, would be something like a blockchain?)
+A central event log used to track major changes to business objects and major events of significance in AyaNova
 Consumed by various widgets for record history purposes
-Default feature, no need to turn on or off keeps logs for 45 days, users who want more can 
+Default feature, no need to turn on or off
 Items are only removed from log when source object is deleted (and replaced with a deleted entry and textual description of deleted item)
-Needs a cleaner job that periodically looks for non-existant objects that are logged
 Has to handle a scenario where there is no data for an object because in future we will likely have a purge feature or maybe a feature to turn it off and needs to accept that scenario
+?FUTURE: Has some sort of checksum or verification so we can tell it wasn't fucked with (too hard to implement, would be something like a blockchain?)
+?FUTURE: Needs a cleaner job that periodically looks for non-existant objects that are logged
+?FUTURE: keeps logs for 45 days initially keeps forever or until object is deleted
+
 
 ROUTES
 ------

devdocs/todo.txt

@@ -20,7 +20,7 @@ CODING WORK
 
 Overall plan for now: anything standing in the way of making the initial client shell UI needs to be done first, everything else can wait
 	- Audit log		
-		- Route for retrieving as log format for reading (like reports: one for specific object id and type, one for user id as log of what they've been doing etc)
+		- Make sure trial generated data generates log events so that we can properly test with huge dataset
 		- Test with huge dataset
 	- Remove CREATED from all objects now that event log tracks it
 	- Localized text