Please, help me... What's the point of the collection If I can use a Tag, instead? And it will work better. It allows me to connect everything (which is the point of the Capacities, isn't?) And it's fast to tag a note, I just have to type #.... With collections I have to manually click click click... until I assign a page to a collection. 1:49 Let's take the "astrophysics" tag as an example (video). Let's Imagine if it was a collection I have an object: Lecture and an object: Person I have an Astrophysics collection (Lecture) and I also have an Astrophysicist collection (Person) Using Collection I couldn't have a page select and connect both. Because those collections are not from the same type/object. But, with tags I can. Not only that, If I need that, I WILL NEED TO create the tag to connect both.. Tag: Astrophysics. Filter: tag_Astrophysics + type_Person = Astrophysicist Filter: tag_Astrophysics + type_Lecture = Astrophysics I mean, isn't that how our brain works? An astrophysicist is a person with an 'astrophysics' tag!? I really think that collection is pointless. Think with me.. What is a collection? I mean.. If I have a type/object and I want to group a bunch of notes in a "collection", then.... I have a 'shared topic' between those notes. And those connections will ALWAYS occur between different objects. That's how humans works. I connect John (person) with his book (book type) which I had a lecture (lecture type) and where I Tweet about those, everyweek (tweet other type) So there's no point in 'collecting' only things that are the same type. As a human, as my brain works, I will always vary the POINT OF VIEW, based on my needs on that moment. On the example above, sometimes I want to see "john" from the Person perspective, sometimes from the Book perspective, sometimes from the Lecture perspective For me, to connect that I'll need a Tag. So, why use collections? It's literally on the website: "Folders and hierarchies limit our creativity - They silo our thinking. They are too rigid to structure our dynamic, diverse, and interconnected work." so... we create the collections to FOLDER and create hierarchies and limit our creativity? I mean... Tag is a "over-powered" collection, so why would I limit myself and use collection of types?! If I create to many tags, lets the capacities AI suggest collections based on topics and I just click "confirm". We, humans, have MILLIONS of mental 'tags'.
I thought about this, and I disagree. 🙂 Both tags and collections have their merits, imo. TAGS: a property you assign to different object types. ➝ for GLOBAL USE. Like "#urgent" or "#inspirational". Why? Because both a Quote, a Book, or a Person (= 3 different Object Types) can be "#inspirational". So if you want to "bind" all inspirational stuff together, you need a property that transcends different object types ➝ a tag! COLLECTIONS: a property you only apply to 1 Object Type, suited to subdivise. ➝ For SPECIFIC USE. Example: Object type "Person". Collections: "Musician", "Writer", "Best Friend". These properties will ONLY apply to the object type they belong too. No Book or Quote or Movie will ever be a "Musician". Hence it is smart to silo these properties inside this Object Type (in the form of a Collection), so as not too clutter your global tag collection. Yes, of course: if you want you can still use Tags for that too... But there's ANOTHER DIFFERENCE: with collections you can see a (finite) amount of options while adding the property to your object. This can be helpful if you try to organise your stuff. "Which subdivisions did I make in my People Objects? Let's see..." And you browse through them and select what's appropriate. With tags - if you use them for each and every property you assign to each and every object - you'll soon find yourself drowning in a near-infinite amount of tags. So, what's the problem? Well, when you try to categorise your notes, you have to create your tag structure from memory ('which tags did I use for persons?') and it has to be pretty exact ('Did I create a different tag for #teacher and for #professor? Did I use #doctor or #healthcare worker? ...') and so on. No problem if you prefer using tags, but in my experience too much global tags soon ends up in total chaos. 😛 Oh, and as for the "NO SILO'S" thing: I wouldn't take that too seriously... I mean... It's all about creating Object Types with specific properties only bound to these objects. What's that, if not a silo?! 🙂
@@CapacitiesHQ when trying to log in to vote on features, your website is getting blocked by Firefox due to 'SSL_ERROR_RX_RECORD_TOO_LONG' and Malwarebytes Anti-Malware flags your website as 'phishing'. 🤔 I think there's some work for your webdevelopers!
Is there a way to autmatically add objects to collections based on a certain property? Thinking something like "Relationship" which is a multi-select property. Each select option could be connected to a collection so any time you create a person with "Relationship" containing "Friend" they are automatically in the Relationship/Friend collection? Or am I thinking too much into this?
The way I expected Collections to work, is I add a collection and filter that collection based on properties. Having to add each individual record to each desired collection is tedious. I'd rather create a collection that adds everyone that is a Musician. So, If I create a new musician I don't have to add them to the collection they are automatically added because their properties meet the filter criteria. Maybe it's possible, but it's not intuitive.
I was struggling to wrap my head around how Capacities organization worked and this explained everything I needed to know. You rock Beth!
Please, help me...
What's the point of the collection If I can use a Tag, instead? And it will work better.
It allows me to connect everything (which is the point of the Capacities, isn't?)
And it's fast to tag a note, I just have to type #....
With collections I have to manually click click click... until I assign a page to a collection.
1:49 Let's take the "astrophysics" tag as an example (video). Let's Imagine if it was a collection
I have an object: Lecture and an object: Person
I have an Astrophysics collection (Lecture) and I also have an Astrophysicist collection (Person)
Using Collection I couldn't have a page select and connect both. Because those collections are not from the same type/object. But, with tags I can. Not only that, If I need that, I WILL NEED TO create the tag to connect both..
Tag: Astrophysics.
Filter: tag_Astrophysics + type_Person = Astrophysicist
Filter: tag_Astrophysics + type_Lecture = Astrophysics
I mean, isn't that how our brain works? An astrophysicist is a person with an 'astrophysics' tag!?
I really think that collection is pointless.
Think with me.. What is a collection? I mean.. If I have a type/object and I want to group a bunch of notes in a "collection", then.... I have a 'shared topic' between those notes. And those connections will ALWAYS occur between different objects. That's how humans works.
I connect John (person) with his book (book type) which I had a lecture (lecture type) and where I Tweet about those, everyweek (tweet other type)
So there's no point in 'collecting' only things that are the same type.
As a human, as my brain works, I will always vary the POINT OF VIEW, based on my needs on that moment. On the example above, sometimes I want to see "john" from the Person perspective, sometimes from the Book perspective, sometimes from the Lecture perspective
For me, to connect that I'll need a Tag. So, why use collections?
It's literally on the website:
"Folders and hierarchies limit our creativity - They silo our thinking. They are too rigid to structure our dynamic, diverse, and interconnected work."
so... we create the collections to FOLDER and create hierarchies and limit our creativity?
I mean... Tag is a "over-powered" collection, so why would I limit myself and use collection of types?!
If I create to many tags, lets the capacities AI suggest collections based on topics and I just click "confirm".
We, humans, have MILLIONS of mental 'tags'.
Same question here!
I thought about this, and I disagree. 🙂 Both tags and collections have their merits, imo.
TAGS: a property you assign to different object types. ➝ for GLOBAL USE.
Like "#urgent" or "#inspirational". Why? Because both a Quote, a Book, or a Person (= 3 different Object Types) can be "#inspirational". So if you want to "bind" all inspirational stuff together, you need a property that transcends different object types ➝ a tag!
COLLECTIONS: a property you only apply to 1 Object Type, suited to subdivise. ➝ For SPECIFIC USE.
Example: Object type "Person". Collections: "Musician", "Writer", "Best Friend".
These properties will ONLY apply to the object type they belong too. No Book or Quote or Movie will ever be a "Musician". Hence it is smart to silo these properties inside this Object Type (in the form of a Collection), so as not too clutter your global tag collection.
Yes, of course: if you want you can still use Tags for that too...
But there's ANOTHER DIFFERENCE: with collections you can see a (finite) amount of options while adding the property to your object. This can be helpful if you try to organise your stuff. "Which subdivisions did I make in my People Objects? Let's see..." And you browse through them and select what's appropriate.
With tags - if you use them for each and every property you assign to each and every object - you'll soon find yourself drowning in a near-infinite amount of tags. So, what's the problem? Well, when you try to categorise your notes, you have to create your tag structure from memory ('which tags did I use for persons?') and it has to be pretty exact ('Did I create a different tag for #teacher and for #professor? Did I use #doctor or #healthcare worker? ...') and so on.
No problem if you prefer using tags, but in my experience too much global tags soon ends up in total chaos. 😛
Oh, and as for the "NO SILO'S" thing: I wouldn't take that too seriously...
I mean... It's all about creating Object Types with specific properties only bound to these objects. What's that, if not a silo?! 🙂
I agree that having a keyboard shortcut to add a "collection" property while typing would be convenient though!
I want become a believer but its too expensive. Hoping to get a discount code for upgrade.
same
I want deeper collections! I need 2th ~ nth collections. For example, people > scientist > physics > ... Can you update like this?
This has been requested, feel free to vote on the ticket here: capacities.io/feedback/p/collection-of-collections
@@CapacitiesHQ when trying to log in to vote on features, your website is getting blocked by Firefox due to 'SSL_ERROR_RX_RECORD_TOO_LONG' and Malwarebytes Anti-Malware flags your website as 'phishing'. 🤔
I think there's some work for your webdevelopers!
Is there a way to autmatically add objects to collections based on a certain property? Thinking something like "Relationship" which is a multi-select property. Each select option could be connected to a collection so any time you create a person with "Relationship" containing "Friend" they are automatically in the Relationship/Friend collection? Or am I thinking too much into this?
You can do this with object type queries! We have a video on this : th-cam.com/video/35GCX55BNsE/w-d-xo.htmlsi=mhKpEG-QQrWolRwJ
The way I expected Collections to work, is I add a collection and filter that collection based on properties. Having to add each individual record to each desired collection is tedious. I'd rather create a collection that adds everyone that is a Musician. So, If I create a new musician I don't have to add them to the collection they are automatically added because their properties meet the filter criteria. Maybe it's possible, but it's not intuitive.
This will be possible with queries which are launching very soon!
awesome! @@CapacitiesHQ
Thank you for the explanation video. I'm finding it a little tough to dintinguish tags from collections. When should I pick one instead of the other?
Thank you for your question! We have a tutorial about this because it's a common question: docs.capacities.io/tutorials/tags-vs-collections
@@CapacitiesHQ I appreciate that, thanks. I get it now. Right now I just have a lot of pages and no other object types.