During discussions about existing implementation and about AQL it was obvious that we need to formalise the concept of TAG/LABEL/ANNOTATION associated with an data instance (COMPOSITION).
The name is not yet settled, but in any case this new feature is something that should be done in release 1.1.0
Notes from the meeting:
tags to make queries easier
tags to record form ids (Marand)
tags purely local? I.e. part of / not part of the data
Marand / DIPS /Code24 - stored outside system with references; Code24 ref point just to VERSIONED_OBJECTs
do tags point to specific versions? Probably 2 types
what do tags look like in AQL? Or as execution parameter to an AQL?
standardise the structure for access by AQL, REST API - potentially define classes representing ‘tags table’.
Can someone interested in this create an example to see how these tags should be used? I don’t have a clear understanding about this requirement.
See comments for a link to wiki page where current state of the art is being documented.