Sub databases / Inheritance / Object inheritance
D
David Jaggi
Have the option to create subdatabases which inherit the attributes of the parent database but extends the properties.
Like have a database with places and a sub-database with restaurants and points of interest.
Log In
Steffen Bleher
Thanks for voting on this ticket.
Object inheritance is currently not on our roadmap. While we agree that this is an important power user feature, we think that there are many more topics that should be added to Capacities first. While including more work you can always reach the same result by duplicating settings across object types.
We still encourage you to vote on this ticket to get a better idea of the importance to users and to stay updated on the topic.
Steffen Bleher
Thanks for voting on this ticket.
Object inheritance is currently not on our roadmap. While we agree that this is an important power user feature, we think that there are many more topics that should be added to Capacities first. While including more work you can always reach the same result by duplicating settings across object types.
We still encourage you to vote on this ticket to get a better idea of the importance to users and to stay updated on the topic.
M
Marc Vanderstraeten
Definitely also waiting for this :-)
Steffen Bleher
Merged in a post:
Objekttypen verschachteln
B
Benjamin Reich
Die Möglichkeit, Objekttypen zu verschachteln wäre wirklich Praktisch - Bspw. Journals gleich Issues zugeordnet werden oder Bücher in mehreren Auflagen vorliegen
J
Justin Kroes
A good example of how this works is in Anytype. Each type's objects can be displayed in views that use distinct filtering, sorting, and property/column selection. This way, use can effectively create subtypes. If only their sidebar and search tools were up to par with capacities.
M
Matthew Johnson
I’ve been looking at all the apps in this space lately and I think Tana and Heptabase are the best examples of this. Both go beyond simple single inheritance with supertags. This approach attaches properties to supertags that can conceptually be thought of as a DAG. In Heptabase, any properties that appear in multiple supertags attached to an object (or their ancestors) are automatically shared by all of the supertags. I don’t know what the behavior is in Tana (maybe someone else does?).
This feature is extremely powerful. One example is that it enables creating a supertag for workflow-related properties that might apply to content of many different types.
I have many further thoughts on this feature space and would be happy to share more when you are ready to start thinking about it in more detail (which I hope will happen soon!).
J
Jeff Williams
I tend to agree with this. Originally, i just assumed this was going to be the functionality of the categories.
Steffen Bleher
Merged in a post:
Attribute inheritance like tana
c
chen wong
Supertag function of tana.
c
chen wong
It would be great if capacities could inherit properties like tana, as this would allow us to better structure information.
Inheriting properties for capacities, similar to tana, would be a valuable feature for organizing structured data.
Steffen Bleher
Merged in a post:
Objects -- any plans to implement a true or at least partial object-oriented model for objects?
E
Earl Takasaki
I think it would be great if you could create child objects that inherit all properties from parent objects. PKM Beth has an example on Youtube where she uses just a media type, then separates them using categories (i suppose you can use tags too). However, then she mentions, what if you want to add a specialized properties like "Author" that only applies to Books, "Director" that only applies to Movies, etc. Well, you can create custom objects for each type (lots of bespoke objects) or you can create a huge catch-all media object with all possible properties for media, then separate using categories. In a object-oriented model, one would first create a generic Media object that contain properties that would apply to just about any media type, then created child objects off that parent like Book and Movie: i.e., every Book is also a Media object and would "inherit" all of the properties of the Media object automatically and every Movie is likewise also a Media object. So you just have to add those properties that differentiate the Book type from other media types. If you search the Media database, you get all your media, but if you search Books, you only get books. Then you could also extend that to create specialized Books (say Novels and Biographies) that are children of Books. Also, let's say as an after thought you decide that a properties should apply to all media types? Well if you have create a dozen specialized media type, then you have to add it to each one, whereas in an OOO model you just add it to the Media object and it flows down to all of the objects. This would not force any complexity on users as they are free to use child objects or not, but would add a lot of power to those who understand the concept. People are free to go as complex or simple as they like, but they would not have to reinvent the wheel for every specialized type. Thanks for listening.
Steffen Bleher
Thanks for sharing. Agree with your observation, this is something we have on the radar. I'll merge it into the existing ticket :)
Load More
→