User story

As an arches application developer, I would like to be able to query and update data for a resource model by a semantic label like a node alias (guaranteed unique) or widget label rather than constructing tiles directly and having to know their UUIDs.

Precedents

• relational views
• Arches ORM (experimental)

Proposal

Another approach would be to provide, in core arches, a solution that:

• annotates resource instance tile data onto the ResourceInstance model instances via Django querysets for Django-native querying, updating, related-object selecting, prefetching, paginating, signalling, etc.
• dogfoods the existing python application methods (thereby reducing drift) for:
  • tile validation
  • edit log, indexing side effects
  • function triggers
• generates (customizable) django rest framework serializers from your resource models (similar to the way django rest framework can generate serializers from your django models in general)
• reads from dynamic graph data, avoiding the need to take snapshots of "well-known" models or write migrations or deploy database views

Demo

Example queries might look like this: