@qualquertipo I think this will be possible in the future and should already be considered by the R&D staff , Quote Roman(CTO@Anytype)'s reply in telegram: "We have plan to create collections that stores ID’s of objects instead of just aggregating them(like a set does). For that reason we have created “Collection of”. "
@qualquertipo I don’t know if my understanding is correct, for the example you mentioned above, there is currently a way that is not necessarily suitable to do it:
You can first create two sets called “Books” and “Tools”, in each set, you can filter by “Lent” to generate a view,
and then create a set of sets (includes all sets by default) called “Lent”, you can filter out “Books” and “Tools” to generate a view, in this view, you click “Books” or “Tools” to see all the books or tools with relation “Lent”.
In this way, you need to click on the corresponding set to view the objects in it.
I am also thinking about how to use “Collection” in the future. I don’t know if the “Collection” can directly collect all the objects of the specified types through filtering in the future, and then display just like the current set view, or in some other way. Looking forward to the release of “Collection”.
It might be possible again once Sets from relation is released. Since sets has a Object type relation to currently represent the type of object it represents
Coming personally from Notion.so, I hope that their agnostic databases will be soon integrated to Anytype, because even if Sets from relation will be possible, I think I’m not the only one to find it constraining to have to add relations each and everytime just to be able to display different Object types in a Set.
Sets limited to a single object type can have a certain utility, but it would not have any advantage to supplant a kind of Sets that would allow many Object types.
Anytype has chosen a meaningful name and doing so it would seem logical to accept any type of Object in a Set, don’t you think?
I wholeheartedly agree. There is no reason to why sets should be limited to one type or to one relation. That just needlessly complicates things. The current functionality should be transferred to a new filter which would allow you to filter by type and the type relation should also get it’s own column in the set.
You can create sets by relation by going into the library and finding your relation in the relations tab. There should be a button in the top right corner to create a set by that relation. A proper way to create these should be in the next release.