Open silvester-pari opened 3 months ago
Description of the current OSC workflow is in https://github.com/ESA-EarthCODE/open-science-catalog-metadata/wiki/User-Guide%E2%80%90v.1.0.0#add-metadata-of-a-single-product-item-to-the-catalogue and https://github.com/ESA-EarthCODE/open-science-catalog-metadata/wiki/User-Guide%E2%80%90v.1.0.0#add-multiple-assets-at-once-with-github
Within EarthCODE, we started experimenting with open-source tools that automate parts of this workflow for the user (scientist, editor):
See Technical note for the current data publication process in OSC provided by @edobrowolska
The ideal outcome for metadata editing would improve the following points:
id
generation: we need a system of how to create unique id
s, either based on random identifiers (less user readable) or by combining metadata properties into an id (harder to check if the id
is actually unique). It is unclear if currently there are technical means for checking the existence of an id
within the catalogIn regards to data management (uploading and storing files, referencing them etc.), the document provided by @edobrowolska gives more insight, but this is a bigger topic that requires more research and discussions.
Description of current workflow issues and future improvements (recommended) are provided in this document:
Technical note of the current publication process in OSC.docx
You may find updated EarthCODE user stories here:
Please also refer to (https://github.com/orgs/ESA-EarthCODE/projects/5/views/8?pane=issue&itemId=72092886)
Hi @silvester-pari,
I hope this captures what we discussed this morning. This should be a useful reference when we learn more about the actual platforms we will use with EarthCODE.
As discussed this will:
Describe the current EarthCODE GitHub Workflow (or user journey) Describe the current EarthCODE GitHub Workflow by role (or user journey by role) Describe any current Workflow issues with support from @edobrowolska Describe any potential GUI enhancements to the portal to duplicate the GitHub Workflow functionality (if they provide a user benefit)
The workflow can be described using diagrams or text as appropriate. The workflow can refer to existing OSC artifacts is helpful
Note that this tech note informs the following stories (and it may indeed resolve them)
https://github.com/orgs/ESA-EarthCODE/projects/5/views/3?pane=issue&itemId=59760877 https://github.com/orgs/ESA-EarthCODE/projects/5/views/3?pane=issue&itemId=59761187 https://github.com/orgs/ESA-EarthCODE/projects/5/views/3?pane=issue&itemId=59761826 https://github.com/orgs/ESA-EarthCODE/projects/5/views/3?pane=issue&itemId=59761923