RESEARCH DATA STORAGE AND PRESERVATION Sample Clauses

RESEARCH DATA STORAGE AND PRESERVATION. 3.1. Data organization and labelling a) Chemical data and procedures followed. These will be linked with the lab notebook number and page number where details of the experiment are recorded (likewise, file names/locations of analytical readings will also be recorded in lab notebooks to allow electronic records to be easily linked to the raw data); b) A PowerPoint report with details of all the analysis performed for each experiment and main results obtained, including on which instrument, which student(s) were in control of the experiment, exact dates, and directories on computers where the raw data is stored to allow the corresponding raw data records to be easily found; c) Published references related to the experiment. Files and folders will have an appropriately descriptive title/name. As QuIET is a large project involving large research institutions and well-established teams which already have advanced data-policies, workflows and naming conventions established, it is not reasonable to apply a one-model-fits-all approach. Therefore, all partners have come to an agreement to use a set of essential minimum information (Including project, WP, date, institution, experiment description) which shall ensure cross platform coherence. The final datasets decided to be deposited in the chosen data repository (see details in section 4) will also be accompanied by a README file listing the contents of the files and outlining the structure and file-naming convention used for potential users to easily understand the database itself. In such way, we will ensure a high quality, standardized and traceable workflow throughout the data generation process complying with the Findable and Interoperable principles of the EC for data management1. For Accessibility, Use and Re-use, please refer to section 4 of this document.
AutoNDA by SimpleDocs

Related to RESEARCH DATA STORAGE AND PRESERVATION

  • Research Use The Requester agrees that if access is approved, (1) the PI named in the DAR and (2) those named in the “Senior/Key Person Profile” section of the DAR, including the Information Technology Director and any trainee, employee, or contractor1 working on the proposed research project under the direct oversight of these individuals, shall become Approved Users of the requested dataset(s). Research use will occur solely in connection with the approved research project described in the DAR, which includes a 1-2 paragraph description of the proposed research (i.e., a Research Use Statement). Investigators interested in using Cloud Computing for data storage and analysis must request permission to use Cloud Computing in the DAR and identify the Cloud Service Provider (CSP) or providers and/or Private Cloud System (PCS) that they propose to use. They must also submit a Cloud Computing Use Statement as part of the DAR that describes the type of service and how it will be used to carry out the proposed research as described in the Research Use Statement. If the Approved Users plan to collaborate with investigators outside the Requester, the investigators at each external site must submit an independent DAR using the same project title and Research Use Statement, and if using the cloud, Cloud Computing Use Statement. New uses of these data outside those described in the DAR will require submission of a new DAR; modifications to the research project will require submission of an amendment to this application (e.g., adding or deleting Requester Collaborators from the Requester, adding datasets to an approved project). Access to the requested dataset(s) is granted for a period of one (1) year, with the option to renew access or close-out a project at the end of that year. Submitting Investigator(s), or their collaborators, who provided the data or samples used to generate controlled-access datasets subject to the NIH GDS Policy and who have Institutional Review Board (IRB) approval and who meet any other study specific terms of access, are exempt from the limitation on the scope of the research use as defined in the DAR.

  • The Web Services E-Verify Employer Agent agrees to, consistent with applicable laws, regulations, and policies, commit sufficient personnel and resources to meet the requirements of this MOU.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • XXX Hosting 10.1 XXX Hosting is not required for resale in the BellSouth region.

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • Technology Access Contractor expressly acknowledges that state funds may not be expended in connection with the purchase of an automated information system unless that system meets certain statutory requirements relating to accessibility by persons with visual impairments. Accordingly, Contractor represents and warrants to System Agency that the technology provided to System Agency for purchase (if applicable under this Contract or any related Solicitation) is capable, either by virtue of features included within the technology or because it is readily adaptable by use with other technology, of: • providing equivalent access for effective use by both visual and non-visual means; • presenting information, including prompts used for interactive communications, in formats intended for non-visual use; and • being integrated into networks for obtaining, retrieving, and disseminating information used by individuals who are not blind or visually impaired. For purposes of this Section, the phrase “equivalent access” means a substantially similar ability to communicate with or make use of the technology, either directly by features incorporated within the technology or by other reasonable means such as assistive devices or services which would constitute reasonable accommodations under the Americans With Disabilities Act or similar state or federal laws. Examples of methods by which equivalent access may be provided include, but are not limited to, keyboard alternatives to mouse commands and other means of navigating graphical displays, and customizable display appearance. In accordance with Section 2157.005 of the Texas Government Code, the Technology Access Clause contract provision remains in effect for any contract entered into before September 1, 2006.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

  • Registry Interoperability and Continuity Registry Operator shall comply with the Registry Interoperability and Continuity Specifications as set forth in Specification 6 attached hereto (“Specification 6”).

  • Information Technology The following applies to all contracts for information technology commodities and contractual services. “Information technology” is defined in section 287.012(15), F.S., to have the same meaning as provided in section 282.0041, F.S.

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

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