diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt
index 7ddf893e..9f6142ba 100644
--- a/ayanova/devdocs/todo.txt
+++ b/ayanova/devdocs/todo.txt
@@ -53,10 +53,11 @@ SHELL / NAV / MENUS / LAYOUT
 		- Relative tokens are stored in the filter as tokens, user never needs to set dates for them as they are all relative anyway
 		- 
 		- If filter selected then it builds the json fragment to send based on the filter currently selected and sends that with the datalist request
-			- If relative dates are in it then they are rehydrated into utc iso-8601 format dates 
+			- If relative dates are in it then they are rehydrated into utc iso-8601 dates as a *BETWEEN* type filter
 		- Server validates filter and sort json fragment during query build, if not ok then either attempts to workaround or balks with error (probably balks is the better choice) 
 
 	- TOOD: 	
+		- SERVER: is leaking implementation details in field enum type ("enumType": "AyaNova.Biz.UserType",), modify datalist definitions to trim enum type to rightmost
 		- SERVER: Keep data filter routes and stuff at server pretty much as is but keep in mind they are only for the client's consumption
 		- SERVER: needs relative date tokens back again but simply for validation to ensure they are correct tokens when storing a datafilter
 		- SERVER: DataList fetcher ListOptions no longer uses datafilterid anymore nor does any part of datalist code, instead they accept a single sort and filter json fragment