Welcome to the EOSC Future wiki!

IMPORTANT: Please be aware that this Wiki space is no longer actively maintained. The information in it applies to the discontinued EOSC Marketplace and Provider Portal, which have been replaced by the EOSC EU Node.
Information related to the EOSC EU Node is available via the official page <here>

TitleEOSC-IF / Interoperability Guideline: Research Product Deposition
URI

https://doi.org/10.5281/zenodo.8091896 (always link to latest version)

Revised version links

https://doi.org/10.5281/zenodo.8325671 (version 2.0)

https://doi.org/10.5281/zenodo.8091897 (version 1.0)
Link to MetadataN/A - onboarded via Provider Dashboard

Guideline id: 44a3bdcb3f778cfd413614a413d8744a

Date Issued to EIAC30.06.2023 (onboarded 28.06.2023)
Submitted by

Alessia Bardi representing the EOSC Future WP3 Working Group on Research product Publishing

Provider = OpenAIRE

Outcome of EIAC reviewno endorsement needed as community guideline
Date Issued to EIAB22.09.23
Outcome of EIAB review27.09.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)

Thanassis MantesATHENA RCSUPPORT
Sabeel Shah Bielefeld UniversitySupport
Andrea ManziEGI FoundationSupportjust one comment: on the last section is written 

"HAL and Episciences implemented the COAR Notify and Signposting protocols in production, while
other use cases, including the one between HAL and Peer Community In are planned to be
implemented by Summer 2023" maybe if there are updates after the summer on this they could be added





Comment/Change Log

Please fill in any comments or proposed changes below or add them as issues on the github repository.

Number

Current Text

Proposed Text / Query

Commenter

Action

1

page 3

Fig. 3.1 illustrates

Fig. 1 illustratesAndrea ManziFixed
2

page 5

Pull mode: COAR Notify + Signposting 

There is a duplication of text at the beginning of the Pull mode: COAR Notify + Signposting section. The 2 sentences are almost similar so one should be removed Andrea ManziFixed
3no commentsno commentsThanassis Mantes
4

Section 2, p 3

The integration ensures that outcomes of such services are deposited by the services, prior authorisation of the users, into a given repository, giving life to an end-to-end scientific workflow, from experimentation to publishing.



add "to":

...prior to authorisation of the users...

Sabeel ShahThanks to he reviewer's suggestion I understand that the sentence was not clear. Rewritten as "when authorised by the users"
5

Section 2, p 3

The limit of existing approaches is to be bound to a specific repository API and format; introducing multiple repositories as potential targets of deposition for the service, multiplies the problem, as bilateral interactions with the respective repository API must be established.

Its a complex sentence. Please consider splitting this sentence into at least two. It will make it easier to comprehend.

Suggested split is as follows:

The limit of existing approaches is to be bound to a specific repository API and format. To solve this limitation, introducing multiple repositories as potential targets of deposition for the service, actually multiplies the problem, because bilateral interactions with the additional respective repository API must be established.

Sabeel ShahSentence rewritten as follows: "The limit of existing approaches is to be bound to a specific repository API and format. Solving this limitation by introducing multiple repositories as potential targets of deposition for the service multiplies the problem, as bilateral interactions with the respective repository API must be established."
6

Section 2, p 3

  1. Scenario 1 - thematic service and deposition options
  1. Scenario 1 - Thematic service and deposition options


i.e. capitalize 'T'

Sabeel ShahFixed
7

Section 2, p 3

Scenario 3 - Automatic Open Access deposition from e-infra service

"e-infra": does it mean "infrastructure" ?Sabeel ShahI changed with e-infrastructure. The term is used to refer to digital, horizontal infrastructures. If there is a preferred term in the EOSC context, please let me known and I will update the text accordingly.





  • No labels

Privacy Policy