You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some proposed functions will require the API to provide a richer description of the matrix. The /ticket endpoint seems like the best place to add this. Doing so will convert that endpoint into one that returns a matrix description with the download URL as one of the metadata fields. Other possible fields include: available formats, default units, matrix dimensions and labels for each dimension.
Is this something we want to do?
Is /tickets the right place for this?
What fields should be added?
The text was updated successfully, but these errors were encountered:
Some proposed functions will require the API to provide a richer description of the matrix. The /ticket endpoint seems like the best place to add this. Doing so will convert that endpoint into one that returns a matrix description with the download URL as one of the metadata fields. Other possible fields include: available formats, default units, matrix dimensions and labels for each dimension.
The text was updated successfully, but these errors were encountered: