Update MAP-Core on API developments

[elisabettai]

MAP-Core will have to report every quarter about our APIs used by the MAP Portal widgets. This will likely involve having regular calls with them and/or providing documentation in time. @pcrespov

And updating Portal datasets when MAP requests that. @elisabettai SIM-Core Role:

• Timely provision of documentation for new APIs

The general MAP-Core milestone says:

Description: Support the integration of new SIM (oSPARC) APIs via the MAP widgets on the SPARC Portal, work with SIM to support MAP functionality on oSPARC. For example:

• Expose new capabilities on the SPARC Portal via the Simulationvuer. This might include: Updates required to match oSPARC authentication service changes ( #1091 #1090 )
• Explore caching of user information via portal profile for use with extended services (#1095 )
• Evaluate how to leverage the extended study configuration API as it evolves (#1110 #1111 )
• Migrate OpenCOR plugin on oSPARC to use libOpenCOR and the new SIM plugin-building tools
  • • will enable progress monitoring which is not possible with current OpenCOR plugin (#1095 )

Acceptance criteria:

Quarterly reporting on new SIM APIs used by the MAP Portal widgets. Attend all SIM-Core Y7 webinars

Prerequisite: n.a

Timeline: continuous

SIM-Core Role:

Timely provision of documentation for new APIs

from wrike 4.2 SIM API support

[elisabettai]

HI @pcrespov, could you maybe summarize the ongoing work with Alan? Also feel free to redirect me to another case if you have one.

[pcrespov]

HI @pcrespov, could you maybe summarize the ongoing work with Alan? Also feel free to redirect me to another case if you have one.

Hi @elisabettai . The interactions with MAP-Core in the last sprints have been mainly for two topics:

• I have been following https://github.com/ITISFoundation/osparc-issues/issues/1135. Check associated wrike to see more details. In short: we have released the API with the port-schemas, reviewed his use-cases and we will meet on January to follow up.
• @bisgaard-itis assisted them to fix old test scripts they had running in the portal against osparc public API

[elisabettai]

@pcrespov, have you met with MAP in January as anticipated in wrike and/or is there any new progress since we published the ports schemas?

[pcrespov]

@pcrespov, have you met with MAP in January as anticipated in wrike and/or is there any new progress since we published the ports schemas?

@elisabettai not yet. I was expecting them to contact me. I will send them a reminder by the end of the week.

[pcrespov]

Update Sprint Schoggilebe

• Meeting with Alan from MAPCore with Pedro from SimCore on Tue Feb 14, 2024 (22h ZH-time)
• Overview of discussion points:
  • Authentication (https://github.com/ITISFoundation/osparc-issues/issues/1091)
    • How to reuse ORCID auth from the portal to authenticate in oSPARC
  • JSON-schema for service ports:
    • New entrypoint with json-schemas of i/o ports already available in oSPARC API
    • This feature allows the service creator to describe ports on the service side
    • A GUI could be auto-generated in the portal.
      • Upgrade of Vue version in the portal facilitates using jsonforms
    • In some cases this is not possible
    • either because
      • the GUI depends on the dataset (not only on the service) or
      • the service did not define sufficiently the ports.
    • Therefore
      • the GUI has to be custom-made on the portal side next to data and
      • the service in osparc used only to run the computations.
    • Some of the MAPCores examples with the Simulation Viewer fall in this category.
  • Updating OpenCore Service (https://github.com/ITISFoundation/osparc-issues/issues/1137)
    • Discussed about how to update Open
• Further details by MAPCore here