Modify DIP for databases Clause Samples

The 'Modify DIP for databases' clause allows for adjustments to the Data Integration Plan (DIP) specifically as it pertains to databases. In practice, this means that the parties can agree to update, expand, or otherwise change the procedures, requirements, or technical specifications related to database integration as the project evolves. For example, if a new database technology is adopted or additional data sources are identified, the DIP can be modified to accommodate these changes. This clause ensures flexibility in managing database-related aspects of the project, helping to address unforeseen technical needs and maintain alignment with project goals.
Modify DIP for databases. This use case is complicated because content and structure has to be analysed in order to create search forms that can be used to retrieve the desired information in the database -­‐ see Use Case 3. 4.1: Database & EDRM-­‐system. If a tool for a scenario as described in Use case 3.4.4: Analyze with OLAP is developed, the archivist will probably use that for the required modification. It is difficult to foresee the kind of modification needed. If the DIP is modified to fulfil end-­‐users’ wishes, it may be necessary to create one or more search forms, or to extract specific data according to the order. If the DIP is modified to meet the conditions of access, it may be necessary to reduce the dataset by removing database records, by removing tables, or by removing fields in tables. It may also be necessary to depersonalise records. If the DIP consists of data from more than one AIP, it can be time consuming to merge the databases and the documents. Figure 15 -­‐ Modify DIP for databases The use case illustration is described in the table below. Table 9 -­‐ Modify DIP for databases Start Open order and DIP to be modified The order is needed for wishes from the user and for any access restrictions The archivist has to gain knowledge of the structure and content of the database, and that can be done in various ways Examine data in each table Examine metadata about content Examine context metadata Examine metadata by navigating in tree structure Create ER-­‐ diagram Evaluate acquired knowledge of DIP Define search Execute search Defined relations and other conditions OK? There can be problems with the SQL query which prevent it from being executed. The more informative the error message, the easier for the archivist Access allowed for end-­‐user to whole DIP? The archivist checks order and whether access restrictions apply and hence if limiting the content of the DIP is necessary. Create queries and forms according to user needs There are no access restrictions, so the only modifications to be done are according to the user needs as specified by the order Anonymise data? The access restrictions can normally mean that the end-­‐user is allowed to get only part of data, or that data about persons have to be anonymised Use tool for anonymising data and create documentation Documentation of anonymising may be important, especially when the end-­‐user wants data for statistical research. Use SQL to extract data according to access restrictions The archivist uses SQL ...
View Source

Related to Modify DIP for databases

  • 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 C. 9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.

  • 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.

  • Customer Data 5.1 The Customer shall have sole responsibility for the legality, reliability, integrity, accuracy and quality of the Customer Data. The customer being a contractor of DSA Airport, the customer shall not own the rights, title and interest in and to the Data which belongs to DSA Airport. 5.2 The Supplier shall follow its archiving procedures for Customer Data as set out in its Back- Up Policy available at ▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇ or such other website address as may be notified to the Customer from time to time, as such document may be amended by the Supplier in its sole discretion from time to time. In the event of any loss or damage to Customer Data, the Customer's sole and exclusive remedy shall be for the Supplier to use reasonable commercial endeavours to restore the lost or damaged Customer Data from the latest back-up of such Customer Data maintained by the Supplier in accordance with the archiving procedure described in its Back-Up Policy. The Supplier shall not be responsible for any loss, destruction, alteration or disclosure of Customer Data caused by any third party (except those third parties subcontracted by the Supplier to perform services related to Customer Data maintenance and back-up). 5.3 The Supplier shall, in providing the Services, comply with its Privacy and Security Policy relating to the privacy and security of the Customer Data available at ▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇ or such other website address as may be notified to the Customer from time to time, as such document may be amended from time to time by the Supplier in its sole discretion. 5.4 If the Supplier processes any personal data on the Customer’s behalf when performing its obligations under this agreement, the parties record their intention that the Customer shall be the data controller and the Supplier shall be a data processor and in any such case: (a) the Customer acknowledges and agrees that the personal data may be transferred or stored outside the EEA or the country where the Customer and the Authorised Users are located in order to carry out the Services and the Supplier’s other obligations under this agreement; (b) the Customer shall ensure that the Customer is entitled to transfer the relevant personal data to the Supplier so that the Supplier may lawfully use, process and transfer the personal data in accordance with this agreement on the Customer's behalf; (c) the Customer shall ensure that the relevant third parties have been informed of, and have given their consent to, such use, processing, and transfer as required by all applicable data protection legislation; (d) the Supplier shall process the personal data only in accordance with the terms of this agreement and any lawful instructions reasonably given by the Customer from time to time; and (e) each party shall take appropriate technical and organisational measures against unauthorised or unlawful processing of the personal data or its accidental loss, destruction or damage.

  • Procedures for Providing NP Through Full NXX Code Migration Where a Party has activated an entire NXX for a single Customer, or activated at least eighty percent (80%) of an NXX for a single Customer, with the remaining numbers in that NXX either reserved for future use by that Customer or otherwise unused, if such Customer chooses to receive Telephone Exchange Service from the other Party, the first Party shall cooperate with the second Party to have the entire NXX reassigned in the LERG (and associated industry databases, routing tables, etc.) to an End Office operated by the second Party. Such transfer will be accomplished with appropriate coordination between the Parties and subject to appropriate industry lead times for movements of NXXs from one switch to another. Neither Party shall charge the other in connection with this coordinated transfer.

  • Customer Content As part of the Services provided under this Agreement, Customer Data will be stored and processed in the data center region specified in the applicable Ordering Document. Axway shall not access Customer Content except in response to support or technical issues where Customer provides Axway with prior Customer’s written authorization required to access such Customer Content. Axway is not responsible for unauthorized access, alteration, theft or destruction of Customer Content arising from Customer’s own or its authorized users’ actions or omissions in contravention of the Documentation. Customer’s ability to recover any lost data resulting from Axway’s misconduct is limited to restoration by Axway from the most recent back-up.