Allow multiple types in entity property for custom types
planned
A
Alejandro Eyquem
When creating a custom type, you get the option to add a new property of any type of database (ie page, weblink, etc) or content (text, number, etc).
however, sometimes it could be desirable to have a poperty that can link to
any
item in any or some selected databases.For example, adding a "source" property to a note should allow to choose a weblink, audio, image, or custom type. and not limited to one type only.
Log In
Y
Yotam Dvir
It would be very nice to have, under the single and multi select properties, the ability to create arbitrary sums and products of objects and basic types (date, text, number..). So for example, in a Project we could have a multi select property of:
(Person+Organization)*Date
that is, filled with either a person or an organization, accompanied by the date they joined.
A
Alice Moore
I had mentioned in a post about fixed sets that using queries as the fixed set for select fields solves a lot of headache. Queries can pull from multiple object types and also programmatically filter by tags, properties, etc., so you're really selecting from the entities you wish, with no extra learning curve.
I do know queries is a paid feature, though, so that might not be everyone's favorite thing. It just made sense in my head that either queries, objects of a type, or collections can be used to choose what a select field is able to select.
michael_v_h
Merged in a post:
Do not limit linked content to one object type
T
Tim Sn
There may be instances where this behavior is desirable, so I think this should just be an additional option in the drop-down menu called "Any". Use case would be when I have an object property that is a select or multi-select list of other objects and I may want to link objects of different types.
B
Ben Slepp
There should be both options available when adding properties to an object, but you can only choose one method of the two at a time.
Option 1) I can select a specific object type and only objects of that type can ever be selected,
Option 2) I can select an "agnostic" object type that lets you select any object of any type.
Adding Option 2 should not necessitate removing strict selection properties (Option 1).
S
ShaoWei Teo
Seems to me that Capacities.io encourages bottom-up objects where we split it to be as fine as we can, e.g. I should store "books" & "articles" separately (as they have different fields), instead of a single type "readings". However occasionally we use fields to link to "readings". This feature would be great.
M
Matthew Johnson
Of course it will also be desirable to be able to name and re-use these lists of types. This is known in programming languages as a “sum” type and is extraordinarily useful, despite being absent in many mainstream languages. If Capacities wants to support robust modeling (and it should) it will need to definitely support sum types!
Steffen Bleher
Merged in a post:
Properties as objects
F
Fillipe de Souza
I think it would be a very big change, but it would be very useful if properties were universal, a referable object for any object type as well as tags. The capacity of Capacities in relation to other apps, such as Notion, I believe is precisely that the system is connected from end to end. Don't know if this is possible, but it would be a good feature.
Steffen Bleher
planned
michael_v_h
Alejandro Eyquem With the next release the text property will support rich text, like any other text block, and will also allow linking to any other entity. This will solve the problem you mention above, as you can add a "source" property as text and link to any weblink, audio, image etc. from there. This connection will of course also show up in the graph view and the backlinks, with the property name as a label.
Steffen Bleher
under review
Thanks for sharing. We are thinking about this as well. Need to get the pickers and layout done before that but we agree that this is a valuable extension.
Load More
→