Do make a feature request… The team is already considering relations as objects - which expand the usage of relations. This should mobilise relation a lot - but not sure how the team plan to do this.
I really supports more functions of relations, like how I layout a bit of my potential usage here.
I will be looking forward to building up FR for dynamic relations, relations context, and sub-relations, based on multi-dimensional relations FR. It would be great if multi-dimensional relations can be expanded to support relations that exists only depending on certain other relations.
E.g. Intensity 5 (number relation) of happiness (emotion relation but also an emotion object) ← number relies on the existence of happiness (but not permanently link to happiness) because of person A (human object)'s
words (the main quote object or referencable block linking to related objects) at time of date for event. (Journal object)
↑ This would be one basic input unit of my journaling point . I would hope to be able to query all these individual points as a whole (multi-dimensional unit) or sometimes just part of it, and observe patterns across different period.
P.S. I still haven’t make a proper FR since my first impression and still part of it has already makes it to development . While I have actual use case, I still haven’t figure out how it could be implemented properly for ease of input, especially how complex dynamics can get and without interfering operations of objects.
Thanks for clarification. Ideally having this idea of “multi-dimensional” relations is a great way to start! Having the option of connecting databases and pulling information from certain relations of them like Notion does with “roll-up” and “relations” is a nice bonus!
A lot of the entries I’m migrating needs to be done manually, so the ability to unlock and edit the creation date is a must. A current workaround is to create a new date relation so I can still sort by date, but this means I’ll have to input the date manually for the rest of my journaling time here in the app.
a couple things I’ve seen that were bothersome/dissuasive to some people:
The ‘too-spartan-to-be-flexible’
The ‘but what about the rest of the day?’
The ‘But I don’t have the spoons to write down my feels right now’
each of these detractors is related, and counter to each other almost…
If you, first thing in the morning… ask someone
‘Quantify your day:’
they may feel denied the ability to express the bullshit of the rest of the day… leading to anxiety about what to put down
If you ask someone to provide multiple datapoints thru-out the day, it’s overwhelming
If you use simple icons, there’s a lot of context and nuance lost.
if you use rich text, it’s a challenge to derive metrics or infer statistics from.
ULTIMATELY, IMO, the goal is “increase one’s happiness with one’s life.”
so… how do we do that?
A solution I came up with, (not saying it’s perfect, but it does help alleviate some of the concerns)
first thing in the morning, ask:
‘How was yesterday?’
It allows you to quantify the day in simpler metrics
It is the voice of remembering-self speaking to future-remembering-self… IOW: the immediate bias/incongruence between experiencing-self and remembering-self is sidestepped,
…But you’re still adjacent-the-relevant-experience enough to objectively/accurately assess the qualities of the day.
. I would hope to be able to query all these individual points as a whole (multi-dimensional unit) or sometimes just part of it, and observe patterns across different period.
and still part of it has already makes it to development 
. While I have actual use case, I still haven’t figure out how it could be implemented properly for ease of input, especially how complex dynamics can get and without interfering operations of objects.