It would be great if every model in Galaxy supported attaching metadata. This includes StoredWorkflows, steps, tools, histories, hda, ldda, etc.
This metadata would be accessible via api GET, PUT, POST transactions.
Ideally all objects returned via the api would have a 'metadata' field that contains key-value pairs. This allows applications built off the API to store application specific data in a structured way that is maintained by Galaxies underlying database schema constraints. If an object is deleted, the metadata should be cleaned up with it.
It would be great if every model in Galaxy supported attaching metadata. This includes StoredWorkflows, steps, tools, histories, hda, ldda, etc. This metadata would be accessible via api GET, PUT, POST transactions. Ideally all objects returned via the api would have a 'metadata' field that contains key-value pairs. This allows applications built off the API to store application specific data in a structured way that is maintained by Galaxies underlying database schema constraints. If an object is deleted, the metadata should be cleaned up with it.