This note is actually opened when the Note Map feature that is accessed from the Launch Bar.
It is possible to create any child notes in it without any additional meaning. For example, it can be used to store a list of note maps which can be linked to from other notes or bookmarked.
Whenever a search is executed from the full Search, the query will be stored here, grouped by month. Only the search parameters are stored and not the results themselves.
This section can be accessed without going to the hidden tree by simply going to the Global menu and selecting Advanced → Open Search History.
Notes can be added as children of this tree, but it's generally not recommended to do so to not interfere with the normal history process.
This section can be used by scripts to create their own notes that should not be directly visible to the user. The note can be identified by scripts by its unique ID: _userHidden
This tree lists all of the notes that are shared publicly. It can be useful to track down which notes are shared regardless of their position in the note tree.
This section can be accessed without going to the hidden tree simply by going to the Global menu and selecting Show Shared Notes Subtree.
This is where the note structure for the User Guide is actually stored. Only the metadata is stored, as the help itself is present as actual files in the application directory.
As an example, the archived label can be set to be inheritable,
allowing you to hide a whole subtree of notes from searches and other dialogs
by applying this label at the top level.
+
Standard inheritance forces all the notes that are children (and sub-children)
+ of a note to have that particular label or relation. If there is a need
+ to have some notes not inherit one of the labels, then copying inheritance or template inheritance needs
+ to be used instead.
Copying Inheritance
Copying inheritance differs from standard inheritance by using a child: prefix
in the attribute name. This prefix causes new child notes to automatically
receive specific attributes from the parent note. These attributes are
independent of the parent and will persist even if the note is moved elsewhere.
-
How to Use
-
-
Syntax:#child:attributeName
-
-
Chained Inheritance: You can chain this inheritance, such
- as #child:child:attributeName, where each child down the hierarchy
- receives the appropriate attribute.
-
-
Example
If a parent note has the label #child:exampleAttribute, all
- newly created child notes will inherit the #exampleAttribute label.
+ newly created child notes (one level deep) will inherit the #exampleAttribute label.
This can be useful for setting default properties for notes in a specific
section.
+
Similarly, for relations use ~child:myRelation.
+
Due to the way it's designed, copying inheritance cannot be used to cascade
+ infinitely within a hierarchy. For that use case, consider using either
+ standard inheritance or templates.
+
Chained inheritance
+
It is possible to define labels across multiple levels of depth. For example, #child:child:child:foo applied
+ to a root note would create:
+
+
#child:child:foo on the first-level children.
+
#child:foo on the second-level children.
+
#foo on the third-level children.
+
+
Similarly, use ~child:child:child:foo if dealing with relations.
+
Do note that same as simple copying inheritance, the changes will not
+ apply retroactively to existing notes in the hierarchy, it will only apply
+ to the newly created notes.
Template Inheritance
-
Attributes can also be inherited from templates.
+
Attributes can also be inherited from Templates.
When a new note is created using a template, it inherits the attributes
defined in that template. This is particularly useful for maintaining consistency
across notes that follow a similar structure or function.
A label is an attribute of a note which
- has a name and optionally a value.
+ has a name and optionally a value.
Common use cases
-
Metadata: Assign labels with optional values for categorization,
- such as #year=1999, #genre="sci-fi", or #author="Neal Stephenson".
+
Metadata for personal use: Assign labels with optional
+ values for categorization, such as #year=1999, #genre="sci-fi",
+ or #author="Neal Stephenson". This can be combined with
+ Promoted Attributes to make their display more user-friendly.
Configuration: Labels can configure advanced features
or settings (see reference below).
Scripts and Plugins: Used to tag notes with special metadata,
diff --git a/src/public/app/doc_notes/en/User Guide/User Guide/Advanced Usage/Attributes/Relations.html b/src/public/app/doc_notes/en/User Guide/User Guide/Advanced Usage/Attributes/Relations.html
index 5d3e541ea..bfb1d8d1c 100644
--- a/src/public/app/doc_notes/en/User Guide/User Guide/Advanced Usage/Attributes/Relations.html
+++ b/src/public/app/doc_notes/en/User Guide/User Guide/Advanced Usage/Attributes/Relations.html
@@ -17,8 +17,15 @@
of having a text value it refers to another note.
Common use cases
-
Metadata Relationships: For example, linking a book note
- to an author note.
+
Metadata Relationships for personal use: For example,
+ linking a book note to an author note.
+ This can be combined with Promoted Attributes to
+ make their display more user-friendly.
+
Configuration: For configuring some notes such as
+ Render Note, or configuring Sharing or
+ Templates (see the list below).
Scripting: Attaching scripts to events or conditions
related to the note.
For easy extensibility, a lot of features in Trilium make use of actual
+ notes to store information as opposed to having them stored in a separate
+ location in the database. This allows some functions such as Attributes, Relations or
+ even Search and
+ Links to be able to operate on them.
+
As the name suggests, these notes are hidden to the user by default to
+ prevent cluttering the note tree and to prevent them from being accidentally
+ deleted.
+
The hidden notes are stored in the user's Database just like normal notes, but they
+ have a unique Note ID which
+ allows them to be distinguished from the normal ones.
+
Accessing the hidden note tree
+
From the Global menu,
+ select Advanced → Show Hidden Subtree.
+
Contents of the hidden note tree
+
Here is a brief summary of all the notes within the hidden tree:
This note is actually opened when the Note Map feature
+ that is accessed from the Launch Bar.
+
It is possible to create any child notes in it without any additional
+ meaning. For example, it can be used to store a list of note maps which
+ can be linked to from other notes or bookmarked.
When SQL queries or commands are executed in the SQL Console,
+ they are stored here, grouped by month. Only the query is stored and not
+ the results.
+
This section can be accessed without going to the hidden tree by simply
+ going to the Global menu and
+ selecting Advanced → Open SQL Console History.
+
Notes can be added as children of this tree, but it's generally not recommended
+ to do so to not interfere with the normal history process.
Whenever a search is executed from the full Search,
+ the query will be stored here, grouped by month. Only the search parameters
+ are stored and not the results themselves.
+
This section can be accessed without going to the hidden tree by simply
+ going to the Global menu and
+ selecting Advanced → Open Search History.
+
Notes can be added as children of this tree, but it's generally not recommended
+ to do so to not interfere with the normal history process.
This section can be used by scripts to create
+ their own notes that should not be directly visible to the user. The note
+ can be identified by scripts by its unique ID: _userHidden
+
This tree lists all of the notes that are shared publicly.
+ It can be useful to track down which notes are shared regardless of their
+ position in the note tree.
+
This section can be accessed without going to the hidden tree simply by
+ going to the Global menu and
+ selecting Show Shared Notes Subtree.
This is where the note structure for the User Guide is actually stored.
+ Only the metadata is stored, as the help itself is present as actual files
+ in the application directory.
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/src/public/app/doc_notes/en/User Guide/User Guide/Advanced Usage/Hidden Notes_image.png b/src/public/app/doc_notes/en/User Guide/User Guide/Advanced Usage/Hidden Notes_image.png
new file mode 100644
index 000000000..60c4c4802
Binary files /dev/null and b/src/public/app/doc_notes/en/User Guide/User Guide/Advanced Usage/Hidden Notes_image.png differ
diff --git a/src/public/app/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/UI Elements/Note Tree.html b/src/public/app/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/UI Elements/Note Tree.html
index a91c810ea..530a8aaca 100644
--- a/src/public/app/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/UI Elements/Note Tree.html
+++ b/src/public/app/doc_notes/en/User Guide/User Guide/Basic Concepts and Features/UI Elements/Note Tree.html
@@ -55,7 +55,7 @@
In the right-click menu, operations such as Cut, Copy, Move to, Clone
to or Delete will apply to all the selected notes. It is also possible
- to apply Bulk actions to
+ to apply Bulk actions to
them. The rest of the options will not be available and will appear disabled
in the menu.
+