Whatâs the use case for knowing which views an entity is shown in?
generating insight by finding / tracing back the information-spaces (discussion-, work-, presentation-, schematization-, association-, sorting-spaces) an entity is associated with / included in / mentioned in.
âFiberyâs set of interactive views helps you to look at the data from multiple angles and (hopefully 
) get new insights.â So, it would be good to know about all possible associated insights, when looking at an entity + starting the process from that entity end.
As far as Iâm concerned, the views arenât the insights.
The insights are what you get after looking at data = multiple related entities and how they are connected/related.
Maybe Iâm missing something.
It is already possible to see what other entities an item is associated with (via relation views) or mentioned by (via back references).
Iâm still not sure what one can learn from knowing that an entity shows up in a given view that you donât already know from looking at the entity itself.
Since a left menu view (board/table/list/timeline) is effectively the result of a query, e.g. âShow me all features, that are not Done, with a due date in the next month, and present them as bars on a timelineâ, all the information to know whether a given entity is present in a particular view is already available in that entityâs field values.
Do you have a concrete example of a situation where you wanted to know which left menu views and entity was shown in, and what you could have achieved if it were possible?
Or are you talking about embedded views in documents/rich text fields? In which case, then I see how knowing the context could be useful - knowing an entity is present in a specific embedded view is akin to knowing that an entity is mentioned in a document/rich text field.
1 Like
To be sure, I talk of âcontent viewsâ generally. as they all generally represent âa way to capture and collaborate on knowledgeâ. that is insight beyond automated population by queries or linear calculation. So, this can be the text / document views you mention as well as whiteboards.
As to the insights:
For me, all âcontent viewsâ are actually âdocumentsâ, in the sense that they are representing / stating some surplus vis-a-vis other data levels, by way of capturing labor + thinking (additional information) not present outside of them.
Such âcontent viewsâ can represent âsurplus actsâ like associations, brainstorms, stories, relationship maps, deployment maps, rough sketches etc. and they often require time and multiple observations to produce final insight. So, real and final insight frequently occurs *when one iterates these âviewsâ (constellations of entities) over time, or revisits them given some change in the underlying data sphere (i.e., I might add more entities and then gain a new insight about the entities that were already present). To enable this, itâs necessary to return to these views. Thus, one needs to see where those connected entities are mentioned and one needs to know where to look again.
As to examples:
I could give plenty, but let me give you the schema of it.
For a newly created entity I have connected, existing entities which themselves already show up in / are associated with pre-existing âcontent viewsâ (existing brainstorming boards for a campaign; a story already developed; a concept or relationship map already cast; a pre-existant deployment map etc).
This linked information can provide valuable cues for considering values or possible contexts for any newly created entity, or ones brought into focus but still outside of those âcontent viewsâ. So, knowing context views of linked cards would help leveraging the systemâs interconnected nature.
⊠one of the possible examples.
Any way to quick create new entity with pinned filter ?
Could you expand the need?
I got an view for all clients in my company, If I quick create new people entity, it cant be assign those filter for the new one
Why not use the +New button in that view (so that the new entities are created with the filter criteria applied)?
At the moment, there is no way to create entities from the left menu with a specific set of filters in mind
Seriously, Have any clients of your guys working without mouse ?
Iâm using ipad daily with keyboard only, so workflow should be fast, hotkey C maybe suitable with tab to select pinned filter can be a quicker way for me right now
Indeed we will reserve this C key for Quick Add, but this quick add will not respect any filter on current view.