- Last updated on .
What legal issues arise when working with research data?
Have you ever wondered how you can protect your research data or how you can licence them? What about when re-using someone else’s research data? Are there any risks if you don’t use a license?
OpenAIRE can help you answer all these questions!
We have just published the first version of our brand new Guides that can help you understand various legal issues and offer you solutions.
Guides on research data and legal issues
These guides are part of the user guide on Copyright, Open Science and Data, offering a state-of-the-art, legally advanced, manageable set of rules, guidelines and resources, with a view to addressing copyright and related rights issues.
When describing the OpenAIRE Infrastructure Service Level Agreements (SLAs) we refer to the levels of availability, serviceability, performance, operation, or other attributes of the Infrastructure. The level of service is speciﬁed as "target" and "minimum," which allows the user of the OpenAIRE Infrastructure to be informed what to expect (the minimum), while providing a measurable (average) target value that shows the level of organization performance.
The following OpenAIRE Infrastructure SLAs have been deﬁned:
The OpenAIRE APIs provide access to a graph of interlinked metadata records and to a corpus of article PDFs. While metadata records are accessible as CC-BY, access to PDFs may only take place on request and is subject to restrictions based on the content providers.
If Users create technology that works with OpenAIRE API Services, they must comply with the current technical documentation applicable to the used OpenAIRE Services available at http://develop.openaire.eu.
All API services are running in production on a best effort basis, targeting 24/7, within the OpenAIRE infrastructure premises deployed at the data center facilities of the Interdisciplinary Centre for Mathematical and Computational Modelling (ICM) - Data center facilities at ICM, Poland.
Users may submit two kinds of information to the OpenAIRE infrastructure: personal sign in information or claims, intended as assertions of associations between research products (publications, datasets, software, other products) and between research products and research projects or research communities.
The OpenAIRE Infrastructure will make reasonable efforts to ensure that data are persisted. In the event of hardware or software failures caused by failures to a hard drive or power supply, the OpenAIRE Infrastructure will make reasonable attempts to restore the user's data. No guarantee whatsoever is provided on the success of any User's data recovery.
Content providers submit two kinds of information to the OpenARE infrastructure: personal/organizational sign in information and operational information to access their metadata and full-texts.
The OpenAIRE Infrastructure will make reasonable efforts to ensure that data are persisted. In the event of hardware or software failures caused by failures to a hard drive or power supply, the OpenAIRE Infrastructure will make reasonable attempts to restore the Content provider’s data. No guarantee whatsoever is provided on the success of any Content provider’s data recovery.
OpenAIRE may offer applications as-a-service (e.g. aggregators and brokers), whereas external organizations operate/administrate instances of OpenAIRE services hosted by the OpenAIRE infrastructure. Once deployed, such instances will deliver a best effort uptime as monitored within the OpenAIRE Infrastructure monitoring system. The following holds:
The Production System Support Team (ISTI-CNR, Italy - ICM, Poland) is responsible for the resolution of all production support requests related to the OpenAIRE production system. This SLA covers incident tickets in the case of issue related to infrastructure incidents (e.g. it does not cover the resolution time of the issues coming from software bugs). In case of incident, a reply time of at most 1 business day is ensured, including the initiation of a resolution procedure. The resolution time may depend on the specific incident (e.g. on warranty terms from hardware suppliers, which are generally longer than 1 day).
For more, please read D9.2 - Infrastructure Policies