This is very much needed. It is really troubling to have so many relations and it seems you have to remember which ones are used for which type.
Extra feedback:
I hope we will still be able to create many relations that works on a global level, like many differents Tags relations.
I’m really affraid that Tags as Object and this specific feature could stop the ability to create many global Tags relations (not values, relations).
Yes, agreed. I think the best solution is that a relation is, by default, list-specific (set or collection); and when you create it, there is an option to “add to Anytype library” or “create as global relation” so it is available outside that specific list.
WHAT DO YOU RECOMMEND?
Multiselect relations always display the full list of options in the autocomplete suggestions. However, in some cases, only the options already used for a specific object type are relevant—for example, when applying context-specific tags. It would be helpful to have an option to restrict the autocomplete list to show only the values associated with the object type being modified.
The adjustment could potentially be applied to other relation types too.
HOW COULD IT BE DONE?
Add a “Limit scope” option in the object type definition page, in the “relations” section (which btw I still didn’t really get what it does, I mean what’s the difference if I add a relation there or not)
REAL WORLD USE CASES
Couple if examples:
- When applying apply tags to a trip I do not want to see the tags I used for the projects.
- Be able to use the “Status” relation for different object types, with context-specific values.
RECOMMENDED ALTERNATIVES
The alternative is to assign a different name, potentially using the “path,” as done in the LocalFirst community. While this approach works to some extent, it results in longer and less readable names, which can be problematic for column names and the ellipsis applied to relation names in the content.
ADDITIONAL CONTEXT
None
Does this request correspond well?
I saw that one, but honestly, even after reading it a few times, I don’t really get it, the description looks too convoluted for me.
My case is simple, limit the values displayed in the autocomplete and show only the ones that have been used for that object type.
Hi, i search for the same problem but i don’t see a similar one.
*Define a specific feature that is missing or could be improved:
I propose a way to make Tags, useful and less frustrating because right now, tags are set globally. A tag “Vegetarian” from a type recipe is selectable for a type Project… etc…
*ᅟDetail the solution you would like to get what you need: I propose that from the properties or a template we can select only the tags that could potentially used for this specific tag.
*Describe how this feature would be used, and why it should be implemented.
This is the exemple from a template of family hub and i added recipe but i can select any global tag
*ᅟExplain any workaround or feature you may have considered: I don’t have any workaround
you just need to make a new multi select property and that will basically act as a tag
As dxn0 suggest, you can create your own property, like “Type of recipe”, as select or multi-select.
The only problem is that if your properties have the name “Tag”, you’ll now have two tag properties. And so on, it’s hard to keep track. And by naming things differently, you still have to find names.
So there’s also a demand to limit the scope of properties (for example, to limit them to one type) :
(if it’s the same request, I’ll group it together)
Interesting
Thank you for your response
Related discussion: