diff --git a/docs/User Guide/!!!meta.json b/docs/User Guide/!!!meta.json index 7e724502c..b6647c8bd 100644 --- a/docs/User Guide/!!!meta.json +++ b/docs/User Guide/!!!meta.json @@ -3523,6 +3523,83 @@ "value": "bx bx-search-alt-2", "isInheritable": false, "position": 30 + }, + { + "type": "relation", + "name": "internalLink", + "value": "xYmIYSP6wE3F", + "isInheritable": false, + "position": 40 + }, + { + "type": "relation", + "name": "internalLink", + "value": "YtSN43OrfzaA", + "isInheritable": false, + "position": 50 + }, + { + "type": "relation", + "name": "internalLink", + "value": "OR8WJ7Iz9K4U", + "isInheritable": false, + "position": 60 + }, + { + "type": "relation", + "name": "internalLink", + "value": "9sRHySam5fXb", + "isInheritable": false, + "position": 70 + }, + { + "type": "relation", + "name": "internalLink", + "value": "m523cpzocqaD", + "isInheritable": false, + "position": 80 + }, + { + "type": "relation", + "name": "internalLink", + "value": "wX4HbRucYSDD", + "isInheritable": false, + "position": 90 + }, + { + "type": "relation", + "name": "internalLink", + "value": "6f9hih2hXXZk", + "isInheritable": false, + "position": 100 + }, + { + "type": "relation", + "name": "internalLink", + "value": "MKmLg5x6xkor", + "isInheritable": false, + "position": 110 + }, + { + "type": "relation", + "name": "internalLink", + "value": "qzNzp9LYQyPT", + "isInheritable": false, + "position": 120 + }, + { + "type": "relation", + "name": "internalLink", + "value": "ivYnonVFBxbQ", + "isInheritable": false, + "position": 130 + }, + { + "type": "relation", + "name": "internalLink", + "value": "oPVyFC7WL2Lp", + "isInheritable": false, + "position": 140 } ], "format": "markdown", diff --git a/docs/User Guide/User Guide/Basic Concepts and Features/Navigation/Search.md b/docs/User Guide/User Guide/Basic Concepts and Features/Navigation/Search.md index f434850b0..fe7e029f6 100644 --- a/docs/User Guide/User Guide/Basic Concepts and Features/Navigation/Search.md +++ b/docs/User Guide/User Guide/Basic Concepts and Features/Navigation/Search.md @@ -1,11 +1,59 @@ # Search
-## Note Search - Note search enables you to find notes by searching for text in the title, content, or [attributes](../../Advanced%20Usage/Attributes.md) of the notes. You also have the option to save your searches, which will create a special search note which is visible on your navigation tree and contains the search results as sub-items. -To search for notes, click on the magnifying glass icon on the toolbar or press the Ctrl + S keyboard [shortcut](../Keyboard%20Shortcuts.md). +## Accessing the search + +* From the Launch Bar, look for the dedicated search button. +* To limit the search to a note and its children, select _Search from subtree_ from the Note tree contextual menu or press Ctrl+Shift+S. + +## Interaction + +To search for notes, click on the magnifying glass icon on the toolbar or press the keyboard [shortcut](../Keyboard%20Shortcuts.md). + +1. Set the text to search for in the _Search string_ field. + 1. Apart from searching for words ad-literam, there is also the possibility to search for attributes or properties of notes. + 2. See the examples below for more information. +2. To limit the search to a note and its sub-children, set a note in _Ancestor_. + 1. This value is also pre-filled if the search is triggered from a [hoisted note](Note%20Hoisting.md) or a [workspace](Workspaces.md). + 2. To search the entire database, keep the value empty. +3. To limit the search to only a few levels of hierarchy (e.g. look in sub-children but not in sub-sub-children of a note), set the _depth_ field to one of the provided values. +4. In addition to that, the search can be configured via the _Add search options_ buttons, as described in the follow-up section. +5. Press _Search_ to trigger the search. The results are displayed below the search configuration pane. +6. The _Search & Execute actions_ button is only relevant if at least one action has been added (as described in the section below). +7. The _Save to note_ will create a new note with the search configuration. For more information, see Saved Search. + +## Search options + +Click on which search option to apply from the Add search option section. + +* For each search option selected, the search configuration will update to reveal the entry. Each search option will have its own configuration. +* To remove a search option, simply press the X button to the right of it. + +The options available are: + +1. Search script + 1. This feature allows writing a Code note that will handle the search on its own. +2. Fast search + 1. The search will not look into the content of the notes, but it will still look into note titles and attributes, relations (based on the search query). + 2. This method can speed up the search considerably for large [databases](../../Advanced%20Usage/Database.md). +3. Include archived + 1. Archived Notes will also be included in the results, whereas otherwise they would be ignored. +4. Order by + 1. Allows changing the criteria for ordering the results, for example to order by creation date or alphabetically instead of by relevancy (default). + 2. It's also possible to change the order (ascending or descending) of the results. +5. Limit + 1. Limits the results to a given maximum. + 2. This can help if the number of results would otherwise be high, at the cost of not being able to view all the results. +6. Debug + 1. This will print additional information in the server log (see Error logs), regarding how the search expression was parsed. + 2. This function is especially useful after understanding the search functionality in detail, in order to determine why a complex search query is not working as expected. +7. Action + 1. Apart from just searching, it is also possible to apply actions such as to add a label or a relation to the notes that have been matched by the search. + 2. Unlike other search configurations, here it's possible to apply the same action multiple times (i.e. in order to be able to apply multiple labels to notes). + 3. The actions given are the same as the ones in Bulk Actions, which is an alternative for operating directly with notes within the Note Tree. + 4. After defining the actions, first press _Search_ to check the matched notes and then press _Search & Execute actions_ to trigger the actions. ### Simple Note Search Examples diff --git a/src/public/app/doc_notes/en/User Guide/!!!meta.json b/src/public/app/doc_notes/en/User Guide/!!!meta.json index 5956cd216..1fdde0cea 100644 --- a/src/public/app/doc_notes/en/User Guide/!!!meta.json +++ b/src/public/app/doc_notes/en/User Guide/!!!meta.json @@ -3523,6 +3523,83 @@ "value": "bx bx-search-alt-2", "isInheritable": false, "position": 30 + }, + { + "type": "relation", + "name": "internalLink", + "value": "xYmIYSP6wE3F", + "isInheritable": false, + "position": 40 + }, + { + "type": "relation", + "name": "internalLink", + "value": "YtSN43OrfzaA", + "isInheritable": false, + "position": 50 + }, + { + "type": "relation", + "name": "internalLink", + "value": "OR8WJ7Iz9K4U", + "isInheritable": false, + "position": 60 + }, + { + "type": "relation", + "name": "internalLink", + "value": "9sRHySam5fXb", + "isInheritable": false, + "position": 70 + }, + { + "type": "relation", + "name": "internalLink", + "value": "m523cpzocqaD", + "isInheritable": false, + "position": 80 + }, + { + "type": "relation", + "name": "internalLink", + "value": "wX4HbRucYSDD", + "isInheritable": false, + "position": 90 + }, + { + "type": "relation", + "name": "internalLink", + "value": "6f9hih2hXXZk", + "isInheritable": false, + "position": 100 + }, + { + "type": "relation", + "name": "internalLink", + "value": "MKmLg5x6xkor", + "isInheritable": false, + "position": 110 + }, + { + "type": "relation", + "name": "internalLink", + "value": "qzNzp9LYQyPT", + "isInheritable": false, + "position": 120 + }, + { + "type": "relation", + "name": "internalLink", + "value": "ivYnonVFBxbQ", + "isInheritable": false, + "position": 130 + }, + { + "type": "relation", + "name": "internalLink", + "value": "oPVyFC7WL2Lp", + "isInheritable": false, + "position": 140 } ], "format": "html", diff --git a/src/public/app/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Navigation/Search.html b/src/public/app/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Navigation/Search.html index 74ff9a57d..8d02358af 100644 --- a/src/public/app/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Navigation/Search.html +++ b/src/public/app/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/Navigation/Search.html @@ -17,14 +17,121 @@ -

Note Search

Note search enables you to find notes by searching for text in the title, content, or attributes of the notes. You also have the option to save your searches, which will create a special search note which is visible on your navigation tree and contains the search results as sub-items.

+

Accessing the search

+ +

Interaction

To search for notes, click on the magnifying glass icon on the toolbar - or press the Ctrl + S keyboard shortcut.

+ or press the keyboard shortcut.

+
    +
  1. Set the text to search for in the Search string field. +
      +
    1. Apart from searching for words ad-literam, there is also the possibility + to search for attributes or properties of notes.
      2. +
    2. See the examples below for more information.
      3. +
    +
    2. +
  2. To limit the search to a note and its sub-children, set a note in Ancestor. +
      +
    1. This value is also pre-filled if the search is triggered from a hoisted note or + a workspace.
      2. +
    2. To search the entire database, keep the value empty.
      3. +
    +
    3. +
  3. To limit the search to only a few levels of hierarchy (e.g. look in sub-children + but not in sub-sub-children of a note), set the depth field to one + of the provided values.
    4. +
  4. In addition to that, the search can be configured via the Add search options buttons, + as described in the follow-up section.
    5. +
  5. Press Search to trigger the search. The results are displayed below + the search configuration pane.
    6. +
  6. The Search & Execute actions button is only relevant if at + least one action has been added (as described in the section below).
    7. +
  7. The Save to note will create a new note with the search configuration. + For more information, see Saved Search.
    8. +
+

Search options

+

Click on which search option to apply from the Add search option section.

+ +

The options available are:

+
    +
  1. Search script +
      +
    1. This feature allows writing a Code note + that will handle the search on its own.
      2. +
    +
    2. +
  2. Fast search +
      +
    1. The search will not look into the content of the notes, but it will still + look into note titles and attributes, relations (based on the search query).
      2. +
    2. This method can speed up the search considerably for large databases.
      3. +
    +
    3. +
  3. Include archived +
      +
    1. Archived Notes will + also be included in the results, whereas otherwise they would be ignored.
      2. +
    +
    4. +
  4. Order by +
      +
    1. Allows changing the criteria for ordering the results, for example to + order by creation date or alphabetically instead of by relevancy (default).
      2. +
    2. It's also possible to change the order (ascending or descending) of the + results.
      3. +
    +
    5. +
  5. Limit +
      +
    1. Limits the results to a given maximum.
      2. +
    2. This can help if the number of results would otherwise be high, at the + cost of not being able to view all the results.
      3. +
    +
    6. +
  6. Debug +
      +
    1. This will print additional information in the server log (see  + Error logs), regarding how the search expression was parsed.
      2. +
    2. This function is especially useful after understanding the search functionality + in detail, in order to determine why a complex search query is not working + as expected.
      3. +
    +
    7. +
  7. Action +
      +
    1. Apart from just searching, it is also possible to apply actions such as + to add a label or a relation to the notes that have been matched by the + search.
      2. +
    2. Unlike other search configurations, here it's possible to apply the same + action multiple times (i.e. in order to be able to apply multiple labels + to notes).
      3. +
    3. The actions given are the same as the ones in Bulk Actions, + which is an alternative for operating directly with notes within the  + Note Tree.
      4. +
    4. After defining the actions, first press Search to check the matched + notes and then press Search & Execute actions to trigger the + actions.
      5. +
    +
    8. +

Simple Note Search Examples