We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Making data openly accessible Sample Clauses

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.
Sample 1
AutoNDA by SimpleDocs
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.
Sample 1
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 ...
Sample 1
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.
Sample 1
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 (xxxxxxxxxxxxxxx.xx) 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...
Sample 1
Making data openly accessible 
Sample 1

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.

  • Electronic and Information Resources Accessibility and Security Standards a. Applicability: The following Electronic and Information Resources (“EIR”) requirements apply to the Contract because the Grantee performs services that include EIR that the System Agency's employees are required or permitted to access or members of the public are required or permitted to access. This Section does not apply to incidental uses of EIR in the performance of the Agreement, unless the Parties agree that the EIR will become property of the State of Texas or will be used by HHSC’s clients or recipients after completion of the Agreement. Nothing in this section is intended to prescribe the use of particular designs or technologies or to prevent the use of alternative technologies, provided they result in substantially equivalent or greater access to and use of a Product.

  • Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, MyLineToo must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • Information Access Each Party (“Disclosing Party”) shall make available to another Party (“Requesting Party”) information that is in the possession of the Disclosing Party and is necessary in order for the Requesting Party to: (i) verify the costs incurred by the Disclosing Party for which the Requesting Party is responsible under this Agreement; and (ii) carry out its obligations and responsibilities under this Agreement. The Parties shall not use such information for purposes other than those set forth in this Article 25.1 of this Agreement and to enforce their rights under this Agreement.

  • Transmission and Routing of Exchange Access Traffic PURSUANT TO 251(c)(2) 13 ARTICLE VI MEET-POINT BILLING ARRANGEMENTS 14 ARTICLE VII BLV/BLVI TRAFFIC 16 7.1 Busy Line Verification 16 7.2 Busy Line Verification Interrupt 16 7.3 BLV/BLVI Traffic 16 7.4 BLV/BLVI Compensation 16

  • Review Systems; Personnel It will maintain business process management and/or other systems necessary to ensure that it can perform each Test and, on execution of this Agreement, will load each Test into these systems. The Asset Representations Reviewer will ensure that these systems allow for each Review Receivable and the related Review Materials to be individually tracked and stored as contemplated by this Agreement. The Asset Representations Reviewer will maintain adequate staff that is properly trained to conduct Reviews as required by this Agreement.

  • Metering Data At Developer’s expense, the metered data shall be telemetered to one or more locations designated by Connecting Transmission Owner, Developer and NYISO. Such telemetered data shall be used, under normal operating conditions, as the official measurement of the amount of energy delivered from the Large Generating Facility to the Point of Interconnection.

  • Access to Protected Information If BA maintains a designated record set on behalf of CE, BA shall make Protected Information maintained by BA or its agents or subcontractors in Designated Record Sets available to CE for inspection and copying within five (5) days of a request by CE to enable CE to fulfill its obligations under state law [Health and Safety Code Section 123110] and the Privacy Rule, including, but not limited to, 45 C.F.R. Section 164.524 [45 C.F.R. Section 164.504(e)(2)(ii)(E)]. If BA maintains Protected Information in electronic format, BA shall provide such information in electronic format as necessary to enable CE to fulfill its obligations under the HITECH Act and HIPAA Regulations, including, but not limited to, 42 U.S.C. Section 17935(e) and 45 C.F.R. Section 164.524.

  • Contracting Information Requirements Contractor represents and warrants that it will comply with the requirements of Section 552.372(a) of the Texas Government Code. Except as provided by Section 552.374(c) of the Texas Government Code, the requirements of Subchapter J (Additional Provisions Related to Contracting Information), Chapter 552 of the Government Code, may apply to the Contract and the Contractor agrees that the Contract can be terminated if the Contractor knowingly or intentionally fails to comply with a requirement of that subchapter.

  • Links to Third Party Websites In your use of the Service and/or the Company’s website, you may encounter various types of links that enable you to visit websites operated or owned by third parties (“Third Party Site”). These links are provided to you as a convenience and are not under the control or ownership of the Company. The inclusion of any link to a Third Party Site is not (i) an endorsement by the Company of the Third Party Site, (ii) an acknowledgement of any affiliation with its operators or owners, or (iii) a warranty of any type regarding any information or offer on the Third Party Site. Your use of any Third Party Site is governed by the various legal agreements and policies posted at that website.

Most Referenced Clauses

Most Referenced Definitions

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!