diff --git a/docs/User Guide/!!!meta.json b/docs/User Guide/!!!meta.json
index 3acb20f0d..0feb993c1 100644
--- a/docs/User Guide/!!!meta.json
+++ b/docs/User Guide/!!!meta.json
@@ -3815,14 +3815,6 @@
"mime": "image/jpg",
"position": 10,
"dataFileName": "Text_image.png"
- },
- {
- "attachmentId": "yGknq3nsWpef",
- "title": "bx-edit-alt.svg",
- "role": "image",
- "mime": "image/svg+xml",
- "position": 10,
- "dataFileName": "Text_bx-edit-alt.svg"
}
],
"dirFileName": "Text",
@@ -8109,6 +8101,13 @@
"value": "bx bx-hash",
"isInheritable": false,
"position": 10
+ },
+ {
+ "type": "relation",
+ "name": "internalLink",
+ "value": "0vhv7lsOLy82",
+ "isInheritable": false,
+ "position": 20
}
],
"format": "markdown",
diff --git a/docs/User Guide/User Guide/Advanced Usage/Note ID.md b/docs/User Guide/User Guide/Advanced Usage/Note ID.md
index e69de29bb..a16bf6141 100644
--- a/docs/User Guide/User Guide/Advanced Usage/Note ID.md
+++ b/docs/User Guide/User Guide/Advanced Usage/Note ID.md
@@ -0,0 +1,16 @@
+# Note ID
+Whereas some applications use file names to uniquely identify notes, Trilium uses the concept of Note ID.
+
+Generally, the Note ID is a 12-character long alphanumeric sequence (including both lower and upper case letter) that is randomly generated for each new note.
+
+## How does the import/export affect the note IDs
+
+When notes are exported, their note ID is kept in the metadata of the export. However when they are imported back in, a new note ID is generated for all the notes. This also includes other entities that are part of the import/export process such as [Attachments](../Basic%20Concepts%20and%20Features/Notes/Attachments.md).
+
+## Note collisions
+
+Since the Note ID is a fixed-width randomly generated number, due to the [pigeonhole principle](https://en.wikipedia.org/wiki/Pigeonhole_principle), there is a possibility that a newly created note will have the same ID as an existing note.
+
+Since the note ID is alphanumeric and the length is 12 we have \\(62^{12}\\) unique IDs. However since we are generating them randomly, we can use a collision calculator such as the one for [Nano ID](https://alex7kom.github.io/nano-nanoid-cc/?alphabet=0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz&size=12&speed=1000&speedUnit=hour) to determine that we'd need to create 1000 notes per hour every hour for 9 centuries in order to have at least 1% probability of a note collision.
+
+As such, Trilium does not take any explicit action against potential note collisions, similar to other software that makes uses of unique hashes such as [Git](https://stackoverflow.com/questions/10434326/hash-collision-in-git). If one would theoretically occur, what would most likely happen is that the existing note will be replaced by the new one.
\ No newline at end of file
diff --git a/docs/User Guide/User Guide/Note Types/Text_bx-edit-alt.svg b/docs/User Guide/User Guide/Note Types/Text_bx-edit-alt.svg
deleted file mode 100644
index 69dbf5040..000000000
--- a/docs/User Guide/User Guide/Note Types/Text_bx-edit-alt.svg
+++ /dev/null
@@ -1 +0,0 @@
-
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 88eb70db7..f19e4823a 100644
--- a/src/public/app/doc_notes/en/User Guide/!!!meta.json
+++ b/src/public/app/doc_notes/en/User Guide/!!!meta.json
@@ -3815,14 +3815,6 @@
"mime": "image/jpg",
"position": 10,
"dataFileName": "Text_image.png"
- },
- {
- "attachmentId": "yGknq3nsWpef",
- "title": "bx-edit-alt.svg",
- "role": "image",
- "mime": "image/svg+xml",
- "position": 10,
- "dataFileName": "Text_bx-edit-alt.svg"
}
],
"dirFileName": "Text",
@@ -8109,6 +8101,13 @@
"value": "bx bx-hash",
"isInheritable": false,
"position": 10
+ },
+ {
+ "type": "relation",
+ "name": "internalLink",
+ "value": "0vhv7lsOLy82",
+ "isInheritable": false,
+ "position": 20
}
],
"format": "html",
diff --git a/src/public/app/doc_notes/en/User Guide/User Guide/Advanced Usage/Note ID.html b/src/public/app/doc_notes/en/User Guide/User Guide/Advanced Usage/Note ID.html
index b2c3dbec9..b3a926fea 100644
--- a/src/public/app/doc_notes/en/User Guide/User Guide/Advanced Usage/Note ID.html
+++ b/src/public/app/doc_notes/en/User Guide/User Guide/Advanced Usage/Note ID.html
@@ -12,7 +12,34 @@
Note ID
-
+
+
Whereas some applications use file names to uniquely identify notes, Trilium
+ uses the concept of Note ID.
+
Generally, the Note ID is a 12-character long alphanumeric sequence (including
+ both lower and upper case letter) that is randomly generated for each new
+ note.
+
How does the import/export affect the note IDs
+
When notes are exported, their note ID is kept in the metadata of the
+ export. However when they are imported back in, a new note ID is generated
+ for all the notes. This also includes other entities that are part of the
+ import/export process such as Attachments.
+
Note collisions
+
Since the Note ID is a fixed-width randomly generated number, due to the
+ pigeonhole principle, there is a possibility that a newly created
+ note will have the same ID as an existing note.
+
Since the note ID is alphanumeric and the length is 12 we have
+ \(62^{12}\) unique IDs. However since we are generating them
+ randomly, we can use a collision calculator such as the one for Nano ID to
+ determine that we'd need to create 1000 notes per hour every hour for 9
+ centuries in order to have at least 1% probability of a note collision.
+
As such, Trilium does not take any explicit action against potential note
+ collisions, similar to other software that makes uses of unique hashes
+ such as Git.
+ If one would theoretically occur, what would most likely happen is that
+ the existing note will be replaced by the new one.