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

Change to linking flow #3

Open
GFibrizo opened this issue Aug 8, 2019 · 0 comments
Open

Change to linking flow #3

GFibrizo opened this issue Aug 8, 2019 · 0 comments
Assignees
Labels

Comments

@GFibrizo
Copy link
Collaborator

GFibrizo commented Aug 8, 2019

Problem

The model buyer has to be able to publish the requirements of the data needed for the training of a model, and the data owner should have a window of time that is wide enough to see the requirement, upload a dataset that fulfils those requirements and accept the request.

Solution

  • Refactor the "link_dataset_to_model_id" endpoint. Split it into several.
    • 1 for receiving the requirements over the data
    • 1 to get all the requirements that have been sent so far (or the ones pending)
    • 1 to get the detail of a specific requirement of data
    • 1 to upload the dataset
    • 1 to accept the training (maybe this isn't a must)
@GFibrizo GFibrizo self-assigned this Aug 8, 2019
This was referenced Oct 11, 2019
This was referenced Oct 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant