silvester-pari
commented
4 months ago @GarinSmith If I understand correctly, this part of the workflow will not be covered by the Portal GUI, since "publishing"/approving a change to a STAC file would be something only administrators are able to do (via the GitHub GUI). This process is the same as the current one in OSC (merging the PR into the main metadata repository, then the builder builds the catalog and the harvester picks it up).
Regarding the previous step, using the Portal GUI to create the PR (as an alternative to using GitHub directly) see https://github.com/ESA-EarthCODE/portal/issues/14
(originally created by @GarinSmith)
The idea is that we re-use the existing GitHub approach to submit STAC Products, but allow them to be published to OSC by the Portal.
This may help scientists, because the platforms are expected to publish products to GitHub on their behalf, however the final publishing step still needs to be controlled by the Scientist. This means the scientist could avoid using GitHub directly to publish if they prefer.
The next step might be to provide a GUI to allow STAC Products to be submitted to the OSC. This might help scientists who want to do local development and publish direct to the GitHub via the Portal GUI.
This is a "Publishing" requirement for the OSC in the Architecture Document.
Hi @silvester-pari ,
Is this what you were suggesting today? We can discuss further if needed. I think it makes sense to do this before the other story. Note that i) We can use existing product STAC definitions to test this. ii) We can use the same approach to publish Experiments and Dashboards when we know what they look like.
Garin