DATABASE DEVELOPMENT. 7.1. On a trial basis, until and unless AD requests in writing that TMCS cease the program described in this Section 7 as of a specified date (sometimes referred to hereinafter as the "Termination Date"), which date shall not be prior to the implementation of the program described in this Section 7 for at least two (2) artist tours, TMCS agrees to place an "artist newsletter sign-up" opt-in box on the confirmation page of live event ticket sales for the applicable AD artist client with a look and feel to be mutually agreed upon by the parties, for all AD artist clients (including those who may become associated with AD during the term of this Agreement). The opt-in box will encourage ticket-buyers to elect to receive the applicable artist's email communications that may be sent by AD, its affiliates, licensees, successors or assigns, on behalf of such artist in the future. The opt-in box will require that the user provide TMCS with, or authorize the use by TMCS of, the following information: name, email address, street address, event for which tickets were purchased, date of event, and location of event. TMCS will pre-populate those portions of the opt-in box for which TMCS has information to encourage opt-ins. TMCS will also inform users of the manner in which they can change or delete their information in the future. TMCS will display a link to AD's privacy policy adjacent to the opt-in box and state that users can learn how their information will be used by reviewing that policy. ------------------------ [*] Confidential information has been omitted and separately filed with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions.
DATABASE DEVELOPMENT a. 3rd party revenue added to PARCS database/reports. AUGUST 10, 2015 HCAA NO. 6155 14 & 61556 15
DATABASE DEVELOPMENT. The structure and format of the database was first approached in APPRAISAL’s kick-off meeting in Brescia on June 28th 2012 where participants were divided into 3 working groups discussing and defining the database key topics. This work benefited from the partner’s expertise and involvement in related projects such as FAIRMODE, APHEIS, AIR4EU or OPERA. This first approach was presented to the NIAM’s community (in Brescia on June 29th) and first comments and contributions were provided. As a result of these meetings and posterior contributions by the project’s partners via e-mail a first tentative version of the database was put in place. A WP2 brainstorming meeting was then organized in Aveiro on 27-28th September to analyse and improve the first tentative version of the database. Besides APPRAISAL’s partners, stakeholders also provided valuable input to improve the database structure. The first version of the database reached a stable form (in terms of structure, format, key words), ready to be tested by the project’s partners.
DATABASE DEVELOPMENT. The ENGINEER will develop a pipeline and manhole database with information collected during the PROJECT. The information may include sewer system information such as pipe lengths and diameters, street names, sewer manhole investigation reports, and other pertinent information relating to the PROJECT. A database will be provided to the TOWN on an external hard drive upon completion of the PROJECT. The database shall be in Microsoft Access format (current edition).
DATABASE DEVELOPMENT. The Contractor will perform SQL database creation, field mapping to link scannable form fields to database elements, and creation of data definition file.
DATABASE DEVELOPMENT. The program database will be constructed and maintained using a standard Relational Data Base Management System (RDBMS). The primary record index will be based upon patient identification. All information collected at enrollment and during all subsequent interventions will be stored in the database. The record schema(s) will be developed according to the specific question sets and data required by the proposed program. Data may be imported or exported off-line using a variety of industry standard formats, or on-line using DSMi's SQL Server interface. DSMi will use industry standard procedures for insuring the confidentiality and security of the program database.
DATABASE DEVELOPMENT. (a) ****
DATABASE DEVELOPMENT ev3 shall use the ev3 Implementation database architecture to develop a database containing MTI’s information concerning MTI’s distribution, manufacturing and finance processes (the “MTI Database”). The MTI Database shall be populated with reference data and transaction data provided by MTI. These data files shall be obtained by, or provided to, ev3 by or on behalf of MTI in the format specified by ev3. The initial data shall be provided to ev3 prior to data conversion.
DATABASE DEVELOPMENT. Lillethorup will develop and create the database necessary to include all fields and functions specified by Orion as set forth in the SOW;
DATABASE DEVELOPMENT. Develop a database structure to support a multispecies or full ecosystem model for Cook Inlet.
