fix conflicts caused by FilterMenu changes to Tool panel struct

client/src/components/Panels/Common/ToolSearch.test.js

@@ -49,7 +49,7 @@ describe("ToolSearch", () => {
         const filterInputs = {
             "[placeholder='any name']": "name-filter",
             "[placeholder='any section']": "section-filter",
-            "[placeholder='any ontology']": "ontology-filter",
+            "[placeholder='any EDAM ontology']": "ontology-filter",
             "[placeholder='any id']": "id-filter",
             "[placeholder='any repository owner']": "owner-filter",
             "[placeholder='any help text']": "help-filter",

client/src/components/Panels/Common/ToolSearch.vue

@@ -89,7 +89,7 @@ const validFilters: ComputedRef<Record<string, ValidFilter<string>>> = computed(
     return {
         name: { placeholder: "name", type: String, handler: contains("name"), menuItem: true },
         section: {
-            placeholder: props.currentPanelView === "default" ? "section" : "ontology",
+            placeholder: "section",
             type: String,
             handler: contains("section"),
             datalist: sectionNames,

client/src/components/Panels/utilities.ts

@@ -25,13 +25,21 @@ const UNSECTIONED_SECTION = {
 };
 const VALID_SECTION_TYPES = ["edam_operations", "edam_topics"]; // other than `default`
 
+/** These are keys used to order/sort results in `ToolSearch`.
+ * The value for each is the sort order, higher number = higher rank.
+ * Must include some `Tool` properties (like name, description, id etc.)
+ * to check against query, and any other keys below are special, used for
+ * specific cases (like `combined` for name+description).
+ */
 export interface ToolSearchKeys {
     [key: string | keyof Tool]: number | undefined;
+    /** property has exact match with query */
     exact?: number;
+    /** property starts with query */
     startsWith?: number;
-    name?: number;
-    description?: number;
+    /** query contains matches `Tool.name + Tool.description` */
     combined?: number;
+    /** property matches   */
     wordMatch?: number;
 }