portal context enhancement

Current situation:

When reviewing notes in RemNote, the content in Portal will only be reviewed based on the context of the Rem referenced in the Portal. For example, if I reference the Portal of "Apple" and add that its color is red, when reviewing, I won't see the context of this Rem in the document, I will only see what color the apple is. While this kind of question is valid, it obviously cannot meet the needs of many situations where context information is highly related.

Feature request:

Add a feature that allows us to choose whether to display the context of the current document or the context of the concept when setting the context for reviewing in Portal.

Workflow:

I create all concepts using cmd E and add them to Portal, and they all become top-rem. This way, I can take notes like in Tana without worrying about whether the concept has already been created elsewhere or the problem of creating a concept elsewhere. This workflow is common in note-taking software such as Tana, Logseq, and Roam, and it can avoid the trouble of finding notes.

Solution and implementation of feature request:

The context of concepts is very important for understanding during review. If we cannot categorize and display the context in different situations, we will not be able to understand the relationship between concepts and study notes, and they will become relatively isolated. Adding a feature can allow us to choose whether to display the context of the current document or the context of the concept, so that we can better understand and remember these concepts.

Why use this workflow:

Note-taking software such as Tana, Logseq, and Roam all use this workflow, where all newly created notes are kept at the same level and can be cross-referenced, which can avoid the trouble of finding notes.

I can reference and create concepts at any time without worrying about whether they have already been created or the risk of duplicate names. Whenever I create a concept, I use cmd E to call up Portal, which can automatically discover Rems that have already been created.

Many people have emphasized that the concept of bidirectional note-taking should be kept at the same level, and I have also adapted to and become accustomed to this workflow. I hope to maintain consistency in RemNote. Creating and placing concepts arbitrarily in different documents will make notes messy, while using this workflow can make notes clearer and more organized. Even if we don't force everyone to use this organization method, it is necessary to adapt to the mainstream workflow to some extent.

Solution and implementation of feature request:

The context of concepts is very important for understanding during review. If we cannot categorize and display the context in different situations, we will not be able to understand the relationship between concepts and study notes, and they will become relatively isolated. Adding a feature can allow us to choose whether to display the context of the current document or the context of the concept, so that we can better understand and remember these concepts.

Why use this workflow:

Note-taking software such as Tana, Logseq, and Roam all use this workflow, where all newly created notes are kept at the same level and can be cross-referenced, which can avoid the trouble of finding notes.

I can reference and create concepts at any time without worrying about whether they have already been created or the risk of duplicate names. Whenever I create a concept, I use cmd E to call up Portal, which can automatically discover Rems that have already been created.

Many people have emphasized that the concept of bidirectional note-taking should be kept at the same level, and I have also adapted to and become accustomed to this workflow. I hope to maintain consistency in RemNote. Creating and placing concepts arbitrarily in different documents will make notes messy, while using this workflow can make notes clearer and more organized. Even if we don't force everyone to use this organization method, it is necessary to adapt to the mainstream workflow to some extent.