Reporting of Registry Activities Sample Clauses

Reporting of Registry Activities. Employers shall report all registry activities to the Labour/Management Relations Committee, including names of those interviewed and those hired.
Sample 1Sample 2Sample 3See All (14)
AutoNDA by SimpleDocs
Reporting of Registry Activities. Employers shall report all registry activities to the Joint Committee, including names of those interviewed and those hired. APPENDIX A Re: Post-Secondary Employers' Association Registry - FORM 001 0. (For PSEA use only:)
Sample 1Sample 2See All (4)
Reporting of Registry Activities. Employers shall report all registry activities to the Labour/Management Relations Committee, including names of those interviewed and those hired. LETTER OF UNDERSTANDING #8 SYSTEM-WIDE ELECTRONIC JOB REGISTRY APPENDIX POST SECONDARY EMPLOYERS' ASSOCIATION REGISTRY FORM 001 0. (For PSEA use only:)
Sample 1Sample 2Sample 3
Reporting of Registry Activities. The College shall report all registry activities to the local Labour/Management Committee, including names of those interviewed and those hired. SIGNED BY BOTH PARTIES TO THIS AGREEMENT, in the City of Cranbrook, British Columbia, this day of , 2018. COLLEGE OF THE ROCKIES CUPE LOCAL 2773 COLLEGE OF THE ROCKIES Xxx Xxxxxxxxxx, President CUPE Local 2773, Negotiating Committee Xxxx Xxxxx, Board Chair, Post- Secondary Employers Association, Negotiating Committee Xxxxxx Xxxxxxx Negotiating Committee Xxxxx Xxxxx, President and CEO, Negotiating Committee Xxxxx Xxxxxx Negotiating Committee Xxxxx Xxxxx, Director Student Affairs, Negotiating Committee Xxxx Xxxxxxxxx Negotiating Committee Xxxxxx XxXxxxxx, Executive Director, Human Resources and College Relations, Negotiating Committtee Xxxxx Xxxxxxx National Representative Xxxxxx Xxxxxxx, Manager of Continuing Education and Contract Training, Negotiating Committee Xxxx Xxxxxxxxx, Manager Student Life and Athletics, Negotiating Committee SCHEDULE 'A' Re: Regular Sessional Employees
Sample 1
Reporting of Registry Activities. The College shall report all registry activities to the local Labour/Management Committee, including names of those interviewed and those hired. SCHEDULE 'A' Re: Regular Sessional Employees
Sample 1Sample 2
Reporting of Registry Activities. The College shall report all registry activities to the local Labour/Management Committee, including names of those interviewed and those hired. SIGNED BY BOTH PARTIES TO THIS AGREEMENT, in the City of Cranbrook, British Columbia, this day of , 2004. CANADIAN UNION OF PUBLIC COLLEGE OF THE ROCKIES EMPLOYEES LOCAL 2773 Xxxxx Xxxxxx, National Representative Xxx Xxxxxx, Board Chair Xxxx Xxxxxx, President Xx. Xxxxxxxx X. Rubidge, President Xxxxxxx Xxxxx, CUPE Negotiating Xxxxx Xxxxxx, COTR Negotiating Committee Member Committee Member Xxxxx Xxxxxx, CUPE Negotiating Xxxxx Xxxxx, COTR Negotiating Committee Member Committee Member Xxxxxxx Xxxxxxxxx, CUPE Negotiating Xxxxx Xxxxxxxx, COTR Negotiating Committee Member Committee Member Letter of Understanding #1 between College of the Rockies and CUPE Local 2773
Sample 1
Reporting of Registry Activities. The College shall report all registry activities to the local Labour/Management Committee, including names of those interviewed and those hired. Letter of Understanding #1 between College of the Rockies and CUPE Local 2773
Sample 1
AutoNDA by SimpleDocs

Related to Reporting of Registry Activities

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: Field # Field Name Description 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES

  • Transition of Registry upon Termination of Agreement text for intergovernmental organizations or governmental entities or other special circumstances: “Transition of Registry upon Termination of Agreement. Upon expiration of the Term pursuant to Section 4.1 or Section 4.2 or any termination of this Agreement pursuant to Section 4.3 or Section 4.4, in connection with ICANN’s designation of a successor registry operator for the TLD, Registry Operator and ICANN agree to consult each other and work cooperatively to facilitate and implement the transition of the TLD in accordance with this Section 4.5. After consultation with Registry Operator, ICANN shall determine whether or not to transition operation of the TLD to a successor registry operator in its sole discretion and in conformance with the Registry Transition Process. In the event ICANN determines to transition operation of the TLD to a successor registry operator, upon Registry Operator’s consent (which shall not be unreasonably withheld, conditioned or delayed), Registry Operator shall provide ICANN or such successor registry operator for the TLD with any data regarding operations of the TLD necessary to maintain operations and registry functions that may be reasonably requested by ICANN or such successor registry operator in addition to data escrowed in accordance with Section 2.3 hereof. In the event that Registry Operator does not consent to provide such data, any registry data related to the TLD shall be returned to Registry Operator, unless otherwise agreed upon by the parties. Registry Operator agrees that ICANN may make any changes it deems necessary to the IANA database for DNS and WHOIS records with respect to the TLD in the event of a transition of the TLD pursuant to this Section 4.5. In addition, ICANN or its designee shall retain and may enforce its rights under the Continued Operations Instrument, regardless of the reason for termination or expiration of this Agreement.”]

  • Abuse and Neglect of Children and Vulnerable Adults: Abuse Registry Party agrees not to employ any individual, to use any volunteer or other service provider, or to otherwise provide reimbursement to any individual who in the performance of services connected with this agreement provides care, custody, treatment, transportation, or supervision to children or to vulnerable adults if there has been a substantiation of abuse or neglect or exploitation involving that individual. Party is responsible for confirming as to each individual having such contact with children or vulnerable adults the non-existence of a substantiated allegation of abuse, neglect or exploitation by verifying that fact though (a) as to vulnerable adults, the Adult Abuse Registry maintained by the Department of Disabilities, Aging and Independent Living and (b) as to children, the Central Child Protection Registry (unless the Party holds a valid child care license or registration from the Division of Child Development, Department for Children and Families). See 33 V.S.A. §4919(a)(3) and 33 V.S.A. §6911(c)(3).

  • Lobbying Activities - Standard Form - LLL No response Do not upload this form unless Vendor has reportable lobbying activities. There are Attributes entitled, “2 CFR Part 200 or Federal Provision - Xxxx Anti-Lobbying Amendment – Continued.” Properly respond to those Attributes and only upload this form if applicable/instructed. If upload is required based on your response to those Attributes, the Disclosure of Lobbying Activities – Standard Form - LLL must be downloaded from the “Attachments” section of the IonWave eBid System, reviewed, properly completed, and uploaded to this location.

  • AGREED FACTS Registration History 6. The Respondent was registered in the securities industry commencing in 1997.

  • Reporting of Unauthorized Disclosure The Contractor shall immediately report to the State any unauthorized disclosure of confidential information.

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

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • DIRECTORS’ RESPONSIBILITY STATEMENT The Directors collectively and individually accept full responsibility for the accuracy of the information given in this announcement and confirm after making all reasonable enquiries that, to the best of their knowledge and belief, this announcement constitutes full and true disclosure of all material facts about the Proposed Acquisition, the Company and its subsidiaries, and the Directors are not aware of any facts the omission of which would make any statement in this announcement misleading. Where information in this announcement has been extracted from published or otherwise publicly available sources or obtained from a named source, the sole responsibility of the Directors has been to ensure that such information has been accurately and correctly extracted from those sources and/or reproduced in this announcement in its proper form and context.

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