An Editorial Workflow Approach For Collaborative Ontology Development

The widespread use of ontologies in the last years has raised new challenges for their development and maintenance. Ontology development has transformed from a process normally performed by one ontology engineer into a process performed collaboratively by a team of ontology engineers, who may be geographically distributed and play different roles. For example, editors may propose changes, while authoritative users approve or reject them following a well defined process. This process, however, has only been partially addressed by existing ontology development methods, methodologies, and tool support. Furthermore, in a distributed environment where ontology editors may be working on local copies of the same ontology, strategies should be in place to ensure that changes in one copy are reflected in all of them. In this paper, we propose a workflow-based model for the collaborative development of ontologies in distributed environments and describe the components required to support them. We illustrate our model with a test case in the fishery domain from the United Nations Food and Agriculture Organisation (FAO)

An integrated approach to preparing, publishing, presenting and preserving theses

[Abstract]: This paper describes progress on a project funded by the Australian government to create Free software; the Integrated Content Environment for research and scholarship (ICE-RS). ICE-RS is a multi-faceted project which will add value to finished theses by making them available in both HTML and PDF, as well as providing a mechanism for packaging multimedia theses. The project will also concentrate on providing services for thesis production, with version control, automated backup and collaboration services. The paper begins with the established content management system that is the basis for the project, ICE-RS , originally developed to create courseware packages. ICE includes distributed, version controlled collaboration, using word processing software and works on multiple platforms, with standard document formats. We survey other approaches to content authoring and publishing for ETDs. We showcase exploratory work on integration of the thesis writing process with Institutional Repository software including publishing theses in both PDF and HTML with preservation and descriptive metadata. The presentation will include demonstrations of thesis production at all stages of development from proposal to completion. In a more speculative vein, we will discuss opportunities for institutions to provide new levels of support for candidates via automated thesis “dashboard” progress reports, supervisor and examiner annotation and comment and support for copyright considerations as early as possible in the process

Git4Voc: Git-based Versioning for Collaborative Vocabulary Development

Collaborative vocabulary development in the context of data integration is the process of finding consensus between the experts of the different systems and domains. The complexity of this process is increased with the number of involved people, the variety of the systems to be integrated and the dynamics of their domain. In this paper we advocate that the realization of a powerful version control system is the heart of the problem. Driven by this idea and the success of Git in the context of software development, we investigate the applicability of Git for collaborative vocabulary development. Even though vocabulary development and software development have much more similarities than differences there are still important differences. These need to be considered within the development of a successful versioning and collaboration system for vocabulary development. Therefore, this paper starts by presenting the challenges we were faced with during the creation of vocabularies collaboratively and discusses its distinction to software development. Based on these insights we propose Git4Voc which comprises guidelines how Git can be adopted to vocabulary development. Finally, we demonstrate how Git hooks can be implemented to go beyond the plain functionality of Git by realizing vocabulary-specific features like syntactic validation and semantic diffs

The Future of Aquatic Commons: Recommendations Based on an Evaluation of Business Models and Stakeholder Consultation

Aquatic Commons is a digital repository established by the International Association of Aquatic and Marine Libraries and Information Centers (IAMSLIC) in 2007 to provide a solution for member institutions that didn’t have an institutional repository. It is directed by the Aquatic Commons Board, and submissions are reviewed by an editorial team. Originally hosted by the Florida Center for Library Automation (FCLA), the repository was moved to the International Oceanographic Data and Information Exchange (IODE) in 2011 when FCLA faced major budgetary issues. Aquatic Commons has grown to more than 20,000 publications from over 90 institutions in all areas of the aquatic sciences, including freshwater, fisheries, and oceanography, yet support for the repository has not kept pace with developmental needs. To ensure a sustainable future, the Aquatic Commons Board determined it was necessary to conduct an evaluation and created the Aquatic Commons Evaluation (ACE) team. The team identified and compared four potential business models: 1a) maintain Aquatic Commons as a separate repository but upgrade the EPrints software; 1b) maintain Aquatic Commons as a separate repository but migrate to DSpace software; 2) migrate content to the existing IODE OceanDocs repository but retain Aquatic Commons identity by having a separate DSpace community; and 3) partner with IODE and possibly the Aquatic Science and Fisheries Abstracts (ASFA) to create an entirely new repository with content merged from Aquatic Commons and OceanDocs. The team consulted with potential partners (e.g. ASFA and IODE) and ran a survey to elicit feedback from members, depositors, and other stakeholders about the models, addressing issues of thematic scope, branding, software, technical requirements, workflows, and training. At the 2019 conference, the team presented a recommendation based on the evaluation in order to initiate a roadmap for the Aquatic Commons

Leveraging HTC for UK eScience with very large Condor pools: demand for transforming untapped power into results

We provide an insight into the demand from the UK eScience community for very large HighThroughput Computing resources and provide an example of such a resource in current productionuse: the 930-node eMinerals Condor pool at UCL. We demonstrate the significant benefits thisresource has provided to UK eScientists via quickly and easily realising results throughout a rangeof problem areas. We demonstrate the value added by the pool to UCL I.S infrastructure andprovide a case for the expansion of very large Condor resources within the UK eScience Gridinfrastructure. We provide examples of the technical and administrative difficulties faced whenscaling up to institutional Condor pools, and propose the introduction of a UK Condor/HTCworking group to co-ordinate the mid to long term UK eScience Condor development, deploymentand support requirements, starting with the inaugural UK Condor Week in October 2004

D3.1. Architecture and design of the platform

This document aims to establish the requirements and the technological basis and design of the PANACEA platform. These are the main goals of the document: - Survey the different technological approaches that can be used in PANACEA. - Specify some guidelines for the metadata. - Establish the requirements for the platform. - Make a Common Interface proposal for the tools. - Propose a format for the data to be exchanged by the tools (Travelling Object). - Choose the technologies that will be used to develop the platform. - Propose a workplan