# What is your dealbreaker with Anytype? **URL:** \ **Category:** Talk\ **Tags:** Community, Meta, Workflow, Multiplayer, Colors\ **Created:** [June 9, 2023, 9:53am UTC](https://community.anytype.io/t/what-is-your-dealbreaker-with-anytype/9406 "2023-06-09T09:53:37Z")\ **Posts on this page:** 1\ **Showing post:** 93
**Author:** ![Shampra](https://community.anytype.io/user_avatar/community.anytype.io/shampra/32/8056_2.png) [@Shampra](https://community.anytype.io/u/Shampra)\ **Post date:** [August 8, 2023, 9:37am UTC](https://community.anytype.io/t/what-is-your-dealbreaker-with-anytype/9406/93 "2023-08-08T09:37:47Z")
User case : user from Notion, with multiples database. In Notion, each database has its own properties (relations) and pages (objects). In AT, a relation or an object are in AT. In practice, this poses organizational problems and, with the multiplication of data, will tend to create a big “mess”. - All relation will be visible everywhere, all the time. If you have 50 databases with dozens of relations (usually specific to the db), you’ll have a list of 500 relationships to manage (add relationship → search the list…). If a relationship has the same name in different places, too bad, the relation list will display the same name several times. - The same goes for objects and type (the person I spoke to gave me a nice explanation of the problem, but I forgot). Hence the need to localize data that is of no interest at a global level. example with some FR : > [@Add support for collection-specific relations](https://community.anytype.io/t/add-support-for-collection-specific-relations/9784): > > WHAT DO YOU RECOMMEND At the moment, relations can only be space-wide. This means that every relation, even if it’s only used in a single collection, will appear in the relation library. It would be a huge quality of life improvement to have relations that are collection-specific and do not appear in the relation library. HOW COULD IT BE DONE When creating a relation from inside a collection, have a checkbox that says “add to library”. If the checkbox is unchecked, the relation is only visible… > [@Object Context](https://community.anytype.io/t/object-context/9686): > > I have been using AnyType more and more and I love Collections. They allow me to isolate some work from other work, like separating information about clients from one another in my notes. One issue that I have been running into is for each client I have some tasks that I need to complete. So, I created a set of tasks. It is nice that I can create a task right from the set of tasks object, but the task shows up on all other task lists. I have gotten around it by adding a relationship called “Co… > [@The options for Option relations should be local to each object type](https://community.anytype.io/t/the-options-for-option-relations-should-be-local-to-each-object-type/8066/3): > > @sambouwer Thanks for your reply! I would agree, but here’s the issue. The default “status” relation is already applied to all object types that have any sort of status by default - so that would be tasks, books, movies, etc. Mind you, this is the default, comes with Antype out-of-the-box status relation. Meaning if I set values for that status (the one that’s automatically applied by default to many unrelated objects) for one object, those options get added to the list for all the other object… > [@Ability to limit the scope of a relation](https://community.anytype.io/t/ability-to-limit-the-scope-of-a-relation/1553): > > Is your feature request related to a problem? Please describe. The add relation pop-up in the create type view lists all the relations across all object types, even the ones such as the camera, camera aperture, camera exposure & rotten tomato scores, etc. These relations are tightly coupled to an objects type. A rotten tomato score is not applicable to any type except a media or a web series. Same goes for the camera exposure relations which is only applicable for the image type. Sin… --- _[View the full topic](https://community.anytype.io/t/what-is-your-dealbreaker-with-anytype/9406)._