Abstract

Abstract

Abstract

Abstract
The effort of generating large city scenes is greatly reduced when using procedural modelling techniques. Nonetheless. users are limited to defining rules and tuning parameters in a define-generation reanalyse cycle, reducing direct control. Describing buildings with split-based operations may disrupt the creative process by forcing the user to focus on how to describe a building instead of how a building should look. We use planar shapes and two-dimensional boo lean operations allowing procedural descriptions that are More aligned with humans' perceptions of buildings while letting users directly manipulate shapes (e.g., by dragging) in an interactive application.

Abstract
In many institutions relational databases are used as a tool for managing information related to day to day activities. Institutions may be required to keep the information stored in relational databases accessible because of many reasons including legal requirements and institutional policies. However, the evolution in technology and change in users with the passage of time put the information stored in relational databases in danger. In the long term the information may become inaccessible when the operating system, database management system or the application software is not available any more or the contextual information not stored in the database may be lost thus affecting the authenticity and understandability of the information. This paper presents an approach for preserving relational databases for the long-term. The proposal involves migrating a relational database to a dimensional model which is simple to understand and easy to write queries against. Practical transformation rules are developed by carrying out multiple case studies. One of the case studies is presented as a running example in the paper. Systematic implementation of the rules ensures no loss of information in the process except for the unwanted details. The database preserved using the approach is converted to an open format but may be reloaded to a database management system in the long-term.

Abstract
Research data management is acknowledged as an important concern for institutions and several platforms to support data deposits have emerged. In this paper we start by overviewing the current practices in the data management workflow and identifying the stakeholders in this process. We then compare four recently proposed data repository platforms-DSpace, CKAN, Zenodo and Figshare-considering their architecture, support for metadata, API completeness, as well as their search mechanisms and community acceptance. To evaluate these features, we take into consideration the identified stakeholders' requirements. In the end, we argue that, depending on local requirements, different data repositories can meet some of the stakeholders requirements. Nevertheless, there is still room for improvements, mainly regarding the compatibility with the description of data from different research domains, to further improve data reuse.