EOW!!

devdocs/specs/core-import-v7.txt

@@ -79,5 +79,13 @@ NOTES FOR DOCS
         - All users are imported with Active status set to false and must be individually edited and set to Active=true as required
         - login and passwords are not imported and need to be individually set after import as required
         - no Authorization Role is set and therefore no rights to anything.  A role needs to be set after import for each user
-- TAGS, the following objects are imported as tags
-    - TODO: List of objects
+- TAGS, the following objects are imported as tags and suffixed with a period and then short versions of the object type in the tag name
+    - Region
+    - UnitModelCategory
+    - UnitServiceType
+    - WorkorderItemType
+    - ClientGroup
+    - WorkorderCategory
+    - PartCategory
+    - DispatchZone
+    - ScheduleableUserGroup

devdocs/todo.txt

@@ -19,36 +19,27 @@ 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	
-	- v7importusers
-		- Do a First test run of importing from v7 just to ensure it's fundamentally working
-			- Then continue on to flesh out the User import second pass stuff
-			- Then test
-	- V7 import tags and other objects make sure the proper attribution and dates are set in the event log,
-		- Right now it looks like it just defaults to manager and today and created and that's it.
+	- v7importusers (on hold?)
+		- Mostly done for now with the exception of client id and headoffice id which await the client and headoffice objects respectively and their importers
+
 	- Is 35char long enough for tags?  Why is there a limit?  Can it be 50?
 	- Why are inactive users allowed to login?
 	- Seed data is seeding users inactive, sb active
-	- Event log make sure can set the date and time to prior values for importing
-	
-	- User route and controller and biz object
+
+	- USER OBJECT	
 		- Check biz rules in v7 for anything that might be missed in RAVEN biz rules
-	- v7import once have users imported then proper attribution in eventlog of creator,modifier, created,modified
-	- NEED a document with checklist to go over to ensure that a v7 object ported to RAVEN is "DONE" i.e. not missing any biz rules or properties or something
+		- NEED a document with checklist to go over to ensure that a v7 object ported to RAVEN is "DONE" i.e. not missing any biz rules or properties or something
+		- User route and controller and biz object	
+		- User routes for create update delete the core User object (no user settings in it) {also see rights in BizRoles.cs as it is not fully fleshed out yet}
+		- UserOptions object will be used for user configurable settings, not core User stuff to avoid any rights issues or confusion or bypasses
+			- Make user options now even if it only has one setting, I will need it ongoing all the time for a ton of shit. 
+	
 	- Tag groups (modify tags already coded)
 	- Localized text
 		- ** DEVISE a system to ensure no unused keys are brought forward to raven
 	- Search and search text indexing
 	- Auto visible id number assigning code
-	- User routes for create update delete the core User object (no user settings in it) {also see rights in BizRoles.cs as it is not fully fleshed out yet}
-		- UserOptions object will be used for user configurable settings, not core User stuff to avoid any rights issues or confusion or bypasses
-			- Make user options now even if it only has one setting, I will need it ongoing all the time for a ton of shit. 
-		
-Created/Changed/Modifier/ Change / Audit log 
-	- Flesh out and implement fully
-		- See cases, specs doc this has already been planned quite a bit
-	- Modify existing routes / objects to use the log
-	- Tests
-	- Do I add more fields to the objects to cover same as v7 (currently only created is there in widget and others) or do I make use of the changelog table for that shit??
+