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: Access to content via PID
URI

https://doi.org/10.5281/zenodo.8091102 (DOI resolves to the latest version)

Revised version links

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

https://doi.org/10.5281/zenodo.8318608 (version 2.1)

Link to Metadata

N/A - onboarded via Provider Dashboard

ID: ff460c57aefd0fc215e0083ed86fc36e

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 reviewendorsed 05/09/2023
Date Issued to EIAB05/09/2023, 22/09/23
Outcome of EIAB reviewendorsed 29/09/2023
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 Uni BielefeldSupport
Andrea ManziEGI Foundation Support








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

1Minor changes and updates in curl examplesFormat curl text to be clearer (maybe use a table), add responses for each case, minor spelling  fixes (e.g 

curl-I curl-I
https://tore.tuhh.de/handle/11
420/14772
to get the Link with rel=”item”), comments on what to expect as a valid result for each call (link to an OpenAPI doc)

Thanassis Mantes, ATHENA RC
  • Added reference to curl manual
  • Used "easy code formatter" plugin for code formatting and highlighting
  • Decreased number of calls in examples by automatically following redirects since the beginning 
  • Added responses for every call with a brief description
  • Removed example from TORE CRIS because it does not support anymore the protocol.
2

page 3 

section 2

I would add references or explain here what is a DOI and HandleAndrea Manzi, EGI FoundationAdded references in footnotes
3

page 4

section 6

I would like to see details on thee SignPosting Publication Boundary Pattern implementation  via Linkset and HTTP Link Headers. There are some examples later, but i feel this info is needed in the guidelines.Andrea Manzi, EGI FoundationAdded description of the two options and references to the standard RFC9264
4Abstract
An important aspect of Open Science is the possibility to re-use existing research products (e.g. research data), deposited in repositories and accessible via their persistent identifiers (e.g. handle, doi, ark).		Should be capital: DOI, ARKSabeel ShahDone
5List of Abbreviationsadd DOI, RDF to this listSabeel ShahDone
6

Description and main features

... depending on the server and on the specific HTTP request: an HTML landing page, json-ld, RDF are some examples.

'and RDF'Sabeel ShahDone
7

Description and main features

.... but there is no standardise mechanism to get directly to the actual resource, ...

should be: standardisation mechanismSabeel ShahChanged to "standard mechanism" (standardisation mechanism has another meaning)
8

Description and main features

.... across servers and regardless the specific type of PID.

'of the'Sabeel ShahDone
  • No labels

Privacy Policy