Moving objects btw object body and properties sections
One of the great strengths of Capacities is that it allows to place objects in the body as well as in specified property fields. This greatly enhances the power and systemic intelligence and flexibility.
It becomes ever more important to have a way to swap/copy/move/transfer objects between body and properties sections. – Currently this is only possible by re-selecting from the dropdown in properties.
There are several workflows where objects can add up in either the body or the properties fields. And there are many scenarios where one wants to streamline this post-hoc, as part of aggregating, cultivating, managing ones objects and system etc. – The number of such scenarios only increased due to the many ways AI/LLM can now be used to fill/extend/improve content and work with object relations.
1 Comment
Sign in to comment
To add and illustrate a little the systemic issue/friction behind this – … maybe bringing in additional issues about autofill:
it seems I can´t make autofill pick up all items of an object type present in a body of an object and use those as relevant for the properties field in the same object. Even after including explicit instructions to do so in the instruction for autofill.
It seems there are two non-compabilities/frictions overlapping: 1) (non-)consideration and (non-)mobility of embedded/quoted objects and property fields for the same parent object type; 2) a lack of full predictability/coherent behavior in autofill (something I noticed also in other contexts when extected tags/property items wouldn´t show up, or the reason for (non-)population of fields were not really clear to me)
Regardless of the parts each of the two factors plays, what remains is that there is a kind of glitch/friction/non-transparency between quoted/embedded object items that are positioned in the *body* vs. the same objects placed (or expected) in the property head section.
For contexts where very high consistency of properties/relations in the overall system and need to shape/control/adapt their behavior is key this creates some systemic problems/inconsistencies. It´s also a bit ashame given that otherwise the free positioning of objects, which can appear as either inline/quote objects *and/or* as part of property lists and fields is such a genuine strong point of Capacities! 🦍