Data Upload Sample Clauses

Data Upload. 4.1 Data relating to the Products can be uploaded onto the Website in the form of Documents. You will have sole responsibility for the legality, reliability, integrity, accuracy and quality of such Data. 4.2 Additional Documents loaded which cause the account to fall into a higher product subscription band will incur additional charges and trigger an additional invoice or invoices to be raised. The additional invoiced amount will equate to the difference between the previous band and the higher price band pro rata for the period to the end of the calendar year and is payable within 7 days. 4.3 Existing Data can be updated by you at any time (provided your account remains active) without incurring any additional fee. It is your responsibility to ensure the Data on the web site remains current in accordance with new or revised regulatory requirements.
View Source
Data Upload. In the documentation looks that the Upload function will be activated only by an AITV request and that SA&PI can only send update record when needed. This functionality is not yet implemented and the current documentation will be changed. In any case SA&PI will be able to initiate the transaction.
View Source
Data Upload. Data contained in the Readiness Database Excel workbook will be used to populate the backend SQL database for the application. Two data uploads have been budgeted. The first data upload will allow the State to have data to work with in order to complete testing during application development. Throughout this first upload, scripts will be written to automate subsequent uploads. The final upload will occur prior to application deployment, and it will be done with the most current version of the Blueprint readiness database. The data upload will include the following worksheets from the Readiness Database Excel workbook: Practices, Providers, CHT Administrative Entity, CHT Staff Names and other worksheets identified by the State Blueprint staff during project startup will also be uploaded to the database.
View Source

Related to Data Upload

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Data Use Each party may use Connected Account Data in accordance with this Agreement and the consent (if any) each obtains from each Connected Account. This consent includes, as to Stripe, consent it receives via the Connected Account Agreement.

  • Data Access Access to Contract and State Data The Contractor shall provide to the Client Agency access to any data, as defined in Conn. Gen Stat. Sec. 4e-1, concerning the Contract and the Client Agency that are in the possession or control of the Contractor upon demand and shall provide the data to the Client Agency in a format prescribed by the Client Agency and the State Auditors of Public Accounts at no additional cost.

  • Data Access Control Persons entitled to use data processing systems gain access only to the Personal Data that they have a right to access, and Personal Data must not be read, copied, modified or removed without authorization in the course of processing, use and storage.

  • Data Input Control It will be possible to retrospectively examine and establish whether and by whom Personal Data have been entered, modified or removed from SAP data processing systems.