Variable Naming Sample Clauses

Variable Naming. In general, variable names reflect the content of the variable, with an 8 character limitation. All of the variables on this file (except some demographic variables and DUID, DUPERSID, PID, and KEYNESS) end in “13” to denote they are combination Panel 18 Round 1/Panel 17 Round 3 variables. For edited variables, the “13” is followed by an “X”, and they are so noted in the variable label. Variables contained in this delivery were derived either from the questionnaire itself or from the CAPI. The source of each variable is identified in the section of the documentation entitled “D. Variable-Source Crosswalk”. Sources for each variable are indicated in one of four ways: (1) variables derived from the CAPI or assigned in sampling are so indicated; (2) variables derived from complex algorithms associated with reenumeration are labeled “RE Section”; (3) variables that come from one or more specific questions have those numbers listed in the “Source” column; and (4) variables constructed from multiple questions using complex algorithms are labeled “Constructed” in the “Source” column.
AutoNDA by SimpleDocs
Variable Naming. In general, variable names reflect the content of the variable, with an 8-character limitation. Edited variables end in an “X” and are so noted in the variable label. (CONDIDX, which is an encrypted identifier variable, also ends in an “X”.) Variables contained in this delivery were derived either from the questionnaire itself or from the CAPI. The source of each variable is identified in Appendix 1 “Variable-Source Crosswalk.” Sources for each variable are indicated in one of three ways: (1) variables derived from CAPI or assigned in sampling are so indicated; (2) variables collected at one or more specific questions have those numbers and questionnaire sections indicated in the “SOURCE” column; and (3) variables constructed from multiple questions using complex algorithms are labeled “Constructed” in the “SOURCE” column.
Variable Naming. In general, variable names reflect the content of the variable, with an 8 character limitation. For questions asked in a specific round, the end digit in the variable name reflects the round in which the question was asked. All imputed/edited variables end with an “X”.
Variable Naming. In general, variable names reflect the content of the variable, with an 8-character limitation. For questions asked in a specific round, the end digit in the variable name reflects the round in which the question was asked. Edited variables end in an “X” and are so noted in the variable label. (CONDIDX, which is an encrypted identifier variable, also ends in an “X”.) Variables contained in this delivery were derived either from the questionnaire itself or from the CAPI. The source of each variable is identified in Appendix 1 “Variable to Source Crosswalk.” Sources for each variable are indicated in one of three ways: (1) variables derived from CAPI or assigned in sampling are so indicated; (2) variables collected at one or more specific questions have those numbers and questionnaire sections indicated in the “SOURCE” column; and (3) variables constructed from multiple questions using complex algorithms are labeled “Constructed” in the “SOURCE” column.
Variable Naming. In general, variable names reflect the content of the variable, with an 8 character limitation. Generally, imputed/edited variables end with an “X.”
Variable Naming. In general, variable names reflect the content of the variable, with an 8 character limitation. For questions asked in a specific Round, the end digit in the variable name reflects the Round in which the question was asked. Edited variables end in an “X”and are so noted in the variable label. Variables contained in this delivery were derived either from the questionnaire itself or from the CAPI. The source of each variable is identified in Appendix 1 entitled “Variable to Source Crosswalk.” Sources for each variable are indicated in one of four ways: (1) variables which are derived from CAPI or assigned in sampling are so indicated; (2) variables derived from complex algorithms associated with re-enumeration are labeled “RE Section”; (3) variables which come from one or more specific questions have those numbers and questionnaire section indicated in the “Source” column; (4) variables constructed from multiple questions using complex algorithms are labeled “Constructed” in the “SOURCE” column.
Variable Naming. In general, variable names reflect the content of the variable, with an eight-character limitation. Edited variables end in an X, and are so noted in the variable label. The last two characters in round-specific variables denote the rounds of data collection, Round 3, 4, or 5 of Panel 3 and Round 1, 2, or 3 of Panel 4. Unless otherwise noted, variables that end in 99 represent status as of December 31, 1999. Variables contained in this delivery were derived either from the questionnaire itself or from the CAPI. The source of each variable is identified in the section of the documentation entitled
AutoNDA by SimpleDocs

Related to Variable Naming

  • Variable Registry-­‐Level Fee If the ICANN accredited registrars (accounting, in the aggregate, for payment of two-thirds of all registrar-level fees (or such portion of ICANN accredited registrars necessary to approve variable accreditation fees under the then-current registrar accreditation agreement), do not approve, pursuant to the terms of their registrar accreditation agreements with ICANN, the variable accreditation fees established by the ICANN Board of Directors for any ICANN fiscal year, upon delivery of notice from ICANN, Registry Operator shall pay to ICANN a variable registry-level fee, which shall be paid on a fiscal quarter basis, and shall accrue as of the beginning of the first fiscal quarter of such ICANN fiscal year (the “Variable Registry-Level Fee”). The fee will be calculated and invoiced by ICANN on a quarterly basis, and shall be paid by Registry Operator within sixty (60) calendar days with respect to the first quarter of such ICANN fiscal year and within twenty (20) calendar days with respect to each remaining quarter of such ICANN fiscal year, of receipt of the invoiced amount by ICANN. The Registry Operator may invoice and collect the Variable Registry-Level Fees from the registrars that are party to a registry-registrar agreement with Registry Operator (which agreement may specifically provide for the reimbursement of Variable Registry-Level Fees paid by Registry Operator pursuant to this Section 6.3); provided, that the fees shall be invoiced to all ICANN accredited registrars if invoiced to any. The Variable Registry-Level Fee, if collectible by ICANN, shall be an obligation of Registry Operator and shall be due and payable as provided in this Section 6.3 irrespective of Registry Operator’s ability to seek and obtain reimbursement of such fee from registrars. In the event ICANN later collects variable accreditation fees for which Registry Operator has paid ICANN a Variable Registry-Level Fee, ICANN shall reimburse the Registry Operator an appropriate amount of the Variable Registry-Level Fee, as reasonably determined by ICANN. If the ICANN accredited registrars (as a group) do approve, pursuant to the terms of their registrar accreditation agreements with ICANN, the variable accreditation fees established by the ICANN Board of Directors for a fiscal year, ICANN shall not be entitled to a Variable-Level Fee hereunder for such fiscal year, irrespective of whether the ICANN accredited registrars comply with their payment obligations to ICANN during such fiscal year. The amount of the Variable Registry-Level Fee will be specified for each registrar, and may include both a per-registrar component and a transactional component. The per‑registrar component of the Variable Registry-Level Fee shall be specified by ICANN in accordance with the budget adopted by the ICANN Board of Directors for each ICANN fiscal year. The transactional component of the Variable Registry-Level Fee shall be specified by ICANN in accordance with the budget adopted by the ICANN Board of Directors for each ICANN fiscal year but shall not exceed US$0.25 per domain name registration (including renewals associated with transfers from one ICANN accredited registrar to another) per year.

  • Pricing The Contractor will not exceed the pricing set forth in the Contract documents.

  • Street Lighting 4.4.1 The Developer shall provide streetlights for the entire Subdivision at his sole expense. The type of lighting standard, pole spacing, and installation shall be per Memphis Light, Gas and Water standards. Memphis Light Gas and Water shall bill the City for installation of street lighting per its standards.

  • Other Methods of Procurement of Consultants’ Services The following table specifies methods of procurement, other than Quality and Cost-based Selection, which may be used for consultants’ services. The Procurement Plan shall specify the circumstances under which such methods may be used. Procurement Method

  • PRICING STRUCTURES Licenses and Support Services for the Licensed Programs to which this OST applies are granted according to the pricing structures mentioned in the related Transaction Document. Standard pricing structures are defined in the section “DEFINITIONS” of this OST, even though those pricing structures may not be applicable to the DS Offerings to which this OST applies. Other pricing structures may be made available on a case-by-case basis.

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