FaCT Database Sample Clauses

Open Split View

Download

Share

Cite

FaCT Database. The electronic repository for FaCT FRC data collection, outcomes reporting, analysis, and evaluation.

Sample 1

Save

Copy

Related to FaCT Database

• Contract Database Metadata Elements Title: Whitesville Central School District and Whitesville Central School Educational Support Staff Association (2003) Employer Name: Whitesville Central School District Union: Whitesville Central School Educational Support Staff Association Local: Effective Date: 07/01/2003 Expiration Date: 06/30/2006 PERB ID Number: 10699 Unit Size: Number of Pages: 23 For additional research information and assistance, please visit the Research page of the Catherwood website - xxxx://xxx.xxx.xxxxxxx.xxx/library/research/ For additional information on the ILR School - xxxx://xxx.xxx.xxxxxxx.xxx/ AGREEMENT BETWEEN WHITESVILLE CENTRAL SCHOOL EDUCATIONAL SUPPORT STAFF ASSOCIATION AND THE WHITESVILLE CENTRAL SCHOOL DISTRICT JULY 1, 2003 THROUGH JUNE 30, 2006 TABLE OF CONTENTS ARTICLE TITLE PAGE Preamble 1 I Recognition 1 II Collective Bargaining U n i t 1 III Dues/Agency Fee Ckoffand Payroll Deduction 1 IV Rights of Employees 2 V Rights of Employer ------------- 2 VI Personnel F i l e 2 VII Employee Definitions 3 VIII Permanent Status/Seniority 4 IX Wages 5 X Overtime 7 XI Vacation 7 XII Holidays 8 XIII Sick Leave and Leavesof A b s e n c e 8 XIV Conference, Workshops,Required Courses 10 XV Meal Allowance and M i l e a g e 11 XVI Retirement 11 XVII Insurance 12 XVIII Cafeteria P l a n 14 .XIX Uniform Allowance------------------ 14 XX Hours of W o r k 14 XXI Transfers/Promotions 15 XXII Job Descriptions 15 XXIII Grievance Procedure 15 XIV Copies of the Contract 18 XV Zipper C x x x x x 18 XXVI Legislative Clause 18 XXVII Duration 19 SIGNATURES 19 APPENDIX A Grievance F o r m 20 APPENDIX B Dues Authorization F o r m 21

• Contract Data The Consultant is advised to read the NEC3 Professional Service Contract (Third edition with amendments of June 2006 and April 2013) and the relevant Guidance Notes and Flow Charts, published by the Institution of Civil Engineers, in order to understand the implications of this Data which is required. Copies of these documents may be obtained from the Engineering Contract Strategies (telephone (00) 000 000 0000). Each item of data given below is cross-referenced to the clause in the NEC3 Professional Service Contract to which it mainly applies.

• Database The LERG is available through Telcordia. ICONN is available through the Qwest web site.

• Line Information Database 9.1 LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, e-Tel must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

• Product Data Illustrations, standard schedules, performance charts, instructions, brochures, diagrams, and other information furnished by Developer to illustrate a material, product, or system for some portion of the Work.

• CONTRACT INFORMATION 1. The State of Arkansas may not contract with another party:

• Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit B.

• Product Information EPIZYME recognizes that by reason of, inter alia, EISAI’s status as an exclusive licensee in the EISAI Territory under this Agreement, EISAI has an interest in EPIZYME’s retention in confidence of certain information of EPIZYME. Accordingly, until the end of all Royalty Term(s) in the EISAI Territory, EPIZYME shall keep confidential, and not publish or otherwise disclose, and not use for any purpose other than to fulfill EPIZYME’s obligations, or exercise EPIZYME’s rights, hereunder any EPIZYME Know-How Controlled by EPIZYME or EPIZYME Collaboration Know-How, in each case that are primarily applicable to EZH2 or EZH2 Compounds (the “Product Information”), except to the extent (a) the Product Information is in the public domain through no fault of EPIZYME, (b) such disclosure or use is expressly permitted under Section 9.3, or (c) such disclosure or use is otherwise expressly permitted by the terms and conditions of this Agreement. For purposes of Section 9.3, each Party shall be deemed to be both the Disclosing Party and the Receiving Party with respect to Product Information. For clarification, the disclosure by EPIZYME to EISAI of Product Information shall not cause such Product Information to cease to be subject to the provisions of this Section 9.2 with respect to the use and disclosure of such Confidential Information by EPIZYME. In the event this Agreement is terminated pursuant to Article 12, this Section 9.2 shall have no continuing force or effect, but the Product Information, to the extent disclosed by EPIZYME to EISAI hereunder, shall continue to be Confidential Information of EPIZYME, subject to the terms of Sections 9.1 and 9.3 for purposes of the surviving provisions of this Agreement. Each Party shall be responsible for compliance by its Affiliates, and its and its Affiliates’ respective officers, directors, employees and agents, with the provisions of Section 9.1 and this Section 9.2.

• PRIVACY INFORMATION Through Your Use of the Website and Services, You may provide Us with certain information. By using the Website or the Services, You authorize the Company to use Your information in the United States and any other country where We may operate.

• Authoritative Root Database To the extent that ICANN is authorized to set policy with regard to an authoritative root server system (the “Authoritative Root Server System”), ICANN shall use commercially reasonable efforts to (a) ensure that the authoritative root will point to the top-­‐level domain nameservers designated by Registry Operator for the TLD, (b) maintain a stable, secure, and authoritative publicly available database of relevant information about the TLD, in accordance with ICANN publicly available policies and procedures, and (c) coordinate the Authoritative Root Server System so that it is operated and maintained in a stable and secure manner; provided, that ICANN shall not be in breach of this Agreement and ICANN shall have no liability in the event that any third party (including any governmental entity or internet service provider) blocks or restricts access to the TLD in any jurisdiction.