-
Notifications
You must be signed in to change notification settings - Fork 0
UIDs
In the context of plain text wikis and Zettelkästen, an explicit UID (unique identifier) is a part of the filename of a note unique to that note, used to create durable links to the note. UIDs are supposed never to change, like primary keys for records in a database.
UIDs usually conform to a strict pattern, most often a timestamp prefix in the form YYYYMMddHHmm
. The wikilink [[202007011200]]
would point to 202007011200 Another Note.txt
, and would remain unbroken even if the note is renamed 202007011200 Renamed Note.txt
. This robustness is the chief benefit of using explicit UIDs.
Drawbacks of explicit UIDs include the interruption of the flow of text with long, usually non-semantic strings of characters, and the fuss of fetching the UIDs of notes in order to link to them (ameliorated by wikilink-uid
).
The Archive recognises UIDs. nvUltra does not.
Another approach is to use the basenames of notes (filenames without extensions) to identify them, so that [[Another Note]]
would link to Another Note.txt
. This has the virtue of preserving the flow of text:
The claim is supported by the [[Regensburg Ordinance]] of 1459, which established a masonic brotherhood ([[Bruderschaft]]) pledged to uphold the articles of the ordinance.
Links under this approach are more fragile, as they will need to be updated whenever a note is renamed (which rename
will do).
As noted in their descriptions, some macros in this repository are intended for contexts in which UIDs are used, others where basenames are used.