No nested journals??
-
Like some other commenters, I’m a long long time user of MacJournal but I’m worried that the software may go zombie. Day One looks attractive but I notice it does not support nested journals. I’ve got hundreds of nested journals; a typical hierarchy is “Travels>2015 Travels>Johnson Pass trip”., where a collection like “2015 Travels” has 6-8 journals, and “Travels” is each year going back to 2006. If I displayed them in a flat format, the list would be long and cumbersome to work with. And apparently you can only tag entries, not journals. How do people deal with this?
-
Hi there.
On the tagging point, that’s correct as of today, tags are entry-level only.
For organizing a large number of journals, Day One recently added Journal Collections. This groups journals into named folders in the sidebar, so instead of one long list you can group related journals together and collapse the ones you’re not using. It’s live now on iPhone, iPad, Mac, and Android (web and Windows support is still rolling out), and creating a collection requires a Day One Silver or Gold plan.
One thing worth flagging for your use case: Collections are a single level, you can’t put a collection inside another collection, so it won’t replicate a multi-level structure like Travels > 2015 Travels > Johnson Pass trip exactly. A workable approach for something like your setup would be one “Travels” collection holding individual trip journals, using a naming convention (for example prefixing journal names with the year) to capture the extra level you’d lose from flattening.
More on how Collections work: https://dayoneapp.com/guides/tips-and-tutorials/journal-collections/
If true multi-level nesting is a dealbreaker for your workflow, let us know and we can log that as a feature request for you.
-
Thanks for your reply. It sounds like the Collections feature would reduce my hierarchy by one level but, in a case like mine, it would place a lot of journals in each of those Collections. Using a naming scheme might help a little, but it would be much easier, make more sense, and be more elegant to have nested journals. I would definitely request that as a new feature!
-
You’re right that Collections only removes one level of nesting, since a collection can’t hold another collection inside it. For a hierarchy as deep as yours, a naming convention only goes so far.
I’ve noted your interest in true multi-level journal nesting as a feature request. I can’t promise if or when this would be added, but your feedback is on record.
