diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt
index ab8007da..c25488a8 100644
--- a/ayanova/devdocs/todo.txt
+++ b/ayanova/devdocs/todo.txt
@@ -50,6 +50,10 @@ TODO: Tag control
 	- kind of weird if you type a search letter it sticks when you make a selection as a partial new entry
 	- drop down should search immediately or bring up something?  Or say type to search??
 	- Test it out completely, there seems to be some minor strangeness.
+	- DO: if type a letter then make a selection from list, typing should clear, that appears to be the only issue with it
+	- DO: it would be good UI if it prompted user to type to search
+	- DO: can select empty item in list, shouldn't do anything if click on that
+	- DO: Need LT key: TYPETOSEARCHPROMPT - "Start typing to search..." and NO_SEARCH_RESULTS - "No results" ( no-data-text="No results"  placeholder="Start typing to Search")
 
 
 TODO: Form customization - hidden fields support
diff --git a/ayanova/src/api/locale.js b/ayanova/src/api/locale.js
index 9c6a799b..804a4efb 100644
--- a/ayanova/src/api/locale.js
+++ b/ayanova/src/api/locale.js
@@ -71,6 +71,7 @@ export default {
     "WikiPage",
     "Duplicate",
     "RecordHistory",
+    "Search",
     "ErrorFieldLengthExceeded",
     "ErrorStartDateAfterEndDate",
     "ErrorRequiredFieldEmpty",
diff --git a/ayanova/src/components/tag-picker.vue b/ayanova/src/components/tag-picker.vue
index 91e8ce1a..a7529c7b 100644
--- a/ayanova/src/components/tag-picker.vue
+++ b/ayanova/src/components/tag-picker.vue
@@ -8,14 +8,22 @@
       v-on:input="$emit('input', $event)"
       :items="sourcetags"
       :loading="tagSearchUnderway"
+      :placeholder="lt('Search')"
       :search-input.sync="tagSearchEntry"
       hide-selected
       multiple
       chips
-      clearable
       deletable-chips
       cache-items
     >
+      <!-- <template v-slot:no-data>
+        <v-list-item>
+          <v-list-item-title>
+            Search for your favorite
+            <strong>TAG</strong>
+          </v-list-item-title>
+        </v-list-item>
+      </template> -->
       <template slot="no-data" v-if="tagSearchEntry">
         <v-container>
           <v-row row>
@@ -35,7 +43,7 @@
 </template>
 <script>
 /////////////////////////////////////////////////////////////////////////////////////////////////////////////
-/*  Xeslint-disable    */
+/*  eslint-disable    */
 ////////////////////////////////////////////////////////////////////////////////////////////////////////////
 
 export default {
@@ -49,7 +57,7 @@ export default {
 
   data() {
     return {
-      sourcetags: [""],
+      sourcetags: [],
       tagSearchEntry: null,
       tagSearchUnderway: false,
       initialized: false
@@ -84,6 +92,7 @@ export default {
     value(val) {
       //this ensures the parent form gets the onchange event
       //not actually sure why there are two here but it worked with the datetime picker so I replicated it here
+      //To answer above it appears both are necessary for proper operation
       this.$emit("input", val);
       this.$emit("change", val);
     }