ACAP activities at RFMO meetings Sample Clauses

ACAP activities at RFMO meetings. The Agreement has four tuna RFMO Coordinators: Xxxxx Xxxxxxxxx - International Commission for the Conservation of Atlantic Tuna (ICCAT); Xxxxx Xxxxx - Indian Ocean Tuna Commission (IOTC), Xxxxx Xxxxxx - Inter-American Tropical Tuna Commission (IATTC); and Xxxxxx Xxxxxxxx - Western and Central Pacific Fisheries Commission (WCPFC). Both Xxxxx Xxxxx and Xxxxxx Xxxxxxxx cover the Commission for the Conservation of Southern Bluefin Tuna (CCSBT). The tRFMO Coordinators have provided reports on progress made in the tuna RFMOs over the past year (SBWG-4 Docs 47-53). The Working Group noted the significant progress made over the past year by several of the tuna RFMOs and thanked the tuna RFMO Coordinators for their work in progressing ACAP's work in these fora. The Working Group also expressed its appreciation to Xx Xxxx Xxxxx of BirdLife International for her ongoing contribution to this work and to France for its voluntary contribution which has allowed this work to be undertaken. Following advice from the RFMO Coordinators on the possibility of advancing ACAP's objectives in the tuna RFMOs over the coming year, the Working Group prioritised actions to be taken in the tuna RFMOs. It was agreed that the two-column approach used in most tuna RFMO seabird conservation measures no longer reflects best practice advice, given the results of recent research on bycatch mitigation measures. In view of the significant advances made recently in mitigation research the Working Group decided that additional resources should be devoted to achieving changes in the tuna RFMOs to ensure conservation measures reflect current best practice. It was agreed that priority should be given to affecting changes in conservation measures in the ICCAT and IOTC tuna RFMOs in 2011, with priority moving to the other tuna RFMOs in subsequent years. To achieve these changes it was recognised that more work would be required to liaise with relevant stakeholders and to prepare meetings documents etc. As the capacity of the tuna RFMO Coordinators was already stretched it was agreed that additional resources in the order of $30,000 a year should be sought to provide the capacity to undertake this work. In relation to advancing acceptance of line weighting within tuna RFMOs it was noted that definitive research findings should be made available on the safety of line-weighting techniques. Without this evidence, it will be very difficult to gain support for the adoption of this mitigation measure in som...
Sample 1
AutoNDA by SimpleDocs

Related to ACAP activities at RFMO meetings

  • Contract Negotiation Meetings 14.09 When operational requirements permit, the Employer will grant leave without pay to an employee for the purpose of attending contract negotiation meetings on behalf of the Alliance. Preparatory Contract Negotiation Meetings

  • Requester and Approved User Responsibilities The Requester agrees through the submission of the DAR that the PI named has reviewed and understands the principles for responsible research use and data management of the genomic datasets as defined in the NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy. The Requester and Approved Users further acknowledge that they are responsible for ensuring that all uses of the data are consistent with national, tribal, and state laws and regulations, as appropriate, as well as relevant institutional policies and procedures for managing sensitive genomic and phenotypic data. The Requester certifies that the PI is in good standing (i.e., no known sanctions) with the institution, relevant funding agencies, and regulatory agencies and is eligible to conduct independent research (i.e., is not a postdoctoral fellow, student, or trainee). The Requester and any Approved Users may use the dataset(s) only in accordance with the parameters described on the study page and in the 1 If contractor services are to be utilized, PI requesting the data must provide a brief description of the services that the contractor will perform for the PI (e.g., data cleaning services) in the research use statement of the DAR. Additionally, the Key Personnel section of the DAR must include the name of the contractor’s employee(s) who will conduct the work. These requirements apply whether the contractor carries out the work at the PI’s facility or at the contractor’s facility. In addition, the PI is expected to include in any contract agreement requirements to ensure that any of the contractor’s employees who have access to the data adhere to the NIH GDS Policy, this Data Use Certification Agreement, and the NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy. Note that any scientific collaborators, including contractors, who are not at the Requester must submit their own DAR. Addendum to this Agreement for the appropriate research use, as well as any limitations on such use, of the dataset(s), as described in the DAR, and as required by law. Through the submission of this DAR, the Requester and Approved Users acknowledge receiving and reviewing a copy of the Addendum which includes Data Use Limitation(s) for each dataset requested. The Requester and Approved Users agree to comply with the terms listed in the Addendum. Through submission of the DAR, the PI and Requester agree to submit a Project Renewal or Project Close-out prior to the expiration date of the one (1) year data access period. The PI also agrees to submit an annual Progress Update prior to the one (1) year anniversary2 of the project, as described under Research Use Reporting (Term 10) below. By approving and submitting the attached DAR, the Institutional Signing Official provides assurance that relevant institutional policies and applicable local, state, tribal, and federal laws and regulations, as applicable, have been followed, including IRB approval, if required. Approved Users may be required to have IRB approval if they have access to personal identifying information for research participants in the original study at their institution, or through their collaborators. The Institutional Signing Official also assures, through the approval of the DAR, that other institutional departments with relevant authorities (e.g., those overseeing human subjects research, information technology, technology transfer) have reviewed the relevant sections of the NIH GDS Policy and the associated procedures and are in agreement with the principles defined. The Requester acknowledges that controlled-access datasets subject to the NIH GDS Policy may be updated to exclude or include additional information. Unless otherwise indicated, all statements herein are presumed to be true and applicable to the access and use of all versions of these datasets.

  • Contract Negotiations Meetings Where operational requirements permit, the Employer will grant leave without pay to an employee for the purpose of attending contract negotiations meetings on behalf of the Institute.

  • Faculty Meetings Principals shall have the authority to schedule necessary faculty meetings; however, such meetings shall be as brief and well planned as possible. Such meetings shall be used for purposes that cannot be accomplished effectively through other means. Faculty meetings shall be scheduled in a manner that impacts teacher planning time to the least degree possible. If more than one faculty meeting is held in a month, the purpose of the meeting shall be announced to the faculty in advance.

  • NOTIFICATION OF PUBLIC EVENTS AND MEETINGS 2 A. CONTRACTOR shall notify ADMINISTRATOR of any public event or meeting funded in 3 whole or in part by the COUNTY, except for those events or meetings that are intended solely to serve 4 clients or occur in the normal course of business.

  • Preparatory Contract Negotiations Meetings Where operational requirements permit, the Employer will grant leave without pay to an employee to attend preparatory contract negotiations meetings.

  • Safety Meetings (iii) Accident investigation.

  • Joint Meetings 10.1(a) Should either party desire to discuss with the other any matter affecting generally the relationship of the parties, a meeting of Union and management representatives shall be arranged upon request of either party. Such meeting shall take place at a time mutually convenient to both parties. Any use of Company time for attendance at such meetings shall be arranged in advance by mutual agreement.

  • Management meetings 31.1 Either the Engineer or the Contractor may require the other to attend a management meeting. The business of a management meeting shall be to review the plans for remaining work and to deal with matters raised in accordance with the early warning procedure.

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

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