Contraceptive Method Use and Intention to Use Sample Clauses

Contraceptive Method Use and Intention to Use. The use of contraceptive methods is examined in this section. Except for male condoms, information provided by male youth relates to their partner’s use of contraception. Contraceptive use was examined in three ways: lifetime ever use (except for the condom, which was measured as ever use in the 12 months preceding the survey); current use (at the time of the survey – during the month preceding the survey); and intention to use (continue to use) in the 12 months following the survey. The intention to use question was asked of all respondents irrespective of the use-status at the time of the survey. For current users, the question was meant to assess continuity in use, and among non-users, the question was designed to assess a change in behavior—a transition from non-users to users of contraceptive methods. As we did in the previous section, we examined changes in the contraceptive use indicators between the baseline and endline.
AutoNDA by SimpleDocs

Related to Contraceptive Method Use and Intention to Use

  • Right to Refuse Unsafe Work Employees have the right to refuse to perform unsafe work pursuant to the Occupational Health and Safety Regulations of the Workers Compensation Act.

  • License; Use Upon delivery to an Authorized Person or a person reasonably believed by Custodian to be an Authorized Person of the Fund of software enabling the Fund to obtain access to the System (the “Software”), Custodian grants to the Fund a personal, nontransferable and nonexclusive license to use the Software solely for the purpose of transmitting Written Instructions, receiving reports, making inquiries or otherwise communicating with Custodian in connection with the Account(s). The Fund shall use the Software solely for its own internal and proper business purposes and not in the operation of a service bureau. Except as set forth herein, no license or right of any kind is granted to the Fund with respect to the Software. The Fund acknowledges that Custodian and its suppliers retain and have title and exclusive proprietary rights to the Software, including any trade secrets or other ideas, concepts, know-how, methodologies, or information incorporated therein and the exclusive rights to any copyrights, trademarks and patents (including registrations and applications for registration of either), or other statutory or legal protections available in respect thereof. The Fund further acknowledges that all or a part of the Software may be copyrighted or trademarked (or a registration or claim made therefor) by Custodian or its suppliers. The Fund shall not take any action with respect tot the Software inconsistent with the foregoing acknowledgement, nor shall the Fund attempt to decompile, reverse engineer or modify the Software. The Fund may not xxx, sell, lease or provide, directly or indirectly, any of the Software of any portion thereof to any other person or entity without Custodian’s prior written consent. The Fund may not remove any statutory copyright notice or other notice included in the Software or on any media containing the Software. The Fund shall reproduce any such notice on any reproduction of the Software and shall add any statutory copyright notice or other notice to the Software or media upon Custodian’s request.

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

  • Research Use The Requester agrees that if access is approved, (1) the PI named in the DAR and (2) those named in the “Senior/Key Person Profile” section of the DAR, including the Information Technology Director and any trainee, employee, or contractor1 working on the proposed research project under the direct oversight of these individuals, shall become Approved Users of the requested dataset(s). Research use will occur solely in connection with the approved research project described in the DAR, which includes a 1-2 paragraph description of the proposed research (i.e., a Research Use Statement). Investigators interested in using Cloud Computing for data storage and analysis must request permission to use Cloud Computing in the DAR and identify the Cloud Service Provider (CSP) or providers and/or Private Cloud System (PCS) that they propose to use. They must also submit a Cloud Computing Use Statement as part of the DAR that describes the type of service and how it will be used to carry out the proposed research as described in the Research Use Statement. If the Approved Users plan to collaborate with investigators outside the Requester, the investigators at each external site must submit an independent DAR using the same project title and Research Use Statement, and if using the cloud, Cloud Computing Use Statement. New uses of these data outside those described in the DAR will require submission of a new DAR; modifications to the research project will require submission of an amendment to this application (e.g., adding or deleting Requester Collaborators from the Requester, adding datasets to an approved project). Access to the requested dataset(s) is granted for a period of one (1) year, with the option to renew access or close-out a project at the end of that year. Submitting Investigator(s), or their collaborators, who provided the data or samples used to generate controlled-access datasets subject to the NIH GDS Policy and who have Institutional Review Board (IRB) approval and who meet any other study specific terms of access, are exempt from the limitation on the scope of the research use as defined in the DAR.

  • Exclusive Use (A) After the Occupancy Date, Lessee expressly agrees and warrants that the Leased Premises will be used exclusively as a Champps Restaurant or other casual dining sit-down restaurant. In any other such case, after obtaining Lessor's prior written consent, such consent not to be unreasonably withheld or delayed, Lessee may conduct any lawful business from the Leased Premises. Lessee acknowledges and agrees that any other use without the prior written consent of Lessor will constitute a default under and a violation and breach of this Lease. Lessee agrees: To open for business within a reasonable period of time after completion of construction of the contemplated Improvements; to operate all of the Leased Premises during the Term or Renewal Terms during regular and customary hours for businesses similar to the permitted exclusive use stated herein, unless prevented from doing so by causes beyond Lessee's control or due to remodeling; and to conduct its business in a professional and reputable manner. (B) If the Leased Premises are not operated as a Champps Restaurant or other casual dining sit-down restaurant or other permitted use hereunder, or remain closed for thirty (30) consecutive days (unless such closure results from reasons beyond Lessee's reasonable control) and in the event Lessee fails to pay Rent when due or fulfill any other obligation hereunder, then Lessee shall be in default hereunder and Lessor may, at its option, cancel this Lease by giving written notice to Lessee or exercise any other right or remedy that Lessor may have; provided, however, that closings shall be reasonably permitted for replacement of trade fixtures or during periods of repair after destruction or due to remodeling.

  • Notice of Material Breach and Intent to Exclude The parties agree that a material breach of this CIA by Indivior constitutes an independent basis for Indivior’s exclusion from participation in the Federal health care programs. The length of the exclusion shall be in OIG’s discretion, but not more than five years per material breach. Upon a determination by OIG that Indivior has materially breached this CIA and that exclusion is the appropriate remedy, OIG shall notify Indivior of: (a) Indivior’s material breach; and (b) OIG’s intent to exercise its contractual right to impose exclusion (this notification is hereinafter referred to as the “Notice of Material Breach and Intent to Exclude”).

  • Exclusive Negotiations The State will not bargain collectively or meet with any employee organization other than MSEA-SEIU with reference to terms and conditions of employment of employees covered by this Agreement. If any such organizations request meetings they will be advised by the State to transmit their requests concerning terms and conditions of employment to MSEA-SEIU.

  • Software License Terms (a) Software that is made available by a Provider to Recipient in connection with any Service (any such Software being referred to herein as “TSA-Licensed Software”) provided hereunder will be subject to the terms set forth in this Section 3.5 except as otherwise provided in the applicable Service Schedule. The Provider hereby grants to the Recipient a non-exclusive, non-transferable license to use, in object code form, any TSA-Licensed Software that is made available by the Provider pursuant to a Service Schedule. For the avoidance of doubt, the Provider that makes available any TSA-Licensed Software in connection with the provision of any Service retains the unrestricted right to enhance or otherwise modify such TSA-Licensed Software at any time, provided that such enhancements or other modifications do not disrupt the provision of such Service to the Recipient. (b) The Recipient may not exceed the number of licenses, agents, tiers, nodes, seats, or other use restrictions or authorizations, if any, specified in the applicable Service Schedule. Some TSA-Licensed Software may require license keys or contain other technical protection measures. The Recipient acknowledges that the Provider may monitor the Recipient’s compliance with use restrictions and authorizations remotely, or otherwise. If the Provider makes a license management program available which records and reports license usage information, the Recipient agrees to appropriately install, configure and execute such license management program. (c) Unless otherwise permitted by the Provider, the Recipient may only make copies or adaptations of the TSA-Licensed Software for archival purposes or when copying or adaptation is an essential step in the authorized use of TSA-Licensed Software. If the Recipient makes a copy for backup purposes and installs such copy on a backup device, the Recipient may not operate such backup installation of the TSA-Licensed Software without paying an additional license fee, except in cases where the original device becomes inoperable. If a copy is activated on a backup device in response to failure of the original device, the use on the backup device must be discontinued when the original or replacement device becomes operable. The Recipient may not copy the TSA-Licensed Software onto or otherwise use or make it available on, to, or through any public or external distributed network. Licenses that allow use over the Recipient’s intranet require restricted access by authorized users only. (d) The Recipient must reproduce all copyright notices that appear in or on the TSA-Licensed Software (including documentation) on all permitted copies or adaptations. Copies of documentation are limited to internal use. (e) Notwithstanding anything to the contrary herein, certain TSA-Licensed Software may be licensed under the applicable Service Schedule for use only on a computer system owned, controlled, or operated by or solely on behalf of the Recipient and may be further identified by the Provider by the combination of a unique number and a specific system type (“Designated System”) and such license will terminate in the event of a change in either the system number or system type, an unauthorized relocation, or if the Designated System ceases to be within the possession or control of the Recipient. (f) The Recipient will not modify, reverse engineer, disassemble, decrypt, decompile, or make derivative works of the TSA-Licensed Software. Where the Recipient has other rights mandated under statute, the Recipient will provide the Provider with reasonably detailed information regarding any intended modifications, reverse engineering, disassembly, decryption, or decompilation and the purposes therefor. (g) The Recipient may permit a consultant or subcontractor to use TSA-Licensed Software at the licensed location for the sole purpose of providing services to the Recipient. (h) Upon expiration or termination of the Service Schedule under which TSA-Licensed Software is made available, the Recipient will destroy the TSA-Licensed Software. The Recipient will remove and destroy or return to the Provider any copies of the TSA-Licensed Software that are merged into adaptations, except for individual pieces of data in the Recipient’s database. The Recipient will provide certification of the destruction of TSA-Licensed Software, and copies thereof, to the Provider. The Recipient may retain one copy of the TSA-Licensed Software subsequent to expiration or termination solely for archival purposes. (i) The Recipient may not sublicense, assign, transfer, rent, or lease the TSA-Licensed Software to any other person except as permitted in this Section 3.5. (j) The Recipient agrees that the Provider may engage a third party designated by the Provider and approved by the Recipient (such approval not to be unreasonably withheld) to audit the Recipient’s compliance with the Software License terms. Any such audit will be at the Provider’s expense, require reasonable notice, and will be performed during normal business hours. Such third party will be required to execute a non-disclosure agreement that restricts such third party from disclosing confidential information of the Recipient to the Provider, except to the extent required to report on the extent to which the Recipient is not in compliance with the Software License terms.

  • Termination of License Agreement This Agreement will terminate automatically in the event that the License Agreement is terminated, provided that prior to such termination of this Agreement becoming effective, the Parties shall cooperate to wind down the activities being conducted hereunder as set forth in Section 15.5(b).

  • Use of Basement and Service Areas The basement(s) and service areas, if any, as located within the

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!