Skip to content

Jobs API custom and client-context metadata #4313

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

Closed
1 task done
mguidon opened this issue Jun 5, 2023 · 0 comments · Fixed by #4476
Closed
1 task done

Jobs API custom and client-context metadata #4313

mguidon opened this issue Jun 5, 2023 · 0 comments · Fixed by #4476
Assignees
Labels
a:api framework api, data schemas, t:enhancement Improvement or request on an existing feature
Milestone

Comments

@mguidon
Copy link
Member

mguidon commented Jun 5, 2023

Is there an existing issue for this?

  • I have searched the existing issues

User Story

When using the API to run computational jobs, the caller has to remember the job ids. Otherwise it is difficult to retrieve job information for a specific job (in s4l this will be stored a part of the smash project). I suggest to either:

  • allow user to add metadata as json and have an endpoint that searches inside this data
  • Add a something static that lets a user identify its job (displayName?)

Definition of Done

No response

@mguidon mguidon added the t:enhancement Improvement or request on an existing feature label Jun 5, 2023
@pcrespov pcrespov added this to the Watermelon milestone Jun 5, 2023
@pcrespov pcrespov added the a:api framework api, data schemas, label Jun 5, 2023
@mguidon mguidon changed the title Jobs API enhancenments Jobs API custom and client-context metadata Jun 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:api framework api, data schemas, t:enhancement Improvement or request on an existing feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants