DOCSLIB.ORG

Describing Data Patterns. a General Deconstruction of Metadata Standards

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Describing Data Patterns. a General Deconstruction of Metadata Standards Describing Data Patterns A general deconstruction of metadata standards Dissertation in support of the degree of Doctor philosophiae (Dr. phil.) by Jakob Voß submitted at January 7th 2013 defended at May 31st 2013 at the Faculty of Philosophy I Humboldt-University Berlin Berlin School of Library and Information Science Reviewer: Prof. Dr. Stefan Gradman Prof. Dr. Felix Sasaki Prof. William Honig, PhD This document is licensed under the terms of the Creative Commons Attribution- ShareAlike license (CC-BY-SA). Feel free to reuse any parts of it as long as attribution is given to Jakob Voß and the result is licensed under CC-BY-SA as well. The full source code of this document, its variants and corrections are available at https://github.com/jakobib/phdthesis2013. Selected parts and additional content are made available at http://aboutdata.org A digital copy of this thesis (with same pagination but larger margins to fit A4 paper format) is archived at http://edoc.hu-berlin.de/. A printed version is published through CreateSpace and available by Amazon and selected distributors. ISBN-13: 978-1-4909-3186-9 ISBN-10: 1-4909-3186-4 Cover: the Arecibo message, sent into empty space in 1974 (image CC-BY-SA Arne Nordmann, http://commons.wikimedia.org/wiki/File:Arecibo_message.svg) CC-BY-SA by Widder (2010) Abstract Many methods, technologies, standards, and languages exist to structure and de- scribe data. The aim of this thesis is to find common features in these methods to determine how data is actually structured and described. Existing studies are limited to notions of data as recorded observations and facts, or they require given structures to build on, such as the concept of a record or the concept of a schema. These presumed concepts have been deconstructed in this thesis from a semiotic point of view. This was done by analysing data as signs, communicated in form of digital documents. The study was conducted by a phenomenological research method. Conceptual properties of data structuring and description were first col- lected and experienced critically. Examples of such properties include encodings, identifiers, formats, schemas, and models. The analysis resulted in six prototypes to categorize data methods by their primary purpose. The study further revealed five basic paradigms that deeply shape how data is structured and described in practice. The third result consists of a pattern language of data structuring. The patterns show problems and solutions which occur over and over again in data, independent from particular technologies. Twenty general patterns were identified and described, each with its benefits, consequences, pitfalls, and relations to other patterns. The results can help to better understand data and its actual forms, both for consumption and creation of data. Particular domains of application include data archaeology and data literacy. iv Zusammenfassung Diese Arbeit behandelt die Frage, wie Daten grundsatzlich¨ strukturiert und be- schrieben sind. Im Gegensatz zu vorhandenen Auseinandersetzungen mit Daten im Sinne von gespeicherten Beobachtungen oder Sachverhalten, werden Daten hierbei semiotisch als Zeichen aufgefasst. Diese Zeichen werden in Form von digitalen Dokumenten kommuniziert und sind mittels zahlreicher Standards, Formate, Spra- chen, Kodierungen, Schemata, Techniken etc. strukturiert und beschrieben. Diese Vielfalt von Mitteln wird erstmals in ihrer Gesamtheit mit Hilfe der phenomenologi- schen Forschungsmethode analysiert. Ziel ist es dabei, durch eine genaue Erfahrung und Beschreibung von Mitteln zur Strukturierung und Beschreibung von Daten zum allgemeinen Wesen der Datenstrukturierung und -beschreibung vorzudrin- gen. Die Ergebnisse dieser Arbeit bestehen aus drei Teilen. Erstens ergeben sich sechs Prototypen, die die beschriebenen Mittel nach ihrem Hauptanwendungszweck kategorisieren. Zweitens gibt es funf¨ Paradigmen, die das Verstandnis¨ und die An- wendung von Mitteln zur Strukturierung und Beschreibung von Daten grundlegend beeinflussen. Drittens legt diese Arbeit eine Mustersprache der Datenstrukturierung vor. In zwanzig Mustern werden typische Probleme und Losungen¨ dokumentiert, die bei der Strukturierung und Beschreibung von Daten unabhangig¨ von konkre- ten Techniken immer wieder auftreten. Die Ergebnisse dieser Arbeit konnen¨ dazu beitragen, das Verstandnis¨ von Daten — das heisst digitalen Dokumente und ihre Metadaten in allen ihren Formen — zu verbessern. Spezielle Anwendungsgebiete liegen unter Anderem in den Bereichen Datenarchaologie¨ und Daten-Literacy. v Contents Abstract ....................................... iv Zusammenfassung .................................v List of Examples .................................. vii List of Figures ................................... vii List of Tables .................................... vii 1. Introduction 1 1.1. Motivation ..................................1 1.2. Background .................................4 1.3. Method and scope ..............................6 1.4. Related work .................................7 2. Foundations 11 2.1. Mathematics ................................. 12 2.1.1. Logic ................................. 12 2.1.2. Set theory .............................. 15 2.1.3. Tuples and relations ........................ 17 2.1.4. Graph theory ............................ 18 2.2. Computer science .............................. 23 2.2.1. Formal languages and computation ................ 24 2.2.2. Data types .............................. 29 2.2.3. Data modeling ............................ 32 2.3. Library and information science ...................... 36 2.3.1. Background of the discipline ................... 36 2.3.2. Documents .............................. 37 2.3.3. Metadata ............................... 39 2.4. Philosophy .................................. 41 2.4.1. Philosophy of Information ..................... 41 2.4.2. Philosophy of Data ......................... 42 2.4.3. Philosophy of Technology and Design .............. 44 2.5. Semiotics ................................... 45 2.6. Patterns and pattern languages ...................... 50 3. Methods of data structuring 53 3.1. Character and number encodings ..................... 54 3.1.1. Unicode ............................... 54 3.1.2. Number encodings ......................... 58 vii Contents 3.2. Identifiers .................................. 59 3.2.1. Basic principles ........................... 59 3.2.2. Namespaces and qualifiers ..................... 62 3.2.3. Identifier Systems .......................... 63 3.2.4. Descriptive identifiers ....................... 67 3.2.5. Ordered identifiers ......................... 68 3.2.6. Hash codes .............................. 69 3.3. File systems ................................. 72 3.3.1. Origins and evolution ........................ 72 3.3.2. Components and properties .................... 73 3.3.3. Wrapping file systems ....................... 77 3.4. Databases ................................... 79 3.4.1. Record databases .......................... 79 3.4.2. Hierarchical databases ....................... 83 3.4.3. Network databases ......................... 84 3.4.4. Relational databases ........................ 85 3.4.5. Object database ........................... 89 3.4.6. NoSQL databases .......................... 90 3.5. Data structuring languages ......................... 92 3.5.1. Data binding languages ...................... 92 3.5.2. INI, CSV, and S-Expressions .................... 93 3.5.3. JSON ................................. 95 3.5.4. YAML ................................. 97 3.5.5. XML ................................. 98 3.5.6. RDF .................................. 103 3.6. Markup languages .............................. 112 3.6.1. General markup types ....................... 112 3.6.2. Text markup languages ....................... 114 3.7. Schema languages .............................. 119 3.7.1. Regular Expressions and Backus-Naur Form ........... 120 3.7.2. XML schema languages ....................... 122 3.7.3. RDF schema languages ....................... 131 3.7.4. SQL schemas ............................. 134 3.7.5. Other schema languages ...................... 135 3.8. Conceptual modeling languages ...................... 138 3.8.1. Entity-relationship model ..................... 138 3.8.2. Object Role Modeling ........................ 142 3.8.3. Unified Modeling language .................... 145 3.8.4. Domain specific modeling and metamodeling .......... 147 3.9. Conceptual diagrams ............................ 149 3.9.1. Diagram types ............................ 150 3.9.2. Diagram properties ......................... 155 3.10. Query languages and APIs ......................... 156 viii Contents 4. Findings 159 4.1. Categorization of methods ......................... 159 4.2. Paradigms in data structuring ....................... 160 4.2.1. Documents and objects ....................... 161 4.2.2. Standards and rules ......................... 164 4.2.3. Collections, types, and sameness ................. 170 4.2.4. Entities and connections ...................... 173 4.2.5. Levels of abstraction ........................ 176 5. Patterns in data structuring 181 5.1. Organization ................................. 181 5.2. Basic patterns ................................ 182 5.2.1. Label pattern ............................ 183 5.2.2. Atomicity pattern .......................... 184 5.2.3. Size pattern ............................. 186 5.2.4. Optionality pattern ......................... 187 5.2.5.
Load more

Recommended publications
  • Development Team Principal Investigator Prof
    Paper No: 6 Remote Sensing & GIS Applications in Environmental Sciences Module: 22 Hierarchical, network and relational data Development Team Principal Investigator Prof. R.K. Kohli & Prof. V.K. Garg & Prof. Ashok Dhawan Co- Principal Investigator Central University of Punjab, Bathinda Dr. Puneeta Pandey Paper Coordinator Centre for Environmental Sciences and Technology Central University of Punjab, Bathinda Dr Dinesh Kumar, Content Writer Department of Environmental Sciences Central University of Jammu Content Reviewer Dr. Puneeta Pandey Central University of Punjab, Bathinda Anchor Institute Central University of Punjab 1 Remote Sensing & GIS Applications in Environmental Sciences Environmental Hierarchical, network and relational data Sciences Description of Module/- Subject Name Environmental Sciences Paper Name Remote Sensing & GIS Applications in Environmental Sciences Module Name/Title Hierarchical, network and relational data Module Id EVS/RSGIS-EVS/22 Pre-requisites Introductory knowledge of computers, basic mathematics and GIS Objectives To understand the concept of DBMS and database Models Keywords Fuzzy Logic, Decision Tree, Vegetation Indices, Hyper-spectral, Multispectral 2 Remote Sensing & GIS Applications in Environmental Sciences Environmental Hierarchical, network and relational data Sciences Module 29: Hierarchical, network and relational data 1. Learning Objective The objective of this module is to understand the concept of Database Management System (DBMS) and database Models. The present module explains in details about the relevant data models used in GIS platform along with their pros and cons. 2. Introduction GIS is a very powerful tool for a range of applications across the disciplines. The capacity of GIS tool to store, retrieve, analyze and model the information comes from its database management system (DBMS).
    [Show full text]
  • Bibliography of Erik Wilde
    dretbiblio dretbiblio Erik Wilde's Bibliography References [1] AFIPS Fall Joint Computer Conference, San Francisco, California, December 1968. [2] Seventeenth IEEE Conference on Computer Communication Networks, Washington, D.C., 1978. [3] ACM SIGACT-SIGMOD Symposium on Principles of Database Systems, Los Angeles, Cal- ifornia, March 1982. ACM Press. [4] First Conference on Computer-Supported Cooperative Work, 1986. [5] 1987 ACM Conference on Hypertext, Chapel Hill, North Carolina, November 1987. ACM Press. [6] 18th IEEE International Symposium on Fault-Tolerant Computing, Tokyo, Japan, 1988. IEEE Computer Society Press. [7] Conference on Computer-Supported Cooperative Work, Portland, Oregon, 1988. ACM Press. [8] Conference on Office Information Systems, Palo Alto, California, March 1988. [9] 1989 ACM Conference on Hypertext, Pittsburgh, Pennsylvania, November 1989. ACM Press. [10] UNIX | The Legend Evolves. Summer 1990 UKUUG Conference, Buntingford, UK, 1990. UKUUG. [11] Fourth ACM Symposium on User Interface Software and Technology, Hilton Head, South Carolina, November 1991. [12] GLOBECOM'91 Conference, Phoenix, Arizona, 1991. IEEE Computer Society Press. [13] IEEE INFOCOM '91 Conference on Computer Communications, Bal Harbour, Florida, 1991. IEEE Computer Society Press. [14] IEEE International Conference on Communications, Denver, Colorado, June 1991. [15] International Workshop on CSCW, Berlin, Germany, April 1991. [16] Third ACM Conference on Hypertext, San Antonio, Texas, December 1991. ACM Press. [17] 11th Symposium on Reliable Distributed Systems, Houston, Texas, 1992. IEEE Computer Society Press. [18] 3rd Joint European Networking Conference, Innsbruck, Austria, May 1992. [19] Fourth ACM Conference on Hypertext, Milano, Italy, November 1992. ACM Press. [20] GLOBECOM'92 Conference, Orlando, Florida, December 1992. IEEE Computer Society Press. http://github.com/dret/biblio (August 29, 2018) 1 dretbiblio [21] IEEE INFOCOM '92 Conference on Computer Communications, Florence, Italy, 1992.
    [Show full text]
  • Pentest-Report Mailvelope 12.2012 - 02.2013 Cure53, Dr.-Ing
    Pentest-Report Mailvelope 12.2012 - 02.2013 Cure53, Dr.-Ing. Mario Heiderich / Krzysztof Kotowicz Index Introduction Test Chronicle Methodology Vulnerabilities MV -01-001 Insufficient Output Filtering enables Frame Hijacking Attacks ( High ) MV -01-002 Arbitrary JavaScript execution in decrypted mail contents ( High ) MV -01-003 Usage of external CSS loaded via HTTP in privileged context ( Medium ) MV -01-004 UI Spoof via z - indexed positioned DOM Elements ( Medium ) MV -01-005 Predictable GET Parameter Usage for Connection Identifiers ( Medium ) MV -01-006 Rich Text Editor transfers unsanitized HTML content ( High ) MV -01-007 Features in showModalDialog Branch expose M ailer to XSS ( Medium ) MV -01-008 Arbitrary File Download with RTE editor filter bypass ( Low ) MV -01-009 Lack of HTML Sanitization when using Plaintext Editor ( Medium ) Miscellaneous Issues Conclusion Introduction “Mailvelope uses the OpenPGP encryption standard which makes it compatible to existing mail encryption solutions. Installation of Mailvelope from the Chrome Web Store ensures that the installation package is signed and therefore its origin and integrity can be verified. Mailvelope integrates directly into the Webmail user interface, it's elements are unintrusive and easy to use in your normal workflow. It comes preconfigured for major web mail provider. Mailvelope can be customized to work with any Webmail.”1 1 http :// www . mailvelope . com /about Test Chronicle • 2012/12/20 - XSS vectors in common input fields (Mailvelope options etc.) • 2012/12/20 -
    [Show full text]
  • Faster Base64 Encoding and Decoding Using AVX2 Instructions
    Faster Base64 Encoding and Decoding using AVX2 Instructions WOJCIECH MUŁA, DANIEL LEMIRE, Universite´ du Quebec´ (TELUQ) Web developers use base64 formats to include images, fonts, sounds and other resources directly inside HTML, JavaScript, JSON and XML files. We estimate that billions of base64 messages are decoded every day. We are motivated to improve the efficiency of base64 encoding and decoding. Compared to state-of-the-art implementations, we multiply the speeds of both the encoding (≈ 10×) and the decoding (≈ 7×). We achieve these good results by using the single-instruction-multiple-data (SIMD) instructions available on recent Intel processors (AVX2). Our accelerated software abides by the specification and reports errors when encountering characters outside of the base64 set. It is available online as free software under a liberal license. CCS Concepts: •Theory of computation ! Vector / streaming algorithms; General Terms: Algorithms, Performance Additional Key Words and Phrases: Binary-to-text encoding, Vectorization, Data URI, Web Performance 1. INTRODUCTION We use base64 formats to represent arbitrary binary data as text. Base64 is part of the MIME email protocol [Linn 1993; Freed and Borenstein 1996], used to encode binary attachments. Base64 is included in the standard libraries of popular programming languages such as Java, C#, Swift, PHP, Python, Rust, JavaScript and Go. Major database systems such as Oracle and MySQL include base64 functions. On the Web, we often combine binary resources (images, videos, sounds) with text- only documents (XML, JavaScript, HTML). Before a Web page can be displayed, it is often necessary to retrieve not only the HTML document but also all of the separate binary resources it needs.
    [Show full text]
  • The Entity-Relationship Model — 'A3s
    .M414 INST. OCT 26 1976 WORKING PAPER ALFRED P. SLOAN SCHOOL OF MANAGEMENT THE ENTITY-RELATIONSHIP MODEL — 'A3S. iflST. l^CH. TOWARD A UNIFIED VIEW OF DATA* OCT 25 197S [ BY PETER PIN-SHAN CHEN WP 839-76 MARCH, 1976 MASSACHUSETTS INSTITUTE OF TECHNOLOGY 50 MEMORIAL DRIVE CAMBRIDGE, MASSACHUSETTS 02139 THE ENTITY-RELATIONSHIP MODEL — — A3S. iHST.TiiCH. TOWARD A UNIFIED VIEW OF DATA* OCT 25 1976 BY PETER PIN-SHAN CHEN WP 839-76 MARCH, 1976 * A revised version of this paper will appear in the ACM Transactions on Database Systems. M.I.T. LlBaARiE; OCT 2 6 1976 ' RECEIVE J I ABSTRACT: A data model, called the entity-relationship model^ls proposed. This model incorporates some of the Important semantic information in the real world. A special diagramatic technique is introduced as a tool for data base design. An example of data base design and description using the model and the diagramatic technique is given. Some implications on data integrity, information retrieval, and data manipulation are discussed. The entity-relationship model can be used as a basis for unification of different views of data: the network model, the relational model, and the entity set model. Semantic ambiguities in these models are analyzed. Possible ways to derive their views of data from the entity-relationship model are presented. KEY WORDS AND PHRASES: data base design, logical view of data, semantics of data, data models, entity-relationship model, relational model. Data Base Task Group, network model, entity set model, data definition and manipulation, data integrity and consistency. CR CATEGORIES: 3.50, 3.70, 4.33, 4.34.
    [Show full text]
  • Cs297report-PDF
    CS297 Report Bookmarklet Builder for Offline Data Retrieval Sheetal Naidu [email protected] Advisor: Dr. Chris Pollett Department of Computer Science San Jose State University Fall 2007 Table of Contents Introduction ………………………………………………………………………………. 3 Deliverable 1 ……………………………………………………………………………... 3 Deliverable 2 ……………………………………………………………………………... 4 Deliverable 3 ……………………………………………………………………………... 6 Deliverable 4 ……………………………………………………………………………... 7 Future work ………………………………………………………………………………. 8 Conclusion ……………………………………………………………………………….. 8 References ………………………………………………………………………………... 8 2 Introduction A bookmarklet is a small computer application that is stored as a URL of a bookmark in the browser. Bookmarlet builders exist for storing single webpages in hand held devices and these webpages are stored as PDF files. The goal of my project is to develop a tool that can save entire web page applications as bookmarklets. This will enable users to use these applications even when they are not connected to the Internet. The main technology beyond Javascript needed to do this is the data: URI scheme. This enables images, Flash, applets, PDFs, etc. to be directly embedded as base64 encoded text within a web page. This URI scheme is supported by all major browsers other than Internet Explorer. Our program will obfuscate the actual resulting JavaScript so these complete applications could potentially be sold without easily being reverse engineered. The application will be made available online, to users who are typically website owners and would like to allow their users to be able to use the applications offline. This report describes the background work that was conducted as preparation for CS298 when the actual implementation of the project will take place. This preparation work was split into four main deliverables. The deliverables were designed at gaining relevant information and knowledge with respect to the main project.
    [Show full text]
  • Q4 2016 Newsletter
    FraudAction™ Anti-Fraud Services Q4 2016 NEWSLETTER TABLE OF CONTENTS Introduction ............................................................................................................................................ 3 The Many Schemes and Techniques of Phishing ............................................................................................... 4 The Tax Refund Ploy - Multi-branded Phishing ............................................................................................... 4 Bulk Phishing Campaigns ........................................................................................................................ 4 Random Folder Generators ...................................................................................................................... 5 Local HTML Scheme .............................................................................................................................. 6 BASE64 encoded Phishing in a URL ........................................................................................................... 7 Phishing with MITM capabilities ................................................................................................................. 7 Phishing Plus Mobile Malware in India ....................................................................................................... 10 Fast-Flux Phishing ............................................................................................................................... 13 Additional Phishing Techniques
    [Show full text]
  • Analysis of Hypertext Markup Isolation Techniques for XSS Prevention
    Analysis of Hypertext Isolation Techniques for XSS Prevention Mike Ter Louw Prithvi Bisht V.N. Venkatakrishnan Department of Computer Science University of Illinois at Chicago Abstract that instructs a browser to mark certain, isolated portions of an HTML document as untrusted. If robust isolation Modern websites and web applications commonly inte- facilities were supported by web browsers, policy-based grate third-party and user-generated content to enrich the constraints could be enforced over untrusted content to user’s experience. Developers of these applications are effectively prevent script injection attacks. in need of a simple way to limit the capabilities of this The draft version of HTML 5 [21] does not propose less trusted, outsourced web content and thereby protect any hypertext isolation facility, even though XSS is a long their users from cross-site scripting attacks. We summa- recognized threat and several informal solutions have re- rize several recent proposals that enable developers to iso- cently been suggested by concerned members of the web late untrusted hypertext, and could be used to define ro- development community. The main objective of this pa- bust constraint environments that are enforceable by web per is to categorize these proposals, analyze them further browsers. A comparative analysis of these proposals is and motivate the web standards and research communities presented highlighting security, legacy browser compati- to focus on the issue. bility and several other important qualities. 2 Background 1 Introduction Today’s browsers implement a default-allow policy for One hallmark of the Web 2.0 phenomenon is the rapid JavaScript in the sense they permit execution of any script increase in user-created content for web applications.
    [Show full text]
  • ISSUE for a WILD NEW SOUND • • • Listen to ALFRED E
    SPECIAL"JUNE-GROOM" ISSUE FOR A WILD NEW SOUND • • • Listen to ALFRED E. NEUMAN VOCALIZE IT'S A GAS!" on this real 1 33 /3R.P.M RECORD You get it as a FREE BONUS in this latest MAD ANNUAL Which also contains articles, ad satires and other garbage — the best from past issues! PLUS A SPECIAL FREE BONUS WITH A WILD NEW SOUND: ON SALE NOW! Rush out and buy a copy! ON A REAL 33/3RPM RECORD It's a "Sound Investment"! N UMBER 104 JULY 1966 VITAL FEATURES ADVERTISING CAMPAIGNS 'There's one thing we know for sure about the speed of light: WITH ULTERIOR It gets here too early in the morning!"—Alfred E. Neuman MOTIVES PG.4 WILLIAM M. GAINES publisher ALBERT B. FELDSTEIN editor JOHN PUTNAM art director LEONARD BRENNER production JERRY DE FUCCIO, NICK MECLIN associate editors MARTIN J. SCHEIMAN lawsuits RICHARD BERNSTEIN publicity GLORIA ORLANDO, CELIA MORELLI, RICHARD GRILLO Subscriptions CONTRIBUTING ARTISTS AND WRITERS the usual gang of idiots FUTURE WIT AND WISDOM DEPARTMENTS BOOKS PG. 10 BERGS-EYE VIEW DEPARTMENT The Lighter Side Of High School 28 DON MARTIN DEPARTMENT In The Hospital 13 Later On In The Hospital 25 Still Later On In The Hospital 42 FUNNY-BONE-HEADS DEPARTMENT MAD VISITS THE AMERICAN Future Wit And Wisdom Books •. 10 MEDIOCRITY HIGHWAY RIBBERY DEPARTMENT ACADEMY Road Signs We'd Really Like To See 32 PG. 21 INSTITUTION FOR THE CRIMINALLY INANE DEPARTMENT MAD Visits The American Mediocrity Academy 21 LETTERS DEPARTMENT Random Samplings Of Reader Mail 2 LICKING THE PROBLEM DEPARTMENT Postage Stamp Advertising 34 MIXING MARGINAL THINKING DEPARTMENT POLITICS Drawn-Out Dramas ** WITH MICROFOLK DEPARTMENT CAREERS Another MAD Peek Through The Microscope 8 PG.
    [Show full text]
  • DATA INTEGRATION GLOSSARY Data Integration Glossary
    glossary DATA INTEGRATION GLOSSARY Data Integration Glossary August 2001 U.S. Department of Transportation Federal Highway Administration Office of Asset Management NOTE FROM THE DIRECTOR Office of Asset Management, Infrastructure Core Business Unit, Federal Highway Administration his glossary is one of a series of documents on data integration being published by the Federal Highway Administration’s Office of Asset T Management. It defines in simple and understandable language a broad set of the terminologies used in information management, particularly in regard to database management and integration. Our objective is to provide convenient reference material that can be used by individuals involved in data integration activities. The glossary is limited to the more fundamental concepts and taxonomies applied in transportation database management and is not intended to be comprehensive. The importance of data integration in implementing Asset Management processes cannot be overstated. My office will continue to provide information and support to all transportation agencies as they work to integrate their data. Madeleine Bloom Director, Office of Asset Management DATA INTEGRATION GLOSSARY 3 LIST OF TERMS Aggregate data . .7 Dynamic segmentation . .12 Application . .7 Enterprise . .12 Application integration . .7 Enterprise application integration (EAI) . .12 Application program interface (API) . .7 Enterprise resource planning (ERP) . .12 Archive . .7 Entity . .12 Asset Management . .7 Entity relationship (ER) diagram . .12 Atomic data . .7 Executive information system (EIS) . .13 Authorization request . .7 Extensibility . .13 Bulk data transfer . .7 Geographic information system (GIS) . .13 Business process . .7 Graphical user interface (GUI) . .13 Business process reengineering (BPR) . .7 Information systems architecture . .13 Communications protocol . .7 Interoperable database . .13 Computer Aided Software Engineering (CASE) tools .
    [Show full text]
  • UK Research Data Registry Mapping Schemes
    UK Research Data Registry Mapping Schemes Project Information Project Identifier PID TBC Project Title UK Research Data (Metadata) Registry Pilot Project Hashtag #jiscrdr Start Date 1 October 2013 End Date 31 March 2014 Lead Institution Jisc Project Director Rachel Bruce Project Manager — Contact Email — Partner Institutions Digital Curation Centre (Universities of Edinburgh, Glasgow, Bath); UKDA (University of Essex) Project Webpage URL http://www.dcc.ac.uk/projects/research-data-registry-pilot Programme Name Jisc Capital Programme Document Information Author(s) and Role(s) Alex Ball (Metadata Coordinator) Date 12 May 2014 Project Refs T3.1; D3.1 Filename uk-rdr-mapping-v09.pdf URL http://www.dcc.ac.uk/sites/default/files/documents/ registry/uk-rdr-mapping-v09.pdf Access This report is for general dissemination Document History Version Date Comments 01 29 November 2013 Summary of RIF-CS. First draft of DDI mapping. 02 8 January 2014 Second draft of DDI mapping. First draft of DataCite mapping. 03 22 January 2014 New introduction. Expanded summary of RIF-CS. First draft of EPrints ReCollect, NERC Discovery, and OAI-PMH Dublin Core mappings. 04 23 January 2014 Section on tips for contributors. 05 31 January 2014 Second draft of NERC Discovery (UK GEMINI), EPrints mappings. 06 12 February 2014 Third draft of DDI mapping. 07 18 March 2014 Corrections to all mappings in the light of codification. 08 21 March 2014 First draft of MODS mapping. Registry quality levels included. 09 9 May 2014 Fixed small errors. Added MODS elements to tips section. 1 Contents 1 Introduction 3 1.1 Typographical conventions .
    [Show full text]
  • Week 4 Tutorial - Conceptual Design
    Week 4 Tutorial - Conceptual Design Tutorial 4 – Conceptual Design Remember we can classify an ERDs at one of three levels: 1. Conceptual ERD - an ERD drawing which makes no assumptions about the Data Model which the system will be implemented in 2. Logical ERD (also called a Data Structure Diagram) - an ERD created from the Conceptual ERD which is redrawn in terms of a selected Data Model eg. Relational. The major issues at this stage, if a Relational Data Model is selected, are: relationships are represented by FK's M:N relationships are replaced by 1:M relationships 3. Physical ERD (also represented by a schema file) - an ERD created from the Logical ERD which is redrawn in terms of a selected DBMS eg. Oracle. Most of the issues at this stage of translation will relate to Oracle data types and the Oracle create table/index syntax. Conceptual and Logical ERDs are drawn in terms of a portable ('idealised') data type, now you must translate these types to those supported by your selected DBMS software. For DBMS you may draw ERDs using any of the following (or any combination of the following): (i) using a general drawing package - hand drawn submissions are not acceptable, however you may make use of any standard drawing package to create your diagrams. This approach will support all three ERD levels, you will need to manually make the appropriate translations. (ii) Microsoft VISIO - VISIO is available in the on-campus labs and also available for you (as a Monash student) to install at home. If you wish to install VISIO at home please speak to your lecturer who will explain the local arrangements.
    [Show full text]