diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt
index 311491fa..501a7c97 100644
--- a/ayanova/devdocs/todo.txt
+++ b/ayanova/devdocs/todo.txt
@@ -51,6 +51,43 @@ CURRENT TODOs
 PICKLISTS:
 
 AUTOCOMPLETE 
+currently in v7:
+	- All picklists in v7 windows are autocomplete based on the START of the phrase typed only
+		- i.e. if you type in a Project box "pr" you will get "Project A", "Project B" but not a project called "ABC Project" as it doesn't search *in* the values
+		- This is simple and easy to intuit, maybe we don't need to get too far ahead of ourselves here.
+		- I do like the option of using tags in search and also a template that can be ordered like part display format for all this
+		
+IDEAS:
+	- SEARCH
+		- SEARCH *IN* 
+			- Search in v7 was only start of string so search IN will be very helpful to people and a step up
+			- For example in v7 if a item was templated like Unit display format with manufacturer first, then search will start with manufacturer
+				so you couldn't search for the model number first or something, you had to start exactly at the start with the manufacturer
+
+	- DISPLAY TEMPLATE
+		- Was thinking the DataListview stuff would be enough for picklist templates but actually there is very little real overlap here
+		- Maybe a kind of similar feature but focused on picklists instead?
+			- Selection templates for each object by TYPE?
+			- One central one, not unique to each user because..chaos.
+		- LINKED OBJECTS / TEMPLATES
+			- When you think about it there are few things that need to be linked for a template to display/search
+			- For example in v7 to make any display template for a Unit it needs Vendor name, Model name, Model number, Unit Serial number, Description 
+				-that's 5 items of text info from at most 3 tables, it could just always query those three tables or fixup the query on the fly to minimize table joins
+			- So you could give the user the options of several text fields pre-defined, they set the order in the template and it searches and displays based on that
+
+
+
+	- TAGS
+		- How important are tags for initial release really? 
+		- People want keyboard focused not a lot of clicking, so searching by tags is a bit of an issue:
+		- Maybe tags can be supported by a special typing sequence like enclose in special characters to search by tag like:
+		"{orange,red,yellow} Proj"
+		- OR, MAYBE have parallel selects beside (or above) each other, from left to right, top down or whatever, TAGS is first in row, then actual drop down of names
+			- if don't select a tag or clear it then only names are taken into account
+			- Most important first but they go as pairs in the same component
+
+			
+OLD RESEARCH AND NOTES
 	- This article is spot on and I need to implement it like this: http://jeremymikkola.com/posts/2019_03_19_rules_for_autocomplete.html
 	- Check article responses and comments here for tweaks: https://news.ycombinator.com/item?id=19438826
 todo: CLIENT PICKLIST DATALISTVIEW selector form