I'm 24 and my life is still changing a lot... what do I do about 'transient' areas?

Hi everyone!

I’m certainly new to the JD system. I’m currently working on brainstorming my areas and categories. I’ve reorganized my files before, but I’m hoping this will be the last time! Consequently, I’m trying to make sure my system will adapt as my life changes.

I’m in grad school working towards my PhD. Obviously, this is a huge area of my life right now. However, in a few years hopefully, this area will mainly be dormant.

I feel that if I create a new JD system for this area, it’ll get too out of hand. I also don’t think it would be right for it to still occupy its own area when I’m 40 and have more relevant areas.

So my question is: does anyone have experience with transient areas? Is there a way to implement an archive system without renaming every item in that area?

Thank you in advance for the insight!!

1 Like

I’ve had a few of these come and go.

30-39 Coruscade was the company that I contracted through. That existed in my personal life. Now merged in to the Johnny.Decimal business system as we use that same entity.

40-49 Strange Attractor was a podcast that me & Lucy did years ago. Now in an archive folder, number available for re-use.

50-59 Wedding celebrant as I used to be one. No longer. Archived.

This is why I recommend really broad areas. You should never come anywhere close to running out of areas, and then if they come and go over the course of a decade it’s no bother.

So, if you archive an area and reuse that number again, do you still leave all those IDs in the index? I’m concerned about having multiple IDs with the same number.

1 Like

No, they’re now folders on disk that I don’t ever imagine looking at again. I’m not tracking them in my JDex.

Edit: they’re not even on this disk, i.e. this laptop. They’re sitting on my file server, so they don’t clutter local search results.

I think this is a common problem with using JD to track projects. At my work, I have projects that follow the same pattern - they require certain kinds of documents and files. I sort the documents by the kind, not by the project. Projects are subdirectories to the AC.ID that are organized by the kind of items I store there.

Using the college example, you may have a category 11 Classes but inside that category, instead of organizing ID by class, organize them by the kind of information you will store there: 11.11 Class Notes, 11.12 Assignments, etc. Inside each AC.ID, you will have subdirectories by class.

The advantage of this approach is that you can use this structure for any class and you can archive subdirectories for completed classes without disruption to your numbering system. The con is that your notes will be fragmented. E.g. Class notes on a certain subject may be related to assignments on that subject, so there it makes sense to keep them together.

As everywhere in life, there are no solutions - there are trade-offs.

Just to elaborate on the opposite pattern which might be more helpful in the case of college classes, at least it would work a lot better for my brain: you might want to have an ID ‘Classes’ (e.g. 11.21) and then in there, folders named by date and class (maybe institution and level? e.g. 2025 UniOfX ENG_G450 English Literature) and then in those, for sure maintain a strict standard of folders similar to what @agru suggests, i.e. class notes, assignments, practicums, etc. This pattern has been discussed elsewhere on the forum.

Welcome here @tushpat!

Beyond the good advice to not be afraid of down- or upgrading a folder as its relative importance changes, I would emphasise that this:

implies that IDs can cover a lot of ground, too. The point of JD for me is that you can find things in a few steps, because you have an exhaustive and non-ambiguous index to consult at the start. The point is not to overclassify things. If you know how to find your way around your files once you’ve narrowed things down, then you don’t need to do more work arranging things. That’s a waste of time.

I don’t think I would make each class an ID (as I said above). Or even my PhD thesis. I think my ID would contain a list of places to put and retrieve stuff relative to each class or project I was doing. So where is my reference manager, and what are the tags/folders I use for references relating to my thesis.

I think my ID index entry would primarily contain the checklists and procedures I use for staying productive with my thesis work. I would think of this as the place to go to get refocused. What is this project I’m working on, what is my goal, how have I decided I’m going to work on this, what are my study habits, what’s my schedule, where are my tools and resources … Ok, now go do it!

Approaching it this way, the ID would be even broader, like ‘Studying and Researching’ and would therefore outlast my graduate studies. Something like a thesis project is fairly big and messy and constantly changing – lots of drafts and notes – and would live in its own ‘repository’, being indexed in the JDex but not actually stored there. I think in my approach, even my whole record of classes I took would just be a text file in the ID ‘education’. I know many people would give each course an ID, whereas I look for much broader things that feel like they’ll last a long time.

So, maybe giving it its own area or even system actually frees you up to tailor the index you’re creating to fit this currently significant part of your life … as @johnnydecimal has explained, don’t worry about archiving it later being a big step. I know this is sort of contradictory advice to what I said above, but what I said above entails thinking long and hard about how to make categories and areas become as timeless as possible, and if you don’t have time for that now, just give yourself lots of room and burn through those IDs for now[1], and consolidate them later, because:

It won’t be. But the next reorganisation won’t be a big deal because you’ll be going from one organised state to another.


  1. remember, too, that areas and systems can be only partially filled. ↩︎

1 Like

For myself, I created an Area called “50-59 Projects”. I expect this area to have time-limited endeavors while they are active, and will move them into the appropriate location in the rest of the system when their time is up.

Linking The Academic problem:

Having a separate system for my academic stuff has been a huge help, both in that everything is well organized and contained, and that it’ll be easy to archive upon completion. I personally can’t imagine trying to contain it all within an ID, as that ID would basically become an index to a separate system on its own.

Per multiple systems, I’ve given my SX.C.ID system and education areas the system ID of E01, so with a few bulk-renames it’ll all become E01.AC.ID or E01.SX.C.ID, and I’ll move the old index files along with the content. The organization and structure will remain, but it frees up the IDs to be used in other contexts.

Yeah, I get that. I think it might depend on how ‘transient’ this domain is in one’s perspective on their life, among a few other things.