- 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...
I haven't found anything that really does all of this, but it seems like Cryptpad[0] and Peergos[1] are viable platforms upon which something like this could be built.
Except for the lack of encryption, Atomic Data[2] also seems like a really cool platform to build this on.
Right now I have a system I call FRAxInUS which uses a document database back end and contains a commenting system, tag system, personal webcrawler, and has some visualization tools. It started out reusing a lot of code from my YOShInOn RSS reader and one of these days I want to make YOShInOn a FRAxInUS application.
In one instance of this I have a collection of 250,000 or so images or so which I am organizing. In the other one I loaded about 400 notes from somebody's Evernote and I am tagging them. I'm planning to introduce "projects" to the system so I could go to a URL like
/projects/b12f2df5-0eda-436a-9776-04221488f744
and this goes to a "tenant" in the system which might have its own db or might be in a shared db with records marked with the project id and also activates a set of Flask blueprints and sets template settings to personalize it. It starts out with ingesting images, HTML, and plain text but the long term plan is to implement structured records, for instance, to have a semiautomated process to suck out references to people in the notes and make a database of people.
Look up my email in profile and I'd be glad to talk about it.
Although it's not really ready to show people yet. But would be interested to hear some more about people's use-cases for this kind of thingy. Would also be willing to jump on a call or smthn sometime and share my experience if u email me.
One thing I've done is a new line staring with a colon represents metadata, like
:tags customer,product2
And I've built tools around tag searching. Same thing goes with dates and other misc metadata I may want to use.It may not be what you're looking for, but I've found it to be a good middle ground for myself.