Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expanding /ticket return fields #96

Open
saupchurch opened this issue Mar 26, 2021 · 0 comments
Open

Expanding /ticket return fields #96

saupchurch opened this issue Mar 26, 2021 · 0 comments

Comments

@saupchurch
Copy link
Contributor

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.

  1. Is this something we want to do?
  2. Is /tickets the right place for this?
  3. What fields should be added?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant