Hey Oshyan, thanks for weighing in on this one, appreciate the time looking at it and the feedback, this remains one of my biggest needs and not really solved fully in Fibery yet!
This is a great dilemma - should all “Talking points” be entities, or just some? One of my big needs is to track mgmt meetings in a tool. I have looked at about every solution out there, none really do the trick. Key on my wish list:
- Affected Entities trace back to the meeting where decisions are made about them. This seems mostly logical to accomplish in the comments stream, ie “we decided in meeting X we will do this…”
- Newly created entities within a meeting can be seen to have originated there. My team often has work get stale, and when going over it and trying to review, we at times lose track of why something got in the system
- Some good ideas come out of meetings, at times ad hoc and related to existing procedures, guidelines, etc and it is great to record that
I had actually eagerly anticipated Highlights as a way to just turn those Talking Points into entities that required that. But Highlights remain limited in the context they show, that’s a main reason I made this request:
I have found that when trying to use Highlights for this need, we can’t really get at a glance enough context when reading the Highlight. We have also used Roam for meetings incidentally, and their implementation of the references was much more thorough so I’m hoping Fibery gets to that soon.
Without the benefit of Highlights, of late I’ve wound up having every Agenda Item in the meeting its own entity. In turn it needs to relate to something in the System, such as a task, project, business area, etc. This also leads to a ton of Relations and one of the reasons you’ve seen me talking about Polymorphic and more arbitrary relating capability.
And to close, not to bring it up again, but Notion actually handles my need better right now, for a few reasons:
- I can write into the related Linked db where I keep the Agenda Times in the meeting
- I can use a “simple text” field - while not ideal - to write in quick notes, and can make primitive bullets hitting “shift” + “enter.” Also @mentions work in those types of fields in Notion, they don’t in Fibery.
And sorry this is so long, but one more thing that occurs to me is that with your request, I’m not sure how you’d get the relation back to the Meeting entity unless that embed in Rich Text picked it up. This is where the Notion example shines because you at least get the relation via the linked db.
Hope that all makes sense and is useful, too!