Sharing of Project Data with the Research Community Sample Clauses

Sharing of Project Data with the Research Community. Awardee will share with the research community Project Data relevant to topics of interest to the research community, such as disease-specific assays, animal models, correlates of protection or diagnostics and epidemic preparedness mechanisms, as described in the IPDP and agreed in the JMAG, subject to the Awardee’s right, prior to such Project Data entering the public domain, (i) to remove Trade Secret Information and Confidential Information within Awardee Background IP, if any, included in such Project Data and (ii) in case there is any patentable subject matter included in such Project Data, to delay such Project Data entering the public domain for a reasonable period of time, not to exceed [***].
View SourceView Similar (2)
Sharing of Project Data with the Research Community. Awardee will share Project Data as described in the IPDP relevant to topics of interest to the research community, such as disease-specific assays, animal models, correlates of protection or diagnostics and epidemic preparedness mechanisms, subject to reasonable protection for Awardee’s rights under this Agreement.
View Source
Sharing of Project Data with the Research Community. Awardee will share with the research community Project Data relevant to topics of interest to the research community, such as disease-specific assays, animal models, correlates of protection or diagnostics and epidemic preparedness mechanisms, as described in the IPDP and agreed in the JMAG, subject to the Awardee’s right, prior to such Project Data entering the public ANNEX A: TERMS AND CONDITIONS domain, (i) to remove Trade Secret Information and Confidential Information within Awardee Background IP, if any, included in such Project Data and (ii) in case there is any patentable subject matter included in such Project Data, to delay such Project Data entering the public domain for a reasonable period of time, not to exceed [***].
View Source

Related to Sharing of Project Data with the Research Community

  • Project Information describing each Eligible Project that started, ended, or was ongoing in the reporting year.

  • Outside Activities of Limited Partners Subject to any agreements entered into by a Limited Partner or its Affiliates with the General Partner, Partnership or a Subsidiary, any Limited Partner and any officer, director, employee, agent, trustee, Affiliate or stockholder of any Limited Partner shall be entitled to and may have business interests and engage in business activities in addition to those relating to the Partnership, including business interests and activities in direct competition with the Partnership or that are enhanced by the activities of the Partnership. Neither the Partnership nor any Partners shall have any rights by virtue of this Agreement in any business ventures of any Limited Partner or Assignee. Subject to such agreements, none of the Limited Partners nor any other Person shall have any rights by virtue of this Agreement or the partnership relationship established hereby in any business ventures of any other Person, other than the Limited Partners benefiting from the business conducted by the General Partner, and such Person shall have no obligation pursuant to this Agreement to offer any interest in any such business ventures to the Partnership, any Limited Partner or any such other Person, even if such opportunity is of a character which, if presented to the Partnership, any Limited Partner or such other Person, could be taken by such Person.

  • Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.

  • Project Initiation i - Upon final execution of the Agreement with the DISTRICT, the ARCHITECT shall: ♦ Review the Program Management Plan (PMP) with the DISTRICT and its representatives to familiarize them with the proposed tasks and schedule and develop necessary modifications. The PMP defines the Program Master Schedule and Budgets and each Project scope and budget. ii - Within the first week following execution of the Agreement, meet with the DISTRICT and its representatives to prepare a detailed task analysis and work plan for documentation in a computer-generated project schedule. iii - This task analysis and work plan will identify specific tasks including, but not limited to: ♦ interviews, ♦ data collection ♦ analysis, ♦ report preparation, ♦ planning, ♦ Architectural programming, concepts and schematic design preparation and estimating that are part of the work of the Project. Also identified will be milestone activities or dates, specific task responsibilities, required completion times necessary for the review and approval by the DISTRICT and by all regulatory agencies and additional definition of deliverables. iv - Participate in a general Project kick-off meeting to include the ARCHITECT, appropriate sub-consultants, and DISTRICT staff. v - The project kick-off meeting will introduce key team members from the DISTRICT and the ARCHITECT to each other, defining roles and responsibilities relative to the Project. vi - Identify and review pertinent information and/or documentation necessary from the DISTRICT for the completion of the Project. vii - Review and explain the overall project goals, general approach, tasks, work plan and procedures and deliverable products of the Project. viii - Review and explain the task analysis and Project work plan for all parties present; determine any adjustments or fine tuning that needs to be made to the work plan. ix - Review documentation of the Project kick-off meeting prepared by the DISTRICT’S representative and comment prior to distribution. x - Base Drawings and Site Survey Information

  • 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.