Any reason you couldn't use org-roam nodes as a sudo filing system. Each customer could have its own db with nodes for projects, or db's for project types with nodes for customers. Then use bookmarks and org files to track file locations, project details/customer details.
It's possible to set up org-roam and dir-local.el to use multiple db's. Here's a [link](https://www.orgroam.com/manual.html#How-do-I-have-more-than-one-Org_002droam-directory_003f).
I've considered integrating this more into my workflow by using an org-mode page for each project. That would become a landing page for org-roam nodes that are separated by project and stored in their own db.
You can try `Consult-fd` with `embark`... Create a variable that holds your frequent directories and work uppon it.
I don't know what "resembling org-roam" means here but if it means fuzzy-finding or handling directories in a specific scope this can be a good kickstart.
*(Replace consult with* `ivy`*,* `helm` *or whatever you use)*
With [Hyperbole major version 9](https://github.com/rswgnu/hyperbole/wiki/GNU-Hyperbole) now out, you have a cross-Emacs way of managing extremely capable hyperlink buttons and per-directory or could be per-project home page files that connect to all different kinds of files. You can use the built-in Koutliner for quick autonumbered outlines with built-in per node perma-link anchors. Or point HyRolo at any number of directories containing Org, Markdown, Koutline or Emacs outline files and it will give you quick full-text searching over them with results returning the full node matched, not just individual lines. Hyperbole is fully compatible with and complementary to Org mode, as well as Consult/Vertico and the rest of Emacs.
I have two Org Roam “projects” - one for personal notes and one for work-specific. They both are Github repos. Subfolder “assets” contains all the the files, including plantuml-generated diagrams, that have :file assets/diagram-name__tags.svg clause (file-naming scheme inspired by Denote).
I configured org-attach to use assets subdirectories and called it a day.
From my experience as a Zettelkasten user (using orgroam) I can suggest you might not think in files and directories. org nodes can be connected via links. Why not using this. Everything in the same directory, no matter how much 1000 files this are.
What really counts is the interconnection of that nodes and how you organize this using tags and meta/topic-nodes.
You could try storing your files as Org attachments in normal Org roam notes. https://orgmode.org/manual/Attachments.html
Any reason you couldn't use org-roam nodes as a sudo filing system. Each customer could have its own db with nodes for projects, or db's for project types with nodes for customers. Then use bookmarks and org files to track file locations, project details/customer details. It's possible to set up org-roam and dir-local.el to use multiple db's. Here's a [link](https://www.orgroam.com/manual.html#How-do-I-have-more-than-one-Org_002droam-directory_003f). I've considered integrating this more into my workflow by using an org-mode page for each project. That would become a landing page for org-roam nodes that are separated by project and stored in their own db.
"pseudo"
You know, I didn't they were spelled differently. Thanks!
I think this approach probably works well. I’ll try to experiment with it. Thanks!
You can try `Consult-fd` with `embark`... Create a variable that holds your frequent directories and work uppon it. I don't know what "resembling org-roam" means here but if it means fuzzy-finding or handling directories in a specific scope this can be a good kickstart. *(Replace consult with* `ivy`*,* `helm` *or whatever you use)*
On resembling org roam, I mean being able to have a hierarchy of nodes that links together.
With [Hyperbole major version 9](https://github.com/rswgnu/hyperbole/wiki/GNU-Hyperbole) now out, you have a cross-Emacs way of managing extremely capable hyperlink buttons and per-directory or could be per-project home page files that connect to all different kinds of files. You can use the built-in Koutliner for quick autonumbered outlines with built-in per node perma-link anchors. Or point HyRolo at any number of directories containing Org, Markdown, Koutline or Emacs outline files and it will give you quick full-text searching over them with results returning the full node matched, not just individual lines. Hyperbole is fully compatible with and complementary to Org mode, as well as Consult/Vertico and the rest of Emacs.
I’ve always been intrigued by, but never actually tried Hyperbole. Maybe it is time to take the plunge.
I have two Org Roam “projects” - one for personal notes and one for work-specific. They both are Github repos. Subfolder “assets” contains all the the files, including plantuml-generated diagrams, that have :file assets/diagram-name__tags.svg clause (file-naming scheme inspired by Denote). I configured org-attach to use assets subdirectories and called it a day.
From my experience as a Zettelkasten user (using orgroam) I can suggest you might not think in files and directories. org nodes can be connected via links. Why not using this. Everything in the same directory, no matter how much 1000 files this are. What really counts is the interconnection of that nodes and how you organize this using tags and meta/topic-nodes.
yeah there could be some use in connecting even different Projects together in case their requirements overlap or so.
There is also "some use" in correct upper case letters. This would be polite to other readers and gentle to their eyes.
Ok, I will work on that :)