Source Data. Direct Premium data will be derived from the Accident and Health column of the Schedule T page of the 2005 annual statements filed with the NAIC for each of the Companies (i.e., Mega , Chesapeake, and Mid-West) B.2. Accident and Health Premiums for each state: The accident and health premiums from B.1. for each of the three companies will be added together to arrive at total accident and health premiums for each state. This will be done for each state that is a Signatory Regulator.
Source Data. All information in original records and certified copies of original records of clinical findings, observations, or other activities in a clinical trial necessary for the reconstruction and evaluation of the trial. Source data are contained in source documents (original records or certified copies).
Source Data. This is the data provided by the Customer and/or extracted from the Customer’s website via Bespoke Plug-ins or Scrape Services and is used to create the Core Master Feed. Core Master Feed An optimized set of data which is organized and structured in a standard Intelligent Reach format and may include: (i) information about the Customer or (if applicable) its client’s product inventory, pricing, stock information, product images; (ii) links to the Customer or (if applicable) its client’s Website; (iii) product reference data; and/or (iv) other product attributes. From this, the various Partner Feeds can be created. Partner Feeds A Partner Feed contains the data from the Core Master Feed organized and formatted to the particular requirements of a given Partner. The Intelligent Reach Platform supports many Partners, across many countries and provides the capability to create additional Partner Feeds as required. If there is no current support for a required partner site and the setup is a standard inventory only integration, then this Partner will be added for the benefit of the Intelligent Reach community of users. Typically, we will set this partner up within 4 days from when we receive all the data format information required. Please use the services desk to submit a new partner request (xxxx@xxxxxxxxxxxxxxxx.xxx) Any non-standard Partner site set ups, requiring non-standard work effort, will be subject to one off set up charges. All costs will be agreed prior to any work being performed.
Source Data. AlP- The Company shall produce the charts using the Source Data provided to or obtained by the Company from the national government and/or regulatory authorities in the various AlP or NOTAM or Customer Data in accordance with the AIRAC Cycle and otherwise in a timely manner.
Source Data. The technical information originating from the automobile manufacturers and other certified suppliers, which the Licensor processes into Technical Data for purposes of its contractual counterparty. XXXX: the subject Agreement. Incorrect Source Data An inaccuracy or error in the Source Data and/or its presentation. Incorrect Technical Data: An inaccuracy or error in the Technical Data and/or its presentation. Infringement acting contrary to one or more conditions related to the XXXX. Licence: the non-exclusive right of use granted of the Licensor’s specific Technical data. Licensor: HaynesPro B.V. of Flankement 6 3831SM LEUSDEN The Netherlands Technical Data: the Source Data edited by Xxxxxxxx using his own formats to be issued in Licence.
Source Data. We use all documents in the ‘archaeology’ category in the 2016 version of the Data Archiving and Networked Services (DANS) repository, one of the largest Dutch e-depots. This data set consists of just over 65,000 files, all of which are in PDF format. Examples of included files – based on document titles – are (excavation) reports, publications, separate appendices and figures, letters, and metadata. Although we have not statistically tested the representativeness of this data set, it represents almost all the output of commercial archaeology units from the last 30 years or so, spanning all time periods, site types and different types of reports. Quite often reports have been split into multiple PDFs, one file for each chapter and appendix is quite common for longer reports. For our research, XXXXX already provides a collection in which all files have been converted to both XML and raw text format, which allows for the use of information retrieval and text classification. In this research, we only use the raw text files, which have been created using the pdftotext software (Glyph & Cog LLC, 1996). We see that the conversion of the PDF files to the required text format intro- duced a lot of noise. This includes headers, page numbering and various indices appearing at random positions in the text. The main culprits are tables and figures, which are no longer recognisable after conversion. Brandsen et al. (2019) estimate that around 15% of all documents are OCRed, a process likely to intro- duce noise even before the PDF to text conversion. Luckily, this percentage will only decrease, as more and more born digital documents are added over time.
Source Data. (a) all patient information shall be fully de-identified pursuant to standards and implementation specifications set forth under 42 CFR § 164.514 (the “De-identified Data Set”); (b) no healthcare provider names are included in such data; and (c) all hospital/center names or other identifying information shall be removed and non-identifying numbers or similar designations will be used.
Source Data. The raw PSP data were first assembled into a Microsoft Access™ database and then extracted into SAS data format. All data were cleaned for general and re-measurement errors and new measurements were updated to May 2010. A data dictionary for the tree and plot level variables (including source and compiled datasets) is provided in Appendix A. 1 Canfor no longer re-establishes previously harvested PSPs, as the Growth and Yield Monitoring plots replace these. However, existing Rotation 2 PSPs are re-measured on their established schedule.
Source Data. This is the data provided by the Customer and/or extracted from the Customer’s website via Bespoke Plug-ins or Scrape Services and is used to create the Core Master Data. Core Master Data An optimized set of data which is organized and structured in a standard Intelligent Reach format and may include: (i) information about the Customer or its client’s product inventory, pricing, stock information, product images; (ii) links to the Customer or its client’s Website;
Source Data. The submitting entity is responsible for retaining the source data in its system of record.
