Open abers opened 2 years ago
SkepticMystic
commented
2 years ago Hey @abers! Thanks for the FR. Interesting idea.
I've been working on a generalisation of this type of hierarchy for q while now. I can't seem to cover all the cases, but maybe it works for you. It's quite janky atm, but check out Naming System under Settings > Alternative Hierarchies
abers
commented
2 years ago I was able to get the basics of this working, but not for the specific hierarchy I was looking to represent, which needs regex for the system delimiter and a way to delimitate 'sibling groups' that have the same parent. I've opened a separate issue for the latter, with a suggestion for how it could be handled within the regular hierarchies. If implemented, it could be extended to the naming system by adding a 'naming system group delimiter' with support for regex.
SkepticMystic
commented
7 months ago Please can you summarise the rules of the system. Specifically, how to move in each direction from one note to another. I don't think the super-broad Naming Notes system I was working on is the best approach. I'll consider adding a dedicated Edge Builder for Folgezettel
charleshan
commented
14 hours ago The basic rule is to use alternating identifier (number, alphabet). Some systems also use capital letters, slashes, and dots we we can ignore them to start off. The same logic applies.
For example, with a note with ID 3b2, starting from the last character, this tells you that:
It would be really cool to be able to generate these dynamically and be able to hover/click on them to get more information.
Is your feature request related to a problem? Please describe. Add support for a folgezettel hierarchy.
Describe the solution you'd like Folgezettel (see also: Luhmann's Zettelkasten index) codes are commonly used in zettelkasten workflows. This is an alphanumerical system for specifying note hierarchy. For example, 23/1a12 has the parent 23/1a, child 23/1a12a, previous 23/1a11, next 23/1a13. The number preceding the '/' specifies a core subject area.
At present, relationships must be added in terms of up, down, prev, next, and same. It'd be great if it was possible to instead add a metadata field, such as 'folge:', through which this type of hierarchy is derived.