devdocs/todo.txt

@@ -23,8 +23,7 @@ Import / update
 		Back end import must handle each item one by one and decide if update or add and act accordingly working with the convention
 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

docs/8.0/ayanova/docs/ay-ex-export.md

@@ -12,19 +12,7 @@ The Export extension is accessed from the [extensions](ay-extensions.md) menu it
 
 ## How the Export extension works
 
-Data is exported exactly as it's stored at the sever, there are no locale conversions made.
-
-Formats available are .json and .csv (comma separated values).
-
-### JSON
-
-JSON is most appropriate for preserving the original structure of the data being exported and a good "round trip" format as it's most compatible with importing back into AyaNova. 
-
-JSON format is widely used and supported and you should choose this format where possible. There are also numerous conversion utilities and online sites if you need your data in another format from JSON.
-
-### CSV
-
-.csv is more widely compatible with 3rd party applications than JSON but CSV is a "flat" file format that will lose some of the structure of the source data so some adaptations need to be made to the data during export and it will not be directly importable back into AyaNova again.
+Data is exported exactly as it's stored at the sever in JSON format, there are no locale conversions made.
 
 ### Time zone is in UTC