You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The guidelines places various requirements on an OAI-PMH endpoint before the information will be accepted. It would be helpful if there was an automated way to check if an endpoint conforms with these requirements.
For example, this could be some online service that would make various requests against the OAI-PMH endpoint and provide a report of the compliance of the service's replies.
Alternatively, it could be a program/script that the OAI-PMH service operators could run (locally). This would similarly make various requests and check the responses are conforming to the guidelines, identifying any problems.
The text was updated successfully, but these errors were encountered:
In the OpenAIRE PROVIDE Dashboard we have the metadata validator for the repository managers where they can check whether they are compliant with the OpenAIRE Guidelines. OpenAIRE is and aggregator where data sources comply with the OpenAIRE Guidelines to be able to be incorporated into the OpenAIRE Graph. Apart from the authoritative data sources that OpenAIRE aggregates into the OpenAIRE Graph every other institutional repository or Open Access Journal that wants to be aggregated should comply with the OpenAIRE Guidelines.
The Metadata Validator will soon be available also as a standalone service.
The guidelines places various requirements on an OAI-PMH endpoint before the information will be accepted. It would be helpful if there was an automated way to check if an endpoint conforms with these requirements.
For example, this could be some online service that would make various requests against the OAI-PMH endpoint and provide a report of the compliance of the service's replies.
Alternatively, it could be a program/script that the OAI-PMH service operators could run (locally). This would similarly make various requests and check the responses are conforming to the guidelines, identifying any problems.
The text was updated successfully, but these errors were encountered: