ECAS part is done (client developed and ready), now waiting for B2SHARE team to finish their developments; this is not a blocker, ECAS plan will not change depending when or if this comes
OneData integration
The ECAS/OneData Integration behind a proxy activity has been completed (https://jira.eosc-hub.eu/browse/EOSCWP10-67). A notebook describing the integration use case has been also released.
B2HANDLE-OneData work is more a WP6 concern; but if ticket is addressed, its outcomes can & should be employed by ECAS to demonstrate use of PIDs across EOSC components. (https://jira.eosc-hub.eu/browse/EOSCWP10-45)
New Ophidia releases, deployed also now at DKRZ, DKRZ instance up to date
IAM-ECAS integration in good shape. Extensions to JupyterHub and PyOphidia have been implemented. Currently being tested on a development instance at CMCC.
More use cases with notebooks developed at DKRZ with detailed help from CMCC team; demonstrator at ECAS workflow repository available, can also be used in future trainings
IS-ENES & EOSC-hub website updates (catalog & marketplace), links need to be updated
Training efforts
Training delivered by ECAS team at EGU 2019 in April
Training currently ongoing locally in the context of a university course in Lecce.
Next call provisionally June 21, 09:00 CEST
There are minutes attached to this event.
Show them.