Modify DIP for databases Sample Clauses

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 Step Description Remarks 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...
Sample 1
AutoNDA by SimpleDocs

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

  • 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 own all right, title and interest in and to all of the Customer Data and shall have sole responsibility for the legality, reliability, integrity, accuracy and quality of the Customer Data.

  • Templates The Applicant shall use Templates provided by Alberta Innovates to comply with its Required Reporting Metrics, Reports obligations, and with the Survey requirements. Because the Reports may contain technical or proprietary information about the Project or the Applicant, the Templates will specify when a section will be considered non-confidential. The content of sections that are marked as non-confidential can be disclosed in the public domain. All other sections will be considered confidential, and thus can only be disclosed to the Government of Alberta and to Funding Partners, if any, in confidence, but to no other party.

  • Technical Requirements for SCPs/Databases 10.5.3.1 BellSouth shall provide physical access to SCPs through the SS7 network and protocols with TCAP as the application layer protocol.

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

  • Protocols Each party hereby agrees that the inclusion of additional protocols may be required to make this Agreement specific. All such protocols shall be negotiated, determined and agreed upon by both parties hereto.

  • We provide Message Boards for the use of Our Website users The Message Boards may not be used to promote Websites or any commercial or business activity. We are not responsible for any of the opinions expressed in the Message Boards. By posting a message to the message board You agree to take full legal responsibility and liability for your comments, including for offensive or defamatory statements. Feedback: Feedback is provided for the purpose of facilitating trading by You on Our Website. Feedback provided on other parties must not contain offensive, defamatory, retaliatory or inappropriate language or content. We may remove any feedback that is considered to be offensive, defamatory, retaliatory or inappropriate. You may only give feedback that relates to a specific transaction. You must not post feedback on a transaction that does not relate to that specific transaction. You must not post feedback about Yourself or include any contact details or Personal Information in Your feedback.

  • Contract Database Metadata Elements Title: Whitesville Central School District and Whitesville Central School Educational Support Staff Association (2003) Employer Name: Whitesville Central School District Union: Whitesville Central School Educational Support Staff Association Local: Effective Date: 07/01/2003 Expiration Date: 06/30/2006 PERB ID Number: 10699 Unit Size: Number of Pages: 23 For additional research information and assistance, please visit the Research page of the Catherwood website - xxxx://xxx.xxx.xxxxxxx.xxx/library/research/ For additional information on the ILR School - xxxx://xxx.xxx.xxxxxxx.xxx/ AGREEMENT BETWEEN WHITESVILLE CENTRAL SCHOOL EDUCATIONAL SUPPORT STAFF ASSOCIATION AND THE WHITESVILLE CENTRAL SCHOOL DISTRICT JULY 1, 2003 THROUGH JUNE 30, 2006 TABLE OF CONTENTS ARTICLE TITLE PAGE Preamble 1 I Recognition 1 II Collective Bargaining U n i t 1 III Dues/Agency Fee Ckoffand Payroll Deduction 1 IV Rights of Employees 2 V Rights of Employer ------------- 2 VI Personnel F i l e 2 VII Employee Definitions 3 VIII Permanent Status/Seniority 4 IX Wages 5 X Overtime 7 XI Vacation 7 XII Holidays 8 XIII Sick Leave and Leavesof A b s e n c e 8 XIV Conference, Workshops,Required Courses 10 XV Meal Allowance and M i l e a g e 11 XVI Retirement 11 XVII Insurance 12 XVIII Cafeteria P l a n 14 .XIX Uniform Allowance------------------ 14 XX Hours of W o r k 14 XXI Transfers/Promotions 15 XXII Job Descriptions 15 XXIII Grievance Procedure 15 XIV Copies of the Contract 18 XV Zipper C x x x x x 18 XXVI Legislative Clause 18 XXVII Duration 19 SIGNATURES 19 APPENDIX A Grievance F o r m 20 APPENDIX B Dues Authorization F o r m 21

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!