Summary of request
Administrator that is managing custom analysis schemas would like to be able to define meta data that describes the Schema. Example properties would be a description field, or a version that tracks to an external ontology or their own versioning system that is independent of the specific Song server.
Details
The Register Analysis endpoint should accept an additional, optional property meta. The value of this property is a JSON object. This meta object will be stored in the analysis-schema table and should be included with the analysis whenever it is fetched.
An example template for the content of the register analysis endpoint:
{ "name": "string", "meta": {}, "options": {}, "schema": {} }