| I have been feeling an itch to build a personal "everything" database for some time now. Use cases: - Knowledge Management / Journal / Zettelkasten - Link Archive / pinboard.in replacement - Cycling Route Archive / Planner - ... The crucial thing is: I don't want it to be text/file based like Obsidian and similar. I want a machine-readable database. I'm thinking about an entity-key-value representation, with 'notes/content' being one attribute, 'cycling.route/gpx' another one, containing the GPX of the route, etc. This would allow tooling to be a first-class citizen: Entities with 'web.bookmark/url' properties could archive the content into 'web.bookmark/snapshot' in the background, GPX routes could be matched with a 'ride' entity, etc. A generic editor would allow editing of any kind of attribute, while use-case specific editors would allow edits to (for example) the GPX route. Anything out there? |
The problem is I feel the tabular DB format is "too raw" for some usecases. I prefer Outliner/DB combos (like the upcoming logseq DB version) or maybe one of the local Notion alternatives.
[1] https://github.com/gristlabs/grist-core [2] https://github.com/gristlabs/grist-desktop [3] https://www.getgrist.com/product/#:~:text=As%20extendible%20...