devdocs/todo.txt

@@ -80,16 +80,10 @@ TODO CLIENT STUFF
 
 TODO SERVER STUFF
 
-	- TAGS: REally need to have a think about how tags are used in the UI, probably need a autofill route that has a source of used or common tags to drive it
-		- so user can type first fiew characters adn select
-		- So consistency is maintained and not sloppy multiple spellings
-		- Maybe a db stored procedure and trigger or biz code that feeds a consolidated tag table of all entered tags in the system?
-			- Maybe a reference count for each tag to drive a tag cloud feature and also a order by commonality feature when offering and also to know when to remove from 
-			the tag repository when no one is using that tag anymore in any records
-
-		- TAG ROUTE: LIST route to fetch tags in Alphabetical order by name based on starts with (or maybe contains) used for quickly autofilling a list at UI level
+	
 		- TAG ROUTE: CLOUD route to fetch tags in order of refcount decreasing
 		- TAG repo tests: ensure updates delete and add properly, ensure new adds properly, ensure lists work properly
+		- TAG Ref count test:
 
 	- Boot server and seed with debug log turned on, see what is being tracked by EF that doesn't need to, seems some of that shit is being tracked.
 	- Docs: pagingOptions, sort and filter need to be documented for API