Data Collection Conditions. To ensure that valid consent is obtained for Meta to share Meta Data, Institution and Authorized Individual will comply with the following prior to collecting any data from potential Research Participants:
Data Collection Conditions Sample Clauses
Related to Data Collection Conditions
Data Collection, Processing and Usage The Company collects, processes and uses the International Participant’s personal data, including the International Participant’s name, home address, email address, and telephone number, date of birth, social insurance number or other identification number, salary, citizenship, job title, any shares of Common Stock or directorships held in the Company, and details of all Equity Awards or any other equity compensation awards granted, canceled, exercised, vested, or outstanding in the International Participant’s favor, which the Company receives from the International Participant or the Employer. In granting the Equity Award under the Plan, the Company will collect the International Participant’s personal data for purposes of allocating shares of Common Stock and implementing, administering and managing the Plan. The Company’s legal basis for the collection, processing and usage of the International Participant’s personal data is the International Participant’s consent.
Data Collection The grant recipient will be required to provide performance data reports on a schedule delineated within Section A of this contract, Specific Terms and Conditions.
Data Collection and Usage The Company and the Employer collect, process and use certain personal information about the Participant, including, but not limited to, the Participant’s name, home address and telephone number, email address, date of birth, social insurance, passport or other identification number, salary, nationality, job title, any Shares or directorships held in the Company, details of all restricted stock units or any other entitlement to Shares or equivalent benefits awarded, canceled, exercised, vested, unvested or outstanding in the Participant’s favor (“Data”), for the legitimate purpose of implementing, administering and managing the Plan. The legal basis, where required, for the processing of Data is the Participant’s consent.
Income Collection, Transaction Processing, Account Administration of a basis point per annum on the average net assets of the Fund.
DATA ESCROW REQUIREMENTS Registry Operator will engage an independent entity to act as data escrow agent (“Escrow Agent”) for the provision of data escrow services related to the Registry Agreement. The following Technical Specifications set forth in Part A, and Legal Requirements set forth in Part B, will be included in any data escrow agreement between Registry Operator and the Escrow Agent, under which ICANN must be named a third-‐party beneficiary. In addition to the following requirements, the data escrow agreement may contain other provisions that are not contradictory or intended to subvert the required terms provided below.
Allocations of Finance Charge Collections The Servicer shall allocate to the Series 1997-1 Certificateholders and retain in the Collection Account for application as provided herein an amount equal to the product of (A) the Floating Allocation Percentage and (B) the Series 1997-1 Allocation Percentage and (C) the aggregate amount of Collections of Finance Charge Receivables deposited in the Collection Account on such Deposit Date.
Repayment of Amounts Advanced for Network Upgrades Upon the Commercial Operation Date, the Interconnection Customer shall be entitled to a repayment, equal to the total amount paid to the Participating TO for the cost of Network Upgrades. Such amount shall include any tax gross-up or other tax-related payments associated with Network Upgrades not refunded to the Interconnection Customer, and shall be paid to the Interconnection Customer by the Participating TO on a dollar-for- dollar basis either through (1) direct payments made on a levelized basis over the five- year period commencing on the Commercial Operation Date; or (2) any alternative payment schedule that is mutually agreeable to the Interconnection Customer and Participating TO, provided that such amount is paid within five (5) years from the Commercial Operation Date. Notwithstanding the foregoing, if this Agreement terminates within five (5) years from the Commercial Operation Date, the Participating TO’s obligation to pay refunds to the Interconnection Customer shall cease as of the date of termination. Any repayment shall include interest calculated in accordance with the methodology set forth in FERC’s regulations at 18 C.F.R. §35.19a(a)(2)(iii) from the date of any payment for Network Upgrades through the date on which the Interconnection Customer receives a repayment of such payment. Interest shall continue to accrue on the repayment obligation so long as this Agreement is in effect. The Interconnection Customer may assign such repayment rights to any person. If the Small Generating Facility fails to achieve commercial operation, but it or another Generating Facility is later constructed and makes use of the Network Upgrades, the Participating TO shall at that time reimburse Interconnection Customer for the amounts advanced for the Network Upgrades. Before any such reimbursement can occur, the Interconnection Customer, or the entity that ultimately constructs the Generating Facility, if different, is responsible for identifying the entity to which reimbursement must be made.
Child Support Enforcement Requirements Contractor is required to comply with the child support enforcement requirements of the County. Failure of the Contractor to comply with all federal, state, and local reporting requirements for child support enforcement or to comply with all lawfully served Wage and Earnings Assignment Orders and Notices of Assignment shall constitute a material breach of the Contract. Failure to cure such breach within 60 calendar days of notice from the County shall constitute grounds for termination of the Contract.
Data Collection and Reporting 1. Grantee shall develop and use a local reporting unit that will provide an assigned location for all clients served within the Hospital. This information shall also be entered into Client Assignment and Registration (CARE)when reporting on beds utilized at the Hospital. 2. Grantee shall budget and report expenditure data on the CARE Report III, incorporated by reference and posted at: xxxxx://xxx.xxx.xxxxx.xxx/doing-business-hhs/provider- portals/behavioral-health-services-providers/behavioral-health-provider- resources/community-mental-health-contracts, within the Community Hospital strategy C.2.1.1 using line 764 - Project Private Beds. 3. Grantee shall ensure that patient registration, diagnostics, admission and discharge data is reported by using the CARE screens and action codes listed below: a. Screen: Campus-Based Assignments (Add/Change/Delete), Action Code: 305; b. Screen: Campus-Based Discharge/Community Placement (Add/Change/Delete), Action Code: 310; c. Screen: Joint Community Support Plan (Add/Change/Delete), Action Code: 312; d. Screen: Register Client, Action Code: 325; e. Screen: Diagnostics (Add/Change/Delete), Action Code: 330; f. Screen: Voluntary Admission and Commitment (Add/Change/Delete), Action Code 332; g. Screen: Campus-Based Residential Xxxx/Dorm (Add/Change/Delete), Action Code 615; and h. Screen: MH Bed Allocation Exception (Add/Change/Delete), Action Code 345. For details related to the use of these screens and action codes, Grantee can refer to the CARE Reference Manual which can be found under the CARE (WebCARE) section on the portal at: xxxxx://xxxxxxxxx.xxx.xxxxx.xx.xx/helpGuide/Content/16_CARE/CAREWebCARE%20Refere nce%20Manual.htm
Emergency Operator Access Registry Operator shall provide bulk access to the zone files for the TLD to the Emergency Operators designated by ICANN on a continuous basis in the manner ICANN may reasonably specify from time to time.
