Adding a property to an object that is not a collection
There may be objects that aren't part of any collections but for which you want to add properties.
In my case, I created a test note and wanted to add a “tag” property to mark it as temporary. I don’t care about the collection; I just need to label my object.
In fact, it took me a while to realize that this isn’t possible without a collection—I almost filed a bug report. Maybe you should revisit this.
I also have a “Note” page, which won’t be in a collection. There, too, if I want to add a property, it requires a collection.
If you require the use of a collection to add properties, perhaps you could provide a “Space objects” collection. But my “Note” page and my “test” page don’t necessarily need the same properties—that solves this issue, but it’s not entirely satisfactory in my opinion.
2 Comments
Sign in to comment
·11 days agoYes, this is a fundamental difference in the system.
In Anytype, to see these 'tag' properties, you have to set up a query and specifically filter for it, which makes it another step that many users frankly never learn to do.
In Anytwo, you just use the collection itself as a tag. Once you apply 'open source' collection to the object, you can then just immediately press the arrow button in the collection chip and it'll open a view with all of your objects. This removes the need to set up a tag property at all.
This does introduce a different potential problem, which is that you may have a lot of tags or that you may not want to have this 'collection tag' visible in the header at all times.
But this is not a bug per se, it's a new system. But this new system could be improved. Look forward to your comments.
I will close this issue for now, because there's not much to action. Soon, we will be implementing an updated architecture and we can revisit this topic.