devdocs/todo.txt

@@ -24,6 +24,7 @@ Import / update
 TODO:
 	All changes should be schema updates now so users don't have to erase their database at this point (too much hassle to explain it)
 	Remove chinchoo CSV export code, update front end and docs to hide it completely
+	Back end consider removing zipping up of data, why do that, how big is it really?  Won't nginx just compress it anyway being json and all so it would double compress wasting time anyway.
 	Front end work to support json or csv files
 	help docs to explain it
 		help docs should have an example of at least two records of JSON and CSV to show the full field names and somehow indicate which ones are absolutely required
@@ -31,6 +32,7 @@ TODO:
 	back end code to work with convention to import
 		back end must ignore any linked id's but can use viz fields to match perhaps?
 		(we could use a different format for the import json since it's not a direct one to one json to class anymore, but maybe still viz fields to match?)
+	
 	Front features:
 		Should warn the user about updating versus importing etc, maybe just a warning when accepting OK do the import that specifies 
 		"the following operation may change existing data" are they sure and have read how it works with a MORE infor link to manual