M2 Query I/O Port Descriptors for Study via API

ITISFoundation / osparc-issues

🐼 issue-only repo for the osparc project

3 stars 5 forks source link

M2 Query I/O Port Descriptors for Study via API #686

Closed elisabettai closed 1 year ago

elisabettai commented 2 years ago

Extend existing APIs (computational API, study creation and access, platform API), add new APIs (progress API, import/export API) as required by users and in support of the DRC APIs -- exposing queuering of service & study input/output port descriptions

Deadline: Month 2

Wrike M4.1.1

pcrespov commented 2 years ago

Goal for sprint Katherine Switzer

[x] Expose in the API: "a study, mark inputs/outputs and get schemas in api" (part of #626)
[x] https://github.com/ITISFoundation/osparc-simcore/issues/3457

REVIEW:

show json-schema of a published solver in swagger (e.g. solver with rich i/o)
Use json-forms to create a UI on a local Portal deploy for that input (nice to have, @ignapas @odeimaiz could help)

pcrespov commented 2 years ago

Update on sprint Katherine Switzer

Done

https://github.com/ITISFoundation/osparc-simcore/issues/3457
Proof-of-concept on how to integrate this feature in sparc.science app using json-forms. Will be shared with MAP-Core in the context of M4.4 SIM API support

Ongoing

Expose in the web API: "a study, mark inputs/outputs and get schemas in api" (part of #626)
Expose studies resources and its i/o ports in public API

pcrespov commented 2 years ago

Goal for sprint Athena

Expose in the web API: "a study, mark inputs/outputs and get schemas in api" (part of #626)
Expose studies resources and its i/o ports in public API

Review demo

Create a project and add ports
Retrieve project i/o port schemas via API

@mguidon would this fullfil this issue?

mguidon commented 1 year ago

I think this fulfills the requirements as stated in the Year 6 Milestones list.

pcrespov commented 1 year ago

Update on sprint Athena

Done

Expose in the web API: "a study, mark inputs/outputs and get schemas in api"
Expose studies resources and its i/o ports in public API

Open

This issues is mostly completed. Some open question/points remain though. Should we address now>

Ports with files
Expose to python client?

elisabettai commented 1 year ago

Hi @pcrespov, regarding your question if we should consider this milestone completed: this is the feedback from EN: "from the point of view of the sparc milestones, we consider it complete. however, for our own needs, we will need to finalize that implementation."

I'd proposed to create a new issue, if you want, with the remaining points and close this one.

fyi, the work done was reported to the NIH in the Q1 Report (I can provide you the link if you're interested).

elisabettai commented 1 year ago

Closing this one if favor of #792