devdocs/specs/unit-service-type.txt

@@ -1,3 +1,3 @@
-Deprecated for tag?
-Didn't actually check but it seems like a likely candidate.
+Deprecated for tag
+Workorder will still have a redundant TAGS area in the unit service section so that section can be specfically tagged with unit service type tags or whatever the user wishes
 See case 3373

devdocs/specs/workorder-item-type.txt

@@ -1,3 +1,7 @@
-Deprecated to tags?
+Deprecated to tags
 See case 3373
-Need to confirm it will work, types don't appear to do anything and are documented as for filtering and reporting and sorting so that's a tag
+It will work, types don't appear to do anything and are documented as for filtering and reporting and sorting so that's a tag
+
+Just need to remember that the Workorder ITEM itself needs a TAGS area so that it can be separately tagged as with other areas of workorder like unit service type etc.
+
+

devdocs/todo.txt

@@ -19,7 +19,17 @@ 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	
-	- V7Import Dispatch zones (as tags), ScheduleableuserGroup (as tags) so can be used with User import and other shit
+	- V7Import things that are replaced by TAGS FIRST, then move on the User import and other stuff again:	
+		- Unit model category
+		- Unit service type
+		- Workorder Item Type
+		- Client group 
+		- Workorder category
+		- REGIONS
+		- PartCategory
+		- Dispatch zones
+		- ScheduleableUserGroups
+
 	- Event log make sure can set the date and time to prior values for importing
 	- v7importusers
 	- User route and controller and biz object