Since we already have system default properties like last-modified date or creation date, I believe the need for space-wide properties are quite clear (or maybe strictly speaking, we also have universal properties that works across all spaces, which might be even crazier to attempt to play around and organise XD)
For my use case, I would be having these space-wide properties:
- Core & Side - for creating pseudo hierarchy, This could be a collection-specific group of property to better manage properties, but the scope of this group of property is applicable for space-wide objects.
- While it is essential to distinguish space-wide or collection-specific properties, Less friction while inserting a Relation in a Page needs to be addressed. Collection-specific properties should be easily searchable and addable to objects which had not be granted CollectionA status. (Or collection status need to be easy to give objects)
- Date/Time - for time-stamping, but I hope it can support aliases for different collections.
- e.g. DateTime as Watch Date in entertainment collection, but Occurring Date for news collection.
- This is space-wide because I want to query them and show in calendar under one Date Property.
- It would be great to have Assigning Multiple Dates .
As for implementation of space-wide properties, I still think relation library should be revived, but not in the same way as previous/current property menu. Following the collection-based UI design, it would be nice if we consolidate property creation menu in collection form.
- Each row is a single property, and each column is one property option e.g. Property Type then pop-down menu for each options (like tag).
- Then we can have individual views for individual collection to manage the relevant properties (and their possible property aliases).
- A view for all properties can have a multi-select option to determine if it is space-wide and its corresponding collections/type.
- For collection/type that ‘inherited’ space-wide properties, allow property alias to be editable but lock out and show grey text for all other property options governed by space-wide management view (and then clickable to jump back to the space-wide view for property amendments)
- This would work hand in hand with Creation of Relations from scratch and Type graph view .
- A high number of collections and property management view can be hard to access if there are lots of views, hence search and pin would help.
To add, these few days I have been wanting to create multiple entries in a collection which lies under the same object. For example, I have a storage/stock list to track how much stuff I have and if restocking is needed.
- I bought 20 types of teas and each has their health benefits. I want to track how many teabags or grams of specialised tea can be brewed. Each consumption is an individual row of data with its own contents for the group of properties e.g. consumption date, consumption amount, brewing time, rating
- This enables calculations of available amount with Derived Relations (Formulas) - which should be doable without LLM, like with simple reference to Sheet2 or macros in excel.
- This benefits commercial use of Anytype where businesses track and calculate their transactions, stocks and cost/gain
- (Sorry for being annoying for keep mentioning this, but relation-data model and references to foreign tables are still my suggested way to manage all these.. Each consumption is its own object but referenced to/stored under the specific Tea)
- This enables calculations of available amount with Derived Relations (Formulas) - which should be doable without LLM, like with simple reference to Sheet2 or macros in excel.
- In the meantime, can we have multiple entries/rows of properties for the same object?
