# References to Views as a way to emulate Embedded Db's in Notion **URL:** \ **Category:** Ideas & Features\ **Created:** [December 16, 2020, 7:35pm UTC](https://community.fibery.io/t/references-to-views-as-a-way-to-emulate-embedded-dbs-in-notion/1247 "2020-12-16T19:35:40Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [December 19, 2020, 4:50am UTC](https://community.fibery.io/t/references-to-views-as-a-way-to-emulate-embedded-dbs-in-notion/1247/6 "2020-12-19T04:50:02Z")
> [@B\_Sp](#): > > And I will go so far as to say that in fact by NOT being able to relate to everything yet in Fibery, I feel there is a limitation that other tools that do allow this have gotten past. In reality, relating to “everything” is also a huge part of Roam, and not just Notion. Without the ability to reference everything, we are not fully able to work in the full networked thinking approach which I am a big advocate of. I continue to hope that Fibery will become the go-to tool for this approach as far as work management, as those two tools are flawed in this role. But we need everything in Fibery linkable two-ways. So if I want to point my team to an App, or Type, in a document about how to use Fibery, I can’t link to either. That’s a drawback. This is, in fact, not actually correct, and speaks to the concern I had with your original proposal. For example, you cannot link to the “network view” in Roam. Why? Because it’s… a view. Not an object. Not a “thing”. It is a view _of_ data, with controls for adjusting that view of data, but not necessarily something you treat _as_ data. Same seems to me to be true in Fibery. View’s are… views. They are not holders of unique content or things with entity-type properties of their own. Not to say they absolutely shouldn’t be, just that this is how they have been treated and described so far, I believe. In Notion you also can’t link to a specific view, as far as I know. You can link to a _database_, but not a specific view of that DB, unless it’s embedded in a page, in which case you’re linking the page not the “view”, really. At least this is all as I understand it. And in the case of linking to DBs there are no backlinks either, AFAIK. Anyway, all of that being said, I can see your argument for this, but… I’m still not necessarily confident it’s the right approach. Even though my (next) proposal itself seems like a bit of a workaround. Which is that unlike Views - where I am less confident that they should have e.g. backlinks, etc. - with **documents** I definitely think we should have a way to view backlinks, and _maybe_ more. And so again going back to the [Embed Views in Rich Text](https://community.fibery.io/t/embed-views-in-rich-text/936) feature, you would do what you’re suggesting exactly in the way that Notion currently does: by embedding one of more views in a _Document_ (in Fibery’s case) and using the backlinks function of the doc… I get though that you seem to be wanting Views to really become kind of a specialized Entity in a way, or at least to get some of the overall functionality of them. I’m still unsure what I think of that, but I definitely see your proposed use case as valuable. Whether your proposed solution is the right way to accomplish it is ultimately something the Fibery team will have to determine. 😃 --- _[View the full topic](https://community.fibery.io/t/references-to-views-as-a-way-to-emulate-embedded-dbs-in-notion/1247)._