Hey there!
JD works beautifully for one person: one tree, one owner, one mental model. I’m trying to make it work for a small team, and the tidy tree keeps running into three realities:
- Several storage platforms (Google Drive shared drives, a Nextcloud, local folders and a wiki).
- Permissions. Access is granted per shared drive/folder, not per area or category. A mirrored JD tree has to serve two masters: meaning and access.
- Personal systems. Everyone already has their own folder logic and won’t reorganise it.
Our first approach was a JD index in a wiki plus an identical tree in Drive. It stalled on point 2.
The idea now: decouple classification from location. People keep their folders. The ID becomes mandatory at the start of every filename. The wiki turns into a file plan: it defines what each ID means, and each ID page carries a search link instead of a folder link. The ID travels with the file across platforms, downloads and email attachments.
Trade-offs I see:
- No browsable structure in storage. Lookup becomes a separate step.
- Search precision: MM.YY at the beginning of a filename will make it harder to separate it. E.g. 09.23 Tax evation
- Erosion: a missing ID is invisible. An empty folder at least shows the gap.
- Granularity: JD IDs are collections, not single files. Per-file IDs add friction.
- Standard zeros: .01 still works as a prefix (“category clear, ID open”), but archive is a status, not a class.
Questions:
- Has anyone run JD with IDs in filenames instead of, or alongside, a mirrored tree in a team? How did it hold up over time?
- How do you align JD with the permission boundaries of your storage?
- Which ID format searches reliably across Drive, Nextcloud, Explorer and Finder?
- Colleagues’ personal systems: integrate, tolerate or replace?
- Is losing the browsable tree a dealbreaker, or can a good index make up for it?
Curious about your experiences, including “don’t do this”.
With best regards
Bruno