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

[server] replace native django route /results/{uuid}/json/ with a DRF api/results/{uuid}/json/ #199

Open
Tointoin opened this issue May 30, 2020 · 1 comment
Assignees
Milestone

Comments

@Tointoin
Copy link
Collaborator

Tointoin commented May 30, 2020

@gnuletik @yomguy

  • api/results/{uuid}/json/ should return the entire content of potential result's hdf5 file. A subprocessor_id query param could allow to choose part of the content. A custom filter (as for ItemWaveViewFilter) could allow to describe hdf5 content structure in the schema.

  • another route may allow to provide hdf5 file content with start/stop and nb_pixel query params as for waveform, for under sampling on the backend side for zooming purpose. Particular focus has to be given to the multiple potential data types on the y axes (e.g. a column of value for a spectrogram, e.g. a single value for an onset detection or no y axes for a full track value or potentiel labeled data instead of numerical values).

@gnuletik
Copy link
Collaborator

gnuletik commented May 30, 2020

Yes !
That would also help for the docs / schema / SDK because native django routes are not available in the schema.

@gnuletik gnuletik reopened this May 30, 2020
@Tointoin Tointoin changed the title [server] replace native django route /result/{uuid}/json/ with a DRF api/result/{uuid}/json/ [server] replace native django route /results/{uuid}/json/ with a DRF api/results/{uuid}/json/ Jun 1, 2020
@yomguy yomguy self-assigned this Jun 2, 2020
@yomguy yomguy modified the milestones: 1.2, 1.3 Jan 24, 2023
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

3 participants