|
|
|
# Current process
|
|
|
|
|
|
|
|
## Onboarding procedure
|
|
|
|
|
|
|
|
## Curation process
|
|
|
|
|
|
|
|
* collaborative curation >> send email to group for every addition
|
|
|
|
## collaborative finale curation
|
|
|
|
Proposal
|
|
|
|
* when receiving alert for an addition into the escape2020 community
|
|
|
|
* send email to group of curators
|
|
|
|
* 1 week review process
|
|
|
|
* this could be automatized through gitlab with auto merge requests
|
|
|
|
|
|
|
|
## Re-assess inclusion in the OSSR
|
|
|
|
|
|
|
|
What shall we do with records included before the onboarding procedure?
|
|
|
|
Or if we update our requirements for the OSSR?
|
|
|
|
|
|
|
|
|
|
|
|
# ESCAPE OSSR outside contributors
|
|
|
|
## ESCAPE OSSR outside contributors
|
|
|
|
|
|
|
|
Role of the OSSR and positioning with contributors outside of ESCAPE?
|
|
|
|
|
|
|
|
* do we want contributions from non-ESCAPE contributors?
|
|
|
|
* what is the process for these contributions?
|
|
|
|
* today, same onboarding process
|
|
|
|
* how de we foresee the OSSR after ESCAPE?
|
|
|
|
* do we want to request ESFRIs official software into the OSSR?
|
|
|
|
* if they are already in Zenodo, do we want to expose those ? through eOSSR, from recognised communities?
|
|
|
|
* shall the OSSR act as an aggregator?
|
|
|
|
* this is in contradiction with the current curation process
|
|
|
|
* what standards do we want to impose?
|
|
|
|
* with other standards, or defined differently, we could pull from Zenodo or even other resources and ensure a future to the OSSR after ESCAPE
|
|
|
|
* current DAC21 CTA uses software that is not in the OSSR (and is not planned to be at the moment) |
|
|
\ No newline at end of file |
|
|
|
* currently, outside contributors follow the same onboarding process.
|
|
|
|
Are there other possibilities?
|
|
|
|
|
|
|
|
|
|
|
|
# how do we foresee the OSSR after ESCAPE?
|
|
|
|
|
|
|
|
- the same onboarding process is not sustainable after ESCAPE
|
|
|
|
|
|
|
|
- do we want to request ESFRIs official software into the OSSR?
|
|
|
|
- if they are already in Zenodo, do we want to expose those ? through eOSSR, from recognised communities?
|
|
|
|
- shall the OSSR act as an aggregator?
|
|
|
|
- this is in contradiction with the current curation process
|
|
|
|
- what standards do we want to impose?
|
|
|
|
- with other standards, or defined differently, we could pull from Zenodo or even other resources and ensure a future to the OSSR after ESCAPE
|
|
|
|
- include other (validated) communities in the OSSR (as an aggregation of communities) --> curation falls back to these communitiess |
