I am using relations to manage many objects in my Vault. A lot of times the same relation is being repeated but is related to a separate note so there are many duplications and It’s getting really convoluted to find the right relation to the correct note.
Creating a segmented list for relations, for example:
Instead of just having two separate statuses in the same relations list.
When working with many relations that are relevant to different projects / notes.
C.c
March 23, 2024, 2:25pm
2
Would these requests resolve your needs?
If relation is full object, we can embed other relation/object into the naming of the major relation/object, or have hierarchies.
I think, moving forward, that there will be value in having the object collection distributed in distinct hierarchies with versioning and owners.
there should (imho) be CORE generic attribute types,
(bool/str/int/float/enum/address/lat-lng/street/city/state/country etc)
there should (imho) be CORE object types/templates
These should be curated/owned by anytype.
These should be distributed versioned.
There could be add-on collections (scientific | architectural | fashion | creatures | plane…
For easier identification between objects/relations that have similar names, we just need to distinguish between themselves.
Naming is not really the solution, because you than have many types of naming and a lot of relations flooding the add relation window. There should b another system to sort through relations and it better be visual based and note naming based.
