Making data openly accessible Clause Samples

Making data openly accessible.  The only data which de-facto will not be made openly accessible will be data which contains personally identifiable information (e.g. individual evaluation forms). These will be summarised, and any individual forms used for research publications (such as inclusion in ‘user stories’) will be redacted or anonymised before online storage. In addition, datasets, measurements, codes that are IP restricted as per the CA will not be made available in full, but the consortium will strive to make meaningful parts of these available for reproducibility. We will also strive to keep such restricted data to a minimum.  During the project, a subset of summary data (e.g. event visitor statistics and feedback summaries) will be made accessible by one or more methods below: - Via newsletters, reports and other publications on the online knowledge sharing platform (▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇.▇▇) developed as part of WP3; - Via partner’s local websites; - Via social media; - The PAINLESS website will provide open-access to the summer-schools pro- ceedings ensuring a wide spread of the results and an increased awareness of the excellence of the PAINLESS network; - The project’s journal/magazine articles will be made available to the wide public through open access and self-archiving, such as ArXiv, OpenAir, IEEE Open Access, and we will pursue open access publication venues.  Detailed data will be available to all consortium partners via the project shared drive (with the exception of individual questionnaires which will be stored at each partner’s premises). The access to this drive is restricted to project part- ners. Should other individuals wish to access the data for research purposes during the project, it will be openly shared on request. At the end of the pro- ject, data to be preserved will be stored in a suitable data repository. At this stage, we are using Microsoft Sharepoint.  Data will be published using standard file formats (pdf, csv and others).  With the exception of the knowledge sharing platform, all data will be accessed using standard tools. It is the responsibility of the Beneficiaries to provide ap- propriate documentation to make measurement results and software readily accessible and reusable.  A relevant software is not seen as being a requirement, but should it be need- ed, we will provide the required open source to access and analyse the data, such as codes implementing our algorithmic solutions, or measurement/test results.  For the duration of the...
View Source
Making data openly accessible. ‌ As part of the ORDP, the aim of BEACONING is to make as much research data as possible openly accessible for third parties to enhance the progress and speed of research. The BEACONING consortium will use the green open access route, meaning that the project members will take care of granting open access to their publications via an online repository [1]. As described in the H2020 Programme Guidelines [1], the publications must be deposited in an online repository not later than the day the scientific article is officially published (Please see the "Guidelines on FAIR Data Management in Horizon 2020" [1] for data format regulations). The BEACONING consortium will use one repository for all their publications: ZENODO. It can be reached by following this URL: The benefit of this repository is that it comprises a holistic way to deposit scientific publications, as well as research data in one place. Data which is needed to validate the scientific publications will also be deposited in ZENODO at the date the article is published at the latest.
View Source
Making data openly accessible. It is not in the intentions of the BOUNCE project to make data openly accessible. Only project public deliverables will be made publically available and accessible for download through the web page of the project.
View Source
Making data openly accessible. The Day to Day DST will be re-usable and freely accessible to the public beyond the end of the project if someone runs it. The analysis from the DST will be made openly accessible. All project related data, as well as the code and the documentation will be long term stored on the Consist server.
View Source
Making data openly accessible. Each partner must ensure open access (free of charge online access for any user) to all peer- reviewed scientific publications relating to its results. Results are owned by the partner that generates them. ‘Results’ means any (tangible or intangible) output of the action such as data, knowledge or information — whatever its form or nature, whether it can be protected or not — that is generated in the action, as well as any rights attached to it, including intellectual property rights. Apart from the data sets specified that will be made open (public), other data generated in CarE-Service project should be kept confidential to avoid jeopardising future exploitation. All the partners must disseminate its results by disclosing them to the public by appropriate means, as soon as possible (other than those resulting from protecting or exploiting the results), including in scientific publications (in any medium). A partner that intends to disseminate its results must give to the other partners at least 45 days advance notice, together with sufficient information on the results it will disseminate (Article 29.1, Grant Agreement). The data will be made available to the public in order to improve and maximize access to and re-use of research data generated by the CarE-Service project. Therefore, all the generated data should be deposited in the Zenodo depository platform (a free repository hosted by CERN and available to all), which allows researchers to deposit both publications and data, in line with Article 29.3 of the Grant Agreement. On Zenodo, all research outputs from all fields of science are welcome. In the upload form, the uploader chooses between types of files: publications (book, book section, conference paper, journal article, patent, preprint, report, thesis, technical note, working paper, etc.), posters, presentations, datasets, images (figures, plots, drawings, diagrams, photos), software, videos/audio and interactive materials such as lessons. All metadata is stored internally in JSON-format according to a defined JSON schema. Metadata is exported in several standard formats such as MARCXML, Dublin Core, and DataCite Metadata Schema (according to the OpenAIRE Guidelines). Files may be deposited under closed, open, or embargoed access. Files deposited under closed access are protected against unauthorized access at all levels. Access to metadata and data files is provided over standard protocols such as HTTP and OAI-PMH. Metadata is licensed under ...
View Source
Making data openly accessible 
View Source

Related to Making data openly accessible

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

  • Access to Records; Contractor Financial Records Contractor agrees that District and its authorized representatives are entitled to review all Contractor books, documents, papers, plans, and records, electronic or otherwise (“Records”), directly pertinent to this Contract for the purpose of making audit, examination, excerpts, and transcripts.

  • DISCLOSURE OF TBS ACCESS CODE TO THIRD PARTY (a) The Account Holder must exercise all care to ensure that the TBS Access Code is not disclosed to any person and shall take all steps to prevent forgery or fraud in connection with the use of his TBS Access Code and/or the operation of the TBS. If the TBS Access Code is disclosed to any person, the Account Holder must forthwith give the Bank written notice thereof, thereupon the Account Holder shall immediately cease to use the TBS Access Code. (b) Unless and until the Bank receives such written notice of disclosure, the Account Holder shall be fully liable and be bound by all transactions effected by the use of such TBS, with or without his consent or knowledge.

  • Verizon OSS Information 8.5.1 Subject to the provisions of this Section 8 and Applicable Law, Verizon grants to Reconex a non-exclusive license to use Verizon OSS Information. 8.5.2 All Verizon OSS Information shall at all times remain the property of Verizon. Except as expressly stated in this Section 8, Reconex shall acquire no rights in or to any Verizon OSS Information. 8.5.2.1 The provisions of this Section 8.5.2 shall apply to all Verizon OSS Information, except (a) Reconex Usage Information, (b) CPNI of Reconex, and (c) CPNI of a Verizon Customer or a Reconex Customer, to the extent the Customer has authorized Reconex to use the Customer Information. 8.5.2.2 Verizon OSS Information may be accessed and used by Reconex only to provide Telecommunications Services to Reconex Customers. 8.5.2.3 Reconex shall treat Verizon OSS Information that is designated by Verizon, through written or electronic notice (including, but not limited to, through the Verizon OSS Services), as “Confidential” or “Proprietary” as Confidential Information of Verizon pursuant to Section 10 of the Agreement. 8.5.2.4 Except as expressly stated in this Section 8, this Agreement does not grant to Reconex any right or license to grant sublicenses to other persons, or permission to other persons (except Reconex’s employees, agents or contractors, in accordance with Section 8.5.2.5 below, to access, use or disclose Verizon OSS Information. 8.5.2.5 Reconex’s employees, agents and contractors may access, use and disclose Verizon OSS Information only to the extent necessary for Reconex’s access to, and use and disclosure of, Verizon OSS Information permitted by this Section 8. Any access to, or use or disclosure of, Verizon OSS Information by Reconex’s employees, agents or contractors, shall be subject to the provisions of this Agreement, including, but not limited to, Section 10 of the Agreement and Section 8.5.2.3 above. 8.5.2.6 Reconex’s license to use Verizon OSS Information shall expire upon the earliest of: (a) the time when the Verizon OSS Information is no longer needed by Reconex to provide Telecommunications Services to Reconex Customers; (b) termination of the license in accordance with this Section 8; or (c) expiration or termination of the Agreement. 8.5.2.7 All Verizon OSS Information received by Reconex shall be destroyed or returned by Reconex to Verizon, upon expiration, suspension or termination of the license to use such Verizon OSS Information. 8.5.3 Unless sooner terminated or suspended in accordance with the Agreement or this Section 8 (including, but not limited to, Section 2.2 of the Agreement and Section 8.6.1 below), Reconex’s access to Verizon OSS Information through Verizon OSS Services shall terminate upon the expiration or termination of the Agreement. 8.5.3.1 Verizon shall have the right (but not the obligation) to audit Reconex to ascertain whether Reconex is complying with the requirements of Applicable Law and this Agreement with regard to Reconex’s access to, and use and disclosure of, Verizon OSS Information. 8.5.3.2 Without in any way limiting any other rights Verizon may have under the Agreement or Applicable Law, Verizon shall have the right (but not the obligation) to monitor Reconex’s access to and use of Verizon OSS Information which is made available by Verizon to Reconex pursuant to this Agreement, to ascertain whether Reconex is complying with the requirements of Applicable Law and this Agreement, with regard to Reconex’s access to, and use and disclosure of, such Verizon OSS Information. The foregoing right shall include, but not be limited to, the right (but not the obligation) to electronically monitor Reconex’s access to and use of Verizon OSS Information which is made available by Verizon to Reconex through Verizon OSS Facilities. 8.5.3.3 Information obtained by Verizon pursuant to this Section 8.5.3.3 shall be treated by Verizon as Confidential Information of Reconex pursuant to Section 10 of the Agreement; provided that, Verizon shall have the right (but not the obligation) to use and disclose information obtained by Verizon pursuant to this Section 8.5.3.3 to enforce Verizon’s rights under the Agreement or Applicable Law.

  • Data Access Control Persons entitled to use data processing systems gain access only to the Personal Data that they have a right to access, and Personal Data must not be read, copied, modified or removed without authorization in the course of processing, use and storage.