DOCSLIB.ORG

Dissemination Plan

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Dissemination Plan Deliverable 1.3 Open Data technological study Author(s): Paul Hermans (ProXML) Editor(s): Paul Hermans (ProXML) Responsible Organisation: ProXML Version-Status: V1 Final Submission date: 30/09/2016 Dissemination level: PU Disclaimer This project has been funded with support from the European Commission. This deliverable reflects the views only of the author, and the Commission cannot be held responsible for any use which may be made of the information contained therein. This project has been funded with the support of the Erasmus+ programme of the European Union Copyright by the ODEdu Consortium . D1.3 Open Data technological study Deliverable factsheet Project Number: 562604-EPP-1-2015-1-EL-EPPKA2-KA Project Acronym: ODEdu Project Title: Innovative Open Data Education and Training based on PBL and Learning Analytics Title of Deliverable: D1.3 – Open Data technological study Work package: WP1 – Stakeholders needs regarding Open Data Due date according to contract: 30/09/2016 Editor(s): Paul Hermans (ProXML) Contributor(s): UOM Reviewer(s): AcrossLimits Approved by: All Partners Abstract: This document presents an inventory of tools available for publishing and reusing Open Data. The study carried out towards this objective took into consideration the Open Data Lifecycle and the curriculum structure that were designed and proposed in the previous two deliverable of the current Work Package. Furthermore, the report performs assessment on teach technology and provides recommendations of the identified tools for each target group (persona) considered in the context of the project. The most important finding is that the majority of the Open Data Lifecycle phases can be covered easily with even multiple valid choices so that curriculum building can leverage this. Keyword List: Open data tool, open data portal, data wrangling, descriptive analytics, prescriptive analytics Page 2 of 119 D1.3 Open Data technological study Consortium Role Name Short Name Country 1. Coordinator , academic University of Macedonia UOM Greece partner 2. Open Data expert Open Data Institute ODI UK 3. Problem Based Aalborg University AAU Denmark Learning expert 4. Technology enhanced AcrossLimits AcrossLimits Malta learning expert 5. Dissemination partner Association of Information Technology SEPVE Greece Companies of Northern Greece 6. Open / Linked Data ProXML ProXML Belgium technologies expert 7. Local Authorities Linked Organisation of Local Authorities LOLA Belgium partner Page 3 of 119 D1.3 Open Data technological study Revision History Version Date Revised by Reason 0.1 01/08/2016 ProXML Initial list of open data technologies and tools 0.2 03/08/2016 ProXML Description of tools 0.3 17/08/2016 ProXML First roundup 0.4 22/08/2016 ProXML Tool Parts reviewed 0.4b 24/08/2016 UOM Provision of feedback 0.5 26/08/2016 ProXML Integration of feedback 0.6 31/08/2016 ProXML More evaluation wording 0.7 19/09/2016 ProXML Integration of partners’ feedback 0.8 19/09/2016 ProXML Executive summary + conclusion 1 26/09/2016 ProXML Final 1 30/09/2016 UOM Submission of deliverable Statement of originality: This deliverable contains original unpublished work except where clearly indicated otherwise. Acknowledgement of previously published material and of the work of others has been made through appropriate citation, quotation or both. Disclaimer This project has been funded with support from the European Commission. This deliverable reflects the views only of the author, and the Commission cannot be held responsible for any use which may be made of the information contained therein. Page 4 of 119 D1.3 Open Data technological study Table of Contents DELIVERABLE FACTSHEET ...................................................................................................................2 CONSORTIUM ....................................................................................................................................3 REVISION HISTORY .............................................................................................................................4 TABLE OF CONTENTS ..........................................................................................................................5 LIST OF FIGURES .................................................................................................................................8 LIST OF TABLES ..................................................................................................................................9 LIST OF ABBREVIATIONS ................................................................................................................... 10 EXECUTIVE SUMMARY ..................................................................................................................... 11 1 INTRODUCTION ........................................................................................................................ 12 1.1 SCOPE .................................................................................................................................................... 12 1.2 AUDIENCE............................................................................................................................................... 12 1.3 STRUCTURE ............................................................................................................................................. 12 2 METHODOLOGY........................................................................................................................ 13 3 DEFINITIONS ............................................................................................................................. 14 4 TECHNOLOGIES AND TOOLS SELECTION ..................................................................................... 16 4.1 INTRODUCTION ........................................................................................................................................ 16 4.1.1 Lifecycle and curriculum based ....................................................................................................... 16 4.1.2 Technological constraints ............................................................................................................... 16 4.1.3 License constraints .......................................................................................................................... 16 4.2 OPEN DATA LIFECYCLE .............................................................................................................................. 17 4.3 TECHNOLOGIES AND TOOLS RELATED TO THE OPEN DATA LIFECYCLE ................................................................... 18 4.3.1 Publish ............................................................................................................................................. 18 4.3.2 Reuse ............................................................................................................................................... 20 4.3.3 Summary ......................................................................................................................................... 22 4.4 CURRICULUM SKELETON ............................................................................................................................ 22 4.5 TOOLS RELATED TO THE CURRICULUM SKELETON ............................................................................................ 25 4.5.1 Introduction .................................................................................................................................... 25 4.5.2 Filtering out sensitive data.............................................................................................................. 25 4.5.3 Deduplication of similar records/rows ............................................................................................ 25 4.5.4 Dashboard software ....................................................................................................................... 26 4.5.5 Storytelling ...................................................................................................................................... 26 4.5.6 Big Data .......................................................................................................................................... 26 4.5.7 Statistical Data ................................................................................................................................ 26 4.5.8 Linked Data ..................................................................................................................................... 26 Page 5 of 119 D1.3 Open Data technological study 5 TOOLS DESCRIPTION ................................................................................................................. 27 5.1 OPEN DATA PORTAL SOFTWARE ................................................................................................................. 27 5.1.1 Positioning in the Open Data Lifecycle ............................................................................................ 27 5.1.2 CKAN ............................................................................................................................................... 28 5.1.3 OpenDataSoft Open Data Solution ................................................................................................. 32 5.1.4 Socrata Open Data .........................................................................................................................
Load more

Recommended publications
  • This Book Doesn't Tell You How to Write Faster Code, Or How to Write Code with Fewer Memory Leaks, Or Even How to Debug Code at All
    Practical Development Environments By Matthew B. Doar ............................................... Publisher: O'Reilly Pub Date: September 2005 ISBN: 0-596-00796-5 Pages: 328 Table of Contents | Index This book doesn't tell you how to write faster code, or how to write code with fewer memory leaks, or even how to debug code at all. What it does tell you is how to build your product in better ways, how to keep track of the code that you write, and how to track the bugs in your code. Plus some more things you'll wish you had known before starting a project. Practical Development Environments is a guide, a collection of advice about real development environments for small to medium-sized projects and groups. Each of the chapters considers a different kind of tool - tools for tracking versions of files, build tools, testing tools, bug-tracking tools, tools for creating documentation, and tools for creating packaged releases. Each chapter discusses what you should look for in that kind of tool and what to avoid, and also describes some good ideas, bad ideas, and annoying experiences for each area. Specific instances of each type of tool are described in enough detail so that you can decide which ones you want to investigate further. Developers want to write code, not maintain makefiles. Writers want to write content instead of manage templates. IT provides machines, but doesn't have time to maintain all the different tools. Managers want the product to move smoothly from development to release, and are interested in tools to help this happen more often.
    [Show full text]
  • David's Advanced Revision Control System
    Hazırlık Darcs Hakkında Pratik Okuma Odevi¨ David’s Advanced Revision Control System Can Burak C¸ilingir1 1Istanbul˙ Bilgi Universitesi¨ Bilgisayar Bilimleri B¨ol¨um¨u [email protected] 5 S¸ubat 2007 Can Burak C¸ilingir Darcs Hazırlık Darcs Hakkında Versiyon Y¨onetimi Pratik Ge¸cmi¸s Okuma Odevi¨ Ne zaman bitecek? 1 Hazırlık Versiyon Y¨onetimi Ge¸cmi¸s 2 Darcs Hakkında 3 Pratik 4 Okuma Odevi¨ Can Burak C¸ilingir Darcs Hazırlık Darcs Hakkında Versiyon Y¨onetimi Pratik Ge¸cmi¸s Okuma Odevi¨ neye yarar? Can Burak C¸ilingir Darcs Hazırlık Darcs Hakkında Versiyon Y¨onetimi Pratik Ge¸cmi¸s Okuma Odevi¨ Aegis, ArX, Arch, BitKeeper, CM Synergy, CVS, Code Co-Op, Codeville, IBM Rational ClearCase, Mercurial, Monotone, OpenCM Perforce, PureCM, RCS, Subversion, Superversion, Vesta, Visual SourceSafe, bazaar-ng, git, monotone, svk http://better-scm.berlios.de/comparison/ http://zooko.com/revision control quick ref.html Can Burak C¸ilingir Darcs Hazırlık Darcs Hakkında Versiyon Y¨onetimi Pratik Ge¸cmi¸s Okuma Odevi¨ Aegis, ArX, Arch, BitKeeper, CM Synergy, CVS, Code Co-Op, Codeville, IBM Rational ClearCase, Mercurial, Monotone, OpenCM Perforce, PureCM, RCS, Subversion, Superversion, Vesta, Visual SourceSafe, bazaar-ng, git, monotone, svk http://better-scm.berlios.de/comparison/ http://zooko.com/revision control quick ref.html Can Burak C¸ilingir Darcs Hazırlık Darcs Hakkında Versiyon Y¨onetimi Pratik Ge¸cmi¸s Okuma Odevi¨ rcs Revision Control System, tek ki¸si cvs Concurrent Versioning System, birden fazla ki¸si svn Subversion, daha d¨uzg¨un
    [Show full text]
  • Bill Laboon Friendly Introduction Version Control: a Brief History
    Git and GitHub: A Bill Laboon Friendly Introduction Version Control: A Brief History ❖ In the old days, you could make a copy of your code at a certain point, and release it ❖ You could then continue working on your code, adding features, fixing bugs, etc. ❖ But this had several problems! VERSION 1 VERSION 2 Version Control: A Brief History ❖ Working with others was difficult - if you both modified the same file, it could be very difficult to fix! ❖ Reviewing changes from “Release n” to “Release n + 1” could be very time-consuming, if not impossible ❖ Modifying code locally meant that a crash could take out much of your work Version Control: A Brief History ❖ So now we have version control - a way to manage our source code in a regular way. ❖ We can tag releases without making a copy ❖ We can have numerous “save points” in case our modifications need to be unwound ❖ We can easily distribute our code across multiple machines ❖ We can easily merge work from different people to the same codebase Version Control ❖ There are many kinds of version control out there: ❖ BitKeeper, Perforce, Subversion, Visual SourceSafe, Mercurial, IBM ClearCase, AccuRev, AutoDesk Vault, Team Concert, Vesta, CVSNT, OpenCVS, Aegis, ArX, Darcs, Fossil, GNU Arch, BitKeeper, Code Co-Op, Plastic, StarTeam, MKS Integrity, Team Foundation Server, PVCS, DCVS, StarTeam, Veracity, Razor, Sun TeamWare, Code Co-Op, SVK, Fossil, Codeville, Bazaar…. ❖ But we will discuss git and its most popular repository hosting service, GitHub What is git? ❖ Developed by Linus Torvalds ❖ Strong support for distributed development ❖ Very fast ❖ Very efficient ❖ Very resistant against data corruption ❖ Makes branching and merging easy ❖ Can run over various protocols Git and GitHub ❖ git != GitHub ❖ git is the software itself - GitHub is just a place to store it, and some web-based tools to help with development.
    [Show full text]
  • ARX Log Catalog
    ARX Log Catalog 810-0029-00 Publication Date This manual was published on September 18, 2012. Legal Notices Copyright Copyright 2005-9/18/12, F5 Networks, Inc. All rights reserved. F5 Networks, Inc. (F5) believes the information it furnishes to be accurate and reliable. However, F5 assumes no responsibility for the use of this information, nor any infringement of patents or other rights of third parties which may result from its use. No license is granted by implication or otherwise under any patent, copyright, or other intellectual property right of F5 except as specifically described by applicable user licenses. F5 reserves the right to change specifications at any time without notice. Trademarks 3DNS, Access Policy Manager, Acopia, Acopia Networks, Advanced Client Authentication, Advanced Routing, APM, Application Security Manager, ARX, AskF5, ASM, BIG-IP, Cloud Extender, CloudFucious, Clustered Multiprocessing, CMP, COHESION, Data Manager, DevCentral, DevCentral [DESIGN], DSI, DNS Express, DSC, Edge Client, Edge Gateway, Edge Portal, ELEVATE, EM, Enterprise Manager, ENGAGE, F5, F5 [DESIGN], F5 Management Pack, F5 Networks, F5 World, Fast Application Proxy, Fast Cache, FirePass, Global Traffic Manager, GTM, GUARDIAN, IBR, Intelligent Browser Referencing, Intelligent Compression, IPv6 Gateway, iApps, iControl, iHealth, iQuery, iRules, iRules OnDemand, iSession, IT agility. Your way., L7 Rate Shaping, LC, Link Controller, Local Traffic Manager, LTM, Message Security Module, MSM, Netcelera, OneConnect, OpenBloX, OpenBloX [DESIGN], Packet
    [Show full text]
  • Introduction to Software Configuration Management
    Introduction to Software Configuration Management CprE 556 Electrical and Computer Engineering Department Iowa State University 1 Example Initially, implementation is in Modula-2 on a Mac. A11 B11 A12 B12 A13 2 Example Next: a variant for Pascal is needed. Component B does not differ for the Pascal and Modula-2. But component A needs a variant. 3 Example A11 B11 A12 B12 A13 Modula Pascal A131 A132 4 Example Next: a variant of component B is needed for Sun and Mac implementations, where component A is believed identical for Mac and Sun. 5 Example A11 B11 A12 B12 Mac Sun A13 B121 B122 Modula Pascal A131 A132 + In Modula for Mac, A131 and B121 + In Pascal for Mac, A132 and B121 + In Modula for Sun, A131 and B122 6 Example After development of some revisions, it turns out that component A must be implemented differently on both machines, and component B has to be developed in two variants according to the programming languages. 7 Component A A11 A12 A13 Modula Pascal A131 A132 Mac Sun A1311 A1321 A1322 Mac Sun A13111 A13112 8 Component B B11 B12 Mac Sun B121 B122 Pascal Modula B1211 B1212 B1221 Pascal Modula B12211 B12212 9 Important concepts Configuration management or configuration control The management of a system through control of changes made to hardware, software, firmware, documentation, test, test fixtures and test documentation of an automated information system, throughout the development and operational life of a system. 10 Important concepts Software configuration management concerns the storage of the entities produced during the software development project.
    [Show full text]
  • Why Use Bazaar Instead Of
    Version Version Management Management with Bazaar with Bazaar Outline Joakim Joakim Lindblad Lindblad Motivation Motivation Example Example Looking Version Management with Bazaar Looking deeper deeper Getting A helping hand for tracking changes in your les Getting What is Bazaar? started started Cooperating Cooperating What is Bazaar good for? More stu More stu A small sample session Joakim Lindblad Conclusions Conclusions [email protected] Getting started with Bazaar More features. Centre for Image Analysis Conclusions 2007-10-29 Version Version Management Management with Bazaar What is Bazaar? with Bazaar What is version control? Joakim Joakim Lindblad Lindblad Motivation Motivation Example Example http://en.wikipedia.org/wiki/Revision_control Looking Looking deeper deeper Getting Getting started started Revision control (also known as version control (system) (VCS), http://bazaar-vcs.org/ Cooperating Cooperating source control or (source) code management (SCM)) is the More stu More stu management of multiple revisions of the same unit of Conclusions Bazaar is a distributed version control system available Conclusions information. under the GPL that reduces barriers to participation in your In computer software engineering, revision control is any project. practice that tracks and provides control over changes to source code. Software tools for revision control are increasingly recognized as being necessary for the organization of multi-developer projects. Version Version Management Management with Bazaar What is version control good for? with Bazaar Why use Bazaar instead of. ? Joakim Joakim Lindblad Lindblad Motivation A version control system keeps a history of the changes made to Motivation Example a set of les. Example Looking Looking deeper It answers questions like: deeper Getting Getting started What has happened with this project since last week? started Cooperating Who changed what and when? Cooperating More stu More stu CVS, Subversion (svn), Visual SourceSafe, .
    [Show full text]
  • DVCS Or a New Way to Use Version Control Systems for Freebsd
    DVCS or a new way to use Version Control Systems for FreeBSD Ollivier ROBERT <[email protected]> 11th May 2006 Abstract FreeBSD, like many open source projects, uses CVS as its main version control system (VCS), which is an extended history of all modifications made since the beginning of the project in 1993. CVS is a cornerstone of FreeBSD in two ways: not only does it record the history of the project, but it is a fundamental tool for coordinating the development of the FreeBSD operating system. CVS is built around the concept of centralised repository, which has a number of limitations. Recently, a new type of VCS has arisen: Distributed VCS, one of the first being BK from Bit- Mover, Inc. Better known from the controversy it generated when Linus Torvalds started using it, it has nonetheless changed the way some people develop software. This paper explores the area of distributed VCS. We analyse two of them (Arch in its Bazaar[1] incarnation and Mercurial[2] and try to show how such a tool could help further FreeBSD devel- opment, both as a tool and as a new development process. 1 Introduction 2 A brief history of VCS 2.1 Ancestors FreeBSD[3] has been using CVS as its main ver- sion control system (VCS) tool for as long as it ex- At the beginning, the main tools used to manage ists and has now more than 10 years of history. A different versions of software were pretty prim- few years ago, limitations inherent in CVS design itive but it was enough for most people during became too much to workaround and the project early stages of development and large pieces of begun using Perforce[4] for projects that needed software were developed using SCCS or later, to change fast without “polluting” the main tree.
    [Show full text]
  • Distributed Development with Bazaar
    Overview An extremely flexible tool Example: the management of ABINIT The end Distributed development with Bazaar Yann Pouillon 1. Facultad de Químicas, Universidad del País Vasco UPV/EHU, Donostia-San Sebastián, Spain. 2. European Theoretical Spectroscopy Facility (ETSF), Spain. CECAM Tutorial — Zaragoza, Spain 2010/06/21 Overview An extremely flexible tool Example: the management of ABINIT The end Outline 1 Overview An evolutionary process Quick tour of Bazaar 2.1 2 An extremely flexible tool Keeping up with an evolving project Popular Bazaar workflows 3 Example: the management of ABINIT Sustaining the growth of the code The ABINIT Forge Overview An extremely flexible tool Example: the management of ABINIT The end Outline 1 Overview An evolutionary process Quick tour of Bazaar 2.1 2 An extremely flexible tool Keeping up with an evolving project Popular Bazaar workflows 3 Example: the management of ABINIT Sustaining the growth of the code The ABINIT Forge Overview An extremely flexible tool Example: the management of ABINIT The end Different times, different challenges, different models 1970’s: first steps (SCCS times) VCS = tool to keep history of single files weave method: uniform data retrieval time outcome: SCCS adopted by Unix 1980’s: from solo to team work (RCS times) independent streams of development project management & VCS decoupled outcome: data retrieval efficiency & reliability 1990’s: organizing collaboration (CVS times) golden age of client-server model uprising of the centralized model outcome: atomicity, file management, deployment
    [Show full text]
  • Održavanje Softvera
    ODRŽAVANJE SOFTVERA DEFINICIJA “The process of modifying a software system or component after delivery to correct faults, improve performance or other attributes, or adapt to a changed environment” • 40-90% of the software life cycle cost Osnovne faze razvoja softvera: Uloga odrzavanja u celom zivotnom ciklusu softvera: TIPOVI ODRZAVANJA: Faze razvoja i elementi održavanja u agilnom razvoju softvera: Grupe aktivnosti u održavanju softvera (izvor: Alain April, Jane Huffman Hayes, Alain Abran, and Reiner Dumke: Software Maintenance Maturity Model (SMmm): The software maintenance process model) (izvor: http://www.klariti.com/technical-writing/2011/08/26/software-maintenance-plan/) There are two sides to Software Maintenance Plans – management and technical. Management issues include aligning with customer priorities, resources, setting up maintenance teams, and costs. Technical issues include impact analysis, testing, maintainability measurement. Software Maintenance includes ten activities: 1. Preparation – Describe software preparation and transition activities including the conception and creation of the maintenance plan; describe how to handle problems identified during development and configuration management. 2. Modification – After the application has become the responsibility of the maintenance team, explain how to analyze each request; confirm and check validity; investigate and propose solutions; document the proposal and get the required authorizations to apply the modifications. 3. Implementation – Describe the process for considering the implementation of the modification itself. 4. Acceptance – Describe how the modification is accepted by the maintenance team. 5. Migration – Describe any migration tasks that need to be executed. If the software needs to be moved to another system, outline the steps to do so without impacting its functionality. 6. Transition – Document the sequence of activities to transition the system from Development to Maintenance.
    [Show full text]
  • Metadefender Core V4.15.0
    MetaDefender Core v4.15.0 © 2018 OPSWAT, Inc. All rights reserved. OPSWAT®, MetadefenderTM and the OPSWAT logo are trademarks of OPSWAT, Inc. All other trademarks, trade names, service marks, service names, and images mentioned and/or used herein belong to their respective owners. Table of Contents About This Guide 11 Key Features of MetaDefender Core 12 1. Quick Start with MetaDefender Core 13 1.1. Installation 13 Operating system invariant initial steps 13 Basic setup 14 1.1.1. Configuration wizard 14 1.2. License Activation 19 1.3. Process Files with MetaDefender Core 19 2. Installing or Upgrading MetaDefender Core 20 2.1. Recommended System Requirements 20 System Requirements For Server 20 Browser Requirements for the Metadefender Core Management Console 22 2.2. Installing MetaDefender 22 Installation 22 Installation notes 23 2.2.1. Installing Metadefender Core using command line 23 2.2.2. Installing Metadefender Core using the Install Wizard 25 2.3. Upgrading MetaDefender Core 25 Upgrading from MetaDefender Core 3.x 25 Upgrading from MetaDefender Core 4.x 26 2.4. MetaDefender Core Licensing 26 2.4.1. Activating Metadefender Licenses 26 2.4.2. Checking Your Metadefender Core License 33 2.5. Performance and Load Estimation 34 What to know before reading the results: Some factors that affect performance 34 How test results are calculated 35 Test Reports 35 Performance Report - Multi-Scanning On Linux 35 Performance Report - Multi-Scanning On Windows 39 2.6. Special installation options 42 Use RAMDISK for the tempdirectory 42 3. Configuring MetaDefender Core 46 3.1. Management Console 46 3.1.1.
    [Show full text]
  • Version Control an Essential Tool for Collaborative Software Development
    Version Control An Essential Tool for Collaborative Software Development Philipp Haller Associate Professor School of Electrical Engineering and Computer Science KTH Royal Institute of Technology DD2480 Software Engineering Fundamentals 17 January, 2020 About Myself • 2006 Dipl.-Inform. Open source activities: Karlsruhe Institute of • Member of Scala language Technology (KIT), Germany team 2006—2014 Creator of Scala’s first 2010 Ph.D. in Computer • • widely-used actor library Science Co-author of futures and Swiss Federal Institute of • promises in Scala Technology Lausanne (EPFL) • Co-author of Scala’s async/ await extension • Held positions at Typesafe, Inc., Stanford University, and EPFL • Since Dec 2014 at KTH A Large Open-Source Project • Example: Scala programming language • Many {users, contributors, commits, releases, …} Challenges of Collaborative Software Development • Several developers extending/changing the same code base concurrently • How to integrate multiple, possibly conflicting changes? • How to track ownership of changes to code and documents? • Development and maintenance of multiple major versions in parallel • Maintain previous major versions through bug fixes (e.g., v3.0 -> v3.1) • In parallel, develop new feature or next major version v2.1.4 -> v2.1.5, v2.1.x -> v2.2.0 • Unambiguous identification of a revision/stable release • Each revision of each file/directory/resource etc. Version Control • Version control = practices and tools that provide control over changes to source code and other documents • Synonyms: revision
    [Show full text]
  • Distributed Version Control and Why You Want to Use It
    KIT Distributed version control and why you want to use it Matthias Vogelgesang Institute for Data Processing and Electronics 0 Oct. 17ᵗʰ 2013 M. Vogelgesang - Distributed version control and why you want to use it Institute for Data Processing and Electronics KIT – University of the State of Baden-Wuerttemberg and National Research Center of the Helmholtz Association www.kit.edu . “Here is the latest version of the proposal/paper/report.” — “Thanks.” “One of these folders must contain the latest version …” KIT Plead guilty! It’s easy to copy digital content, so why not re-create it over and over again? 1 Oct. 17ᵗʰ 2013 M. Vogelgesang - Distributed version control and why you want to use it Institute for Data Processing and Electronics . “Here is the latest version of the proposal/paper/report.” — “Thanks.” KIT Plead guilty! It’s easy to copy digital content, so why not re-create it over and over again? “One of these folders must contain the latest version …” 1 Oct. 17ᵗʰ 2013 M. Vogelgesang - Distributed version control and why you want to use it Institute for Data Processing and Electronics . KIT Plead guilty! It’s easy to copy digital content, so why not re-create it over and over again? “Here is the latest version of the proposal/paper/report.” — “Thanks.” “One of these folders must contain the latest version …” 1 Oct. 17ᵗʰ 2013 M. Vogelgesang - Distributed version control and why you want to use it Institute for Data Processing and Electronics . KIT Obvious disadvantages . No meta data about what was changed when by whom . You lose track of what’s going on .
    [Show full text]