Relational databases Sample Clauses

Relational databases. The third case represents a relational database encapsulated in the E-ARK SIP. This case structure presumes that the database is previously exported in the SIARD 2.0 format (a harmonised format for database archiving based on SIARD, Figure 14).52 52 The SIARD 2.0 specification (xxxx://xxx.xxxx-xxxxxxx.xxx/resources/specificationdocs/32-specification-for-siard- format-v20/file) represents the SIP profile for the relational databases content type. Figure 14: Export to SIARD 2.0‌ Various relational databases (e.g. Oracle, PostgreSQL, etc.) exist (1). These databases contain the metadata and records in its native format (2) which can be extracted into a standardised format (4) by following SIARD 2.0 (3). The SIARD extraction should be complemented with more general information about the information package and could be complemented with PREMIS, EAC-CPF, EAD metadata as well (Figure 15). Figure 15: SIARD 2.0 to E-ARK SIP BLOBs and CLOBs in relational databases The Figure 14 and Figure 15 show the most common profile for relational databases with metadata and records. However, in some cases there can be binary data in a relational database which will be exported as external files in SIP creation. This might cause a situation where it is necessary to consult with “Recommendations for external file structure of binary data for the SIARD 2.0 format”, which is a specific and technical recommendation that is not included in the SIARD 2.0 specification. The detailed recommendation can be found in Appendix D, but in order to see if this recommendation is needed a short introduction to where it applies is presented in the following. Binary data in regard to relational databases is defined as information which is stored in the database as a bit stream following a specific file format. The potentially huge size of binary data within a database can lead to problems in the handling and archival processing of the database. Binary data is mostly referred to as binary large object (BLOB). Similarly large amounts of character data are named CLOB. CLOBs pose a problem due to size more than lack of a proper data type. For the rest of this section CLOBs will be treated as BLOBs. An example of a relational database with BLOBs could be a database where images are stored. Databases and the handling of binary data has always been a challenge, regardless of whether the handling was based on:
Sample 1
AutoNDA by SimpleDocs

Related to Relational databases

  • Processing Personal Data 40.1. The Company is the data controller in the relevant jurisdiction. You hereby acknowledge and agree to the collection and processing of personal data provided by you in connection with the opening of a trading account for the purpose of performing our obligations under these Terms and Conditions and for administering the relationship between you and us.

  • Personal Data Registry Operator shall (i) notify each ICANN-­‐accredited registrar that is a party to the registry-­‐registrar agreement for the TLD of the purposes for which data about any identified or identifiable natural person (“Personal Data”) submitted to Registry Operator by such registrar is collected and used under this Agreement or otherwise and the intended recipients (or categories of recipients) of such Personal Data, and (ii) require such registrar to obtain the consent of each registrant in the TLD for such collection and use of Personal Data. Registry Operator shall take reasonable steps to protect Personal Data collected from such registrar from loss, misuse, unauthorized disclosure, alteration or destruction. Registry Operator shall not use or authorize the use of Personal Data in a way that is incompatible with the notice provided to registrars.

  • Processing of Personal Data (a) SORACOM collects and processes personal data about the Subscriber, including name, e-mail, IP-address as well as data on data uses and billing data in order to provide SORACOM’s service and other purposes such as billing.

  • Personal Data Processing 2.1 The Processor shall process Personal Data only on the basis of corresponding recorded orders from the Controller.

  • Data To permit evaluation of requests under paragraph (c) of this clause based on unreasonable cost, the Contractor shall include the following information and any applicable supporting data based on the survey of suppliers: Foreign and Domestic Construction Materials Cost Comparison Construction material description Unit of measure Quantity Cost (dollars) * Item 1: Foreign construction material Domestic construction material Item 2 Foreign construction material Domestic construction material [List name, address, telephone number, and contact for suppliers surveyed. Attach copy of response; if oral, attach summary.] [Include other applicable supporting information.] (*Include all delivery costs to the construction site.]

  • Protection of Personal Data 25.1 The Parties agree that they may obtain and have access to personal data for the duration of the Agreement for the fulfilment of the rights and obligations contained herein. In performing the obligations as set out in this Agreement, the Parties shall at all times ensure that:

  • Types of Personal Data Contact Information, the extent of which is determined and controlled by the Customer in its sole discretion, and other Personal Data such as navigational data (including website usage information), email data, system usage data, application integration data, and other electronic data submitted, stored, sent, or received by end users via the Subscription Service.

  • Customer’s Processing of Personal Data Customer shall, in its use of the Services, Process Personal Data in accordance with the requirements of Data Protection Laws and Regulations. For the avoidance of doubt, Customer’s instructions for the Processing of Personal Data shall comply with Data Protection Laws and Regulations. Customer shall have sole responsibility for the means by which Customer acquired Personal Data.

  • Type of Personal Data Data Subjects may provide the following Shared Personal Data in connection with the purchase of a domain name from a Registrar: Registrant Name: Example Registrant Street: 0000 Xxxxxxxxx Xxx City: Marina del Rey State/Province: CA Postal Code: 90292 Country: US Phone Number: +1.0000000000 Fax Number: +1.3105551213 Email: xxxxxxxxxx@xxxxxxx.xxx Admin Contact: Xxxx Registrant Phone Number: +1.3105551214 Fax Number: +1.3105551213 Email: xxxxxxxxxxxxx@xxxxxxx-xxxxxxxxxx.xxx Technical Contact: Xxxx Geek Phone Number: +1.3105551215 Fax Number: +1.3105551216

  • Protection of Personal Information Party agrees to comply with all applicable state and federal statutes to assure protection and security of personal information, or of any personally identifiable information (PII), including the Security Breach Notice Act, 9 V.S.A. § 2435, the Social Security Number Protection Act, 9 V.S.A. § 2440, the Document Safe Destruction Act, 9 V.S.A. § 2445 and 45 CFR 155.260. As used here, PII shall include any information, in any medium, including electronic, which can be used to distinguish or trace an individual’s identity, such as his/her name, social security number, biometric records, etc., either alone or when combined with any other personal or identifiable information that is linked or linkable to a specific person, such as date and place or birth, mother’s maiden name, etc.

Time is Money Join Law Insider Premium to draft better contracts faster.