Data entry Literature interpretation and data entry Sample Clauses

Data entry Literature interpretation and data entry. For the purpose of a harmonized data entry from peer reviewed literature by all partners a training was organized. The training elaborated on the structure of the database, the entry-tool and the interpretation of fields in the entry tool. Six persons from different WP6 partners institutes participated in this training. During the project the persons receiving the training were not always able to continue the work. It turned out to be difficult to transfer the knowledge of the person that received the training to these new persons. Feedback at the end project showed that each individual should receive proper training for data entry. With the help of the training and the guidance trained people are able to interpret literature for data entry. It turned out that a high level of expertise in the field of nanomaterial characterization, toxicology or ecotoxicology is necessary to interpret the literature and extract the essential information. Minimum requirement/ data completeness It is essential to set the minimum requirements of the level of completeness of the data depending on the purpose of its use. Two factors are important: - What is the minimum data that is needed to properly interpret the results of a given experiment considering the goal of the data collection. - Which contextual can be added via a reference document. For modelling purposes not always all data needs to be stored in a structured fashion. It is worthwhile to investigate beforehand which data are essential to be stored in a harmonized and structured way and which data can be added via a reference document or otherwise. Data entry of the literature was a time consuming process due to the high level of detail that was required in the entry tool. In current and future projects experts on various assay are asked to provide what the essential data is that is needed to interpret experimental results. The final set of minimum required information should be defined in a dialog between experts on the specific assays and experts on the database structure and purpose of the data collection.
AutoNDA by SimpleDocs

Related to Data entry Literature interpretation and data entry

  • Review of legality and data minimisation (a) The data importer agrees to review the legality of the request for disclosure, in particular whether it remains within the powers granted to the requesting public authority, and to challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful under the laws of the country of destination, applicable obligations under international law and principles of international comity. The data importer shall, under the same conditions, pursue possibilities of appeal. When challenging a request, the data importer shall seek interim measures with a view to suspending the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the personal data requested until required to do so under the applicable procedural rules. These requirements are without prejudice to the obligations of the data importer under Clause 14(e).

  • Data Security and Unauthorized Data Release The Requester and Approved Users, including the Requester’s IT Director, acknowledge NIH’s expectation that they have reviewed and agree to manage the requested controlled-access dataset(s) and any Data Derivatives of controlled-access datasets according to NIH’s expectations set forth in the current NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy and the Requester’s IT security requirements and policies. The Requester, including the Requester’s IT Director, agree that the Requester’s IT security requirements and policies are sufficient to protect the confidentiality and integrity of the NIH controlled-access data entrusted to the Requester. If approved by NIH to use cloud computing for the proposed research project, as outlined in the Research and Cloud Computing Use Statements of the Data Access Request, the Requester acknowledges that the IT Director has reviewed and understands the cloud computing guidelines in the NIH Security Best Practices for Controlled-Access Data Subject to the NIH GDS Policy. The Requester and PI agree to notify the appropriate DAC(s) of any unauthorized data sharing, breaches of data security, or inadvertent data releases that may compromise data confidentiality within 24 hours of when the incident is identified. As permitted by law, notifications should include any known information regarding the incident and a general description of the activities or process in place to define and remediate the situation fully. Within 3 business days of the DAC notification, the Requester agrees to submit to the DAC(s) a detailed written report including the date and nature of the event, actions taken or to be taken to remediate the issue(s), and plans or processes developed to prevent further problems, including specific information on timelines anticipated for action. The Requester agrees to provide documentation verifying that the remediation plans have been implemented. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. All notifications and written reports of data security incidents and policy compliance violations should be sent to the DAC(s) indicated in the Addendum to this Agreement. NIH, or another entity designated by NIH may, as permitted by law, also investigate any data security incident or policy violation. Approved Users and their associates agree to support such investigations and provide information, within the limits of applicable local, state, tribal, and federal laws and regulations. In addition, Requester and Approved Users agree to work with the NIH to assure that plans and procedures that are developed to address identified problems are mutually acceptable and consistent with applicable law.

  • Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.

  • Procurement of Recovered Materials (1) In the performance of this contract, the Contractor shall make maximum use of products containing recovered materials that are EPA-designated items unless the product cannot be acquired

  • Your Billing Rights: Keep This Document For Future Use This notice tells you about your rights and our responsibilities under the Fair Credit Billing Act.

  • Certification Regarding Entire TIPS Agreement for Part 1 and Part 2 Contracts 5 This is a two part solicitation. Part 1 is solicited for TIPS sales that are not considered a "public work" construction project. Part 1 permits the sale of goods and non-construction/non-"public work" services such as maintenance and minor repairs. Part 2 Job Order Contract (JOC) is solicited for projects considered by your TIPS Member Customers to be a "public work" construction project. The determination of whether or not a TIPS sale amounts to a "public work" construction project requiring a Part 2 JOC contract is made by the TIPS Member Customer at the time of each TIPS sale. Thus, Vendors are encouraged to respond to both Parts 1 and 2 in case your TIPS Member Customers require that a sale be made under one Part or the other. However, responding to both Parts is not required. If Vendor responds and is awarded to both Parts, Vendor will have one contract for Part 1 and a separate contract for Part 2.

  • Use of Attachment Facilities by Third Parties Purpose of Attachment Facilities.‌‌ Except as may be required by Applicable Laws and Regulations, or as otherwise agreed to among the Parties, the Attachment Facilities shall be constructed for the sole purpose of interconnecting the Large Generating Facility to the New York State Transmission System and shall be used for no other purpose.

  • CONTRACTOR STAFF WITHIN AUTHORIZED USER AGREEMENT The provisions of this section shall apply unless otherwise agreed in the Authorized User Agreement. All employees of the Contractor, or of its Subcontractors, who shall perform under an Authorized User Agreement, shall possess the necessary qualifications, training, licenses, and permits as may be required within the jurisdiction where the Services specified are to be provided or performed, and shall be legally entitled to work in such jurisdiction. All Business Entities that perform Services under the Contract on behalf of Contractor shall, in performing the Services, comply with all applicable Federal, State, and local laws concerning employment in the United States. Staffing Changes within Authorized User Agreement

  • Data Return and Destruction of Data (a) Protecting PII from unauthorized access and disclosure is of the utmost importance to the EA, and Contractor agrees that it is prohibited from retaining PII or continued access to PII or any copy, summary or extract of PII, on any storage medium (including, without limitation, in secure data centers and/or cloud-based facilities) whatsoever beyond the period of providing Services to the EA, unless such retention is either expressly authorized for a prescribed period by the Service Agreement or other written agreement between the Parties, or expressly requested by the EA for purposes of facilitating the transfer of PII to the EA or expressly required by law. As applicable, upon expiration or termination of the Service Agreement, Contractor shall transfer PII, in a format agreed to by the Parties to the EA.

  • Local Interconnection Data Exchange for Billing 7.7.1 There are certain types of calls or types of Interconnection that require exchange of Billing records between the Parties, including, for example, alternate billed and Toll Free Service calls. The Parties agree that all call types must be routed between the networks, accounted for, and settled among the Parties. Certain calls will be handled via the Parties' respective operator service platforms. The Parties agree to utilize, where possible and appropriate, existing accounting and settlement systems to xxxx, exchange records and settle revenue.

Time is Money Join Law Insider Premium to draft better contracts faster.