devdocs/todo.txt

@@ -3,7 +3,6 @@
 
 Import / export features
 
-Export - JSON only, no csv, remove the csv export, export anything exactly as it is now probably no change required
 Import / update
 	limited specific subset of objects from admin import page (rename that to "import / update"?)
 	JSON AND CSV both supported
@@ -25,6 +24,17 @@ 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)
 
 	Front end work to support json or csv files
+		if user opens CSV:
+			read in csv if not column headers should barf
+			convert csv to JSON, the proceed as if opened json:
+		
+		Scan json fields in each item and ensure that they have minimum required field property names "Name" or whatever
+		if any missing reject
+		don't care if extra that won't be used, that's ok
+		maybe rename viz from export to whatever the expected format is for importing a linked object by name (or keep viz just to be easier?)
+		Once scan completed then issue dire warning about how it will not only import but also modify objects see below with help link
+		once double approved then it goes to work and uploads to the server for import where the server does it's now back end magic
+
 	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
 		probably a single page for each object, i.e. admin-import-customer.md, admin-import-part.md etc
@@ -35,6 +45,8 @@ TODO:
 	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
+
+
 	Once it's working then can see about expanding to other objects
 	If add translation keys should try to do it as a schema update now