WHAT DO YOU RECOMMEND
One of Anytype’s strengths is that it doesn’t require you to come with your Entity–relationship model - Wikipedia already fully formed. You can create types and relations on the fly, so there’s no need to do Big design up front - Wikipedia for your knowledge.
This strength can be enhanced by enabling conversion between relations and values and corresponding types and objects. In particular, I’m thinking of the text, status, tag, date, and url relation types.
REAL WORLD USE CASES
Probably the most common case would be users wanting to convert statuses and tags. Suppose you’re building your recipe database, and you create an Ingredient type, and on that type you create a tag relation Allergy to keep track of diseases that prevent people from safely eating that ingredient.
Later on you come to be interested in medicine in it’s own right, and you want to start storing knowledge about diseases, including but not limited to diseases that prevent people from eating certain things. You could create a Disease type and start creating objects manually.
But you’ve already got a great set of tags. What you want is to promote the Allergy relation to a Disease type, and each of the tag values to an object of the Disease type. The old relation is converted to an object relation, so that where once Ingredients were tagged with the Allergy relation, now they’re related to the Disease objects instead. In one step you’ve married your knowledge about ingredients to your knowledge about diseases.
It can even be done in reverse, since generating a tag relation from a set of objects doesn’t necessitate actually deleting the objects.
HOW COULD IT BE DONE
The context menu for relations should have a Turn into Object command the same as blocks. The user could select an existing type or create a new one.
Sets that display, filter, and sort with the relation are updated as necessary. Sets that use the Kanban layout will need to be able to group by object relation types.