| Title | EOSC IF Guidelines for Data Sources to onboard Research Products |
|---|---|
| URI | |
| Revised version links | |
| Link to Metadata | |
| Date Issued to EIAC | 20.06.23 |
| Submitted by | PAOLO MANGHI |
| Outcome of EIAC review | endorsed, 22.08.23 |
| Date Issued to EIAB | 22.08.23, 13.10.23 |
| Outcome of EIAB review | accepted 17/10/23 |
| On portal? | yes |
Overview
The proposed document has been submitted for inclusion in the EOSC Interoperability Framework.
Comments should be made either on eiac@eoscfuture.eu, where they will be archived for future reference or added to the change log below. Comments posted to other discussion methods will not be included in the review.
Statements of Support/Deny
All members of the EIAC are encouraged to make a statement of support or dissension in consideration of this proposal.
Name | Organisation | Support or Deny | Reason (if denied) |
|---|---|---|---|
| Jorik van Kemenade | SURF | support | |
| Paul Gondim van Dongen | SURF | support | |
| Sabeel Shah | support | ||
Comment/Change Log
Please fill in any comments or proposed changes below.
Number | Current Text | Proposed Text / Query | Commenter | Action |
|---|---|---|---|---|
| 1 | EOSC Data source managers/developers (personnel acting on behalf of Data Source providers) (Section 1) | Maybe we should define somewhere what we mean by a EOSC Data Source? | Jorik van Kemenade (SURF) | |
| 2 | In order to onboard research products, data source providers must follow the EOSC Data Source onboarding procedures. Once the EOSC Data Source is onboarded, the following Interoperability Guidelines must be implemented. (Section 2) | Section 2 is meant to focus on the description and main features. I am not sure if this is the place to put the steps for onboarding. If we decide to do it, make sure that they are also duplicated in section 5. | Jorik van Kemenade (SURF) | |
| 3 | To this aim, the EOSC has adopted a System of Systems approach which tries to maximize global coverage of research products within the EOSC Resources Catalogue, while minimizing the amount of effort to be done to deliver such content. (Section 3) | Consider removing this sentence. It describes on a very high level what solution has been implemented. it does not answer the question of what specific needs of the community can be met by implementing this guideline. | Jorik van Kemenade (SURF) | |
| 4 | Once the EOSC Data Source fulfills these IF guidelines (...). (Section 5) | I would like to see that section 5 covers all information needed to understand and perform the integration. This means that the IF guidelines, which are currently covered in section 2, need to be moved here or need to be duplicated to this section. | Jorik van Kemenade (SURF) | I agree the structure of the document is redundant, but not with the replication of content. |
| 5 | The Dashboard supports capabilities for automated compatibility validation and for the final request of integration, which is followed up by EOSC data curators. (Section 5) | Is it possible to link to a guide explaining the usage of the dashboard? | Jorik van Kemenade (SURF) | |
| 6 | OpenAIRE Guidelines1 (Section 7) | Please include the link directly instead of having a footnote. It might be nice if there is a table with a link and a short description (I think this was part of the template). | Jorik van Kemenade (SURF) | |
| 7 | Table 1 (Section 8) | We list 2 options on the linked protocol pages. Should we add both options to this table? We are also referencing metadata standards, do they need to be included in Table 1? | Jorik van Kemenade (SURF) | |
| 8 | the PUSH workflow approach (Section 10) | This implies that there are a push and a pull workflow to choose from. However, I can't find any of the options in this document. Where can I find the push workflow and where can I find the alternatives? | Jorik van Kemenade (SURF) | |
| 9 | Figure 3: Zenodo (zenodo.org) since January 2022 (Section 10) | Figure is missing. | Jorik van Kemenade (SURF) | |
| 10 | Throughout the document | Both "data source" and "datasource" are used throughout the document. Unless we are naming something specifically a "datasource", the document should use one of these two | Paul Gondim van Dongen (SURF) | |
| 11 | Once the EOSC Data Source fulfills these IF guidelines (section 5) | I would rather see "adheres to" or "follows" instead of "fulfills" | Paul Gondim van Dongen (SURF) |