diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt
index c703a210..6dc5b45e 100644
--- a/ayanova/devdocs/todo.txt
+++ b/ayanova/devdocs/todo.txt
@@ -6,14 +6,15 @@ PRIORITY - ALWAYS Lowest level stuff first, i.e. TODO at server, api route chang
 
 
 todo: JOBS UI
-		For now, just show a report of jobs log
-		v.next maybe can kill a job or submit ops ones
-		trigger test job maybe? (not widget, just more generic tester)
+		For now, just show a report of jobs log	
+		option to trigger test job maybe? (not widget, just more generic tester that sits under the JobOperations route)
+
+todo: OPS view server logs
+
+todo: OPS view metrics
+	- view metrics
+	- this could be made to look really cool, take a brief amount of time to see what can be done re graphs etc and make v.next cases if too involved for now
 
-todo: add long polling notification route CLIENT UI
-	https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3507
-	- Need way to acknowledge receipt of long poll info from client to server so that it can be removed or something?
-	- maybe successfull sending clears it regardless of client?
 
 todo: translation page with translation settings
 	- Translation feedback link in translation page https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3722
@@ -21,12 +22,24 @@ todo: translation page with translation settings
 	https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1439
 
 todo: ability to mass tag items from list CLIENT UI
+	- some kind of generic or copyable light interface for any mass / bulk job?
+		this will get re-used for other stuff undoubtedly down the road
 	- also a good way to do an initial implementation of a mass ops UI code
 	ability to mass rename a tag to something else in all objects 
 	this is bizadmin level page dedicated to this kind of operation, list of objects and mass changes to be made
 		maybe this is a mass changes feature in general??
 		Or maybe just targetted to tags and can copy and re-use for something else if needed later
 
+todo: notification
+	it's time, this is a big deal and it's tied to infrastructure shit so qualifies as an early thing to be done
+	add CLIENT long polling notification route check
+	add dummy route for above then flesh out
+	- Notifications for OPS jobs?  (Notify me when done kind of thing?)
+
+	This is a bit outdated, lots of decisions already made and worked out in cases / spec docs
+		https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3507
+		- Need way to acknowledge receipt of long poll info from client to server so that it can be removed or something?
+		- maybe successfull sending clears it regardless of client?
 
 todo: WIKI insert image should have extra linefeed before and after because it fails to show the image at all if it follows something like <br> even though it appears to be on the next line
 	- tl/dr: ensure blank before and after for any url