#  1\. Introduction

This document provides a data management plan (DMP) for the AppHub project.
According to the guidelines of the European Commission [EC13a], “ _the purpose
of the DMP is to support the data management life cycle for all data that will
be collected, processed or generated by the project_ .”

The AppHub project is a Coordination and Support Action that aims on
supporting the development of open source software of European industry, SMEs,
and in particular projects funded by the European Commission towards higher
professionalism regarding development and maintenance processes, higher
software quality, and – ultimately – increased market applicability. To
achieve this objective, AppHub provides a technical platform that will provide
market place services for open source software products (assets):

  * **Directory** : Classification and analysis of open source software with regard to a software taxonomy based on an enterprise computing model. This taxonomy – the Open Interoperability Framework (OIF) - allows to understand purpose and functionalities of software in a unified way. 

  

  * **Factory** : A packaging and deployment feature that allows to model templates and create a virtual run-time environment for software assets, and to deploy them to a wide range of infrastructure service clouds. 

  

  * **Marketplace** : An exposition feature to expose packages created by the Factory as templates or ready-to-use Virtual Machines, which can be directly exploited by end users. 

  

Hence, the data management plan relates to data regarding open source asset
and taxonomy data.

#  2\. Data Management Objectives

The guideline [EC13a] provides a check list of objectives to be taken into
account when defining data management principles. In the following, we are
going to relate out approach to these:  
  
<table>  
<tr>  
<th>

Objective

</th>  
<th>

Description

</th>  
<th>

AppHub actions

</th> </tr>  
<tr>  
<td>

Discoverable

</td>  
<td>

Are the data and associated software produced and/or used in the project
discoverable (and readily located), identifiable by means of a standard
identification mechanism (e.g. Digital Object Identifier)?

</td>  
<td>

The AppHub Directory provides a centralized location for taxonomy data which
can be searched by standard mechanisms (search engines). The AppHub
Marketplace provides a centralized location for software. In addition, REST
APIs are available for automated discovery both for the

AppHub Directory and the Marketplace.

</td> </tr>  
<tr>  
<td>

Accessible

</td>  
<td>

Are the data and associated software produced and/or used in the project
accessible and in what modalities, scope, licenses (e.g. licensing framework
for research and education, embargo periods, commercial exploitation, etc.)?

</td>  
<td>

For taxonomy data, unconditional access is provided. For publications, embargo
periods may apply depending. For software in the Marketplace, the respective
open source license applies.

</td> </tr>  
<tr>  
<td>

Assessable and

intelligible

</td>  
<td>

Are the data and associated software produced and/or used in the project
assessable for and intelligible to third parties in contexts such as
scientific scrutiny and peer review (e.g. are the

</td>  
<td>

Data are collected collaboratively by incorporating projects that produce open
source assets. Classification data are accessible and can be validated with
regard to their correctness and appropriateness. Software in the AppHub

</td> </tr>  
<tr>  
<td>

</td>  
<td>

minimal datasets handled together with scientific papers for the purpose of
peer review, are data is provided in

a way that judgements can be made about their reliability and the competence
of those who created them)?

</td>  
<td>

Marketplace can be executed, and a public review and rating mechanism is
available.

</td> </tr>  
<tr>  
<td>

Useable beyond the original purpose for which it was collected

</td>  
<td>

Are the data and associated software produced and/or used in the project
useable by third parties even long time after the collection of the data (e.g.
is the data safely stored in certified repositories for long term preservation
and curation; is it stored together with the minimum software, metadata and
documentation to make it useful; is the data useful for the wider public needs
and usable for the likely purposes of nonspecialists)?

</td>  
<td>

The AppHub project will not use repositories certificated for long term
storage. Data acquired during the project time frame will be available for a
two year period after the end of the project.

AppHub is intended to be an integral part of the OW2 strategy. Hence, the
project aims on making the AppHub marketplace a sustainable platform for open
source in Europe. Wether data acquired during the project time frame will stay
available under the conditions outlined in this document once the
responsibility for the marketplace operation has been transferred to OW2 will
be decided in the course of the AppHub project.

</td> </tr>  
<tr>  
<td>

Interoperable to specific quality standards

</td>  
<td>

Are the data and associated software produced and/or used in the project
interoperable allowing data exchange between researchers, institutions,
organisations, countries, etc (e.g. adhering to standards for data annotation,
data exchange, compliant with available software applications, and allowing
re-combinations with different datasets from different origins)?

</td>  
<td>

Data can be accessed using web interfaces based on REST/JSON.

Hence, interoperability is provided on the level of data transfer and
exchange.

</td> </tr> </table>

#  3\. Project and Taxonomy Data Sets

Data on open source assets stored in the AppHub Directory provide a
comprehensive description of the capabilities of those assets in term of (a)
activities they support (asset usage), (b) functional characteristics, (c)
standards and technologies used or supported, and (d) cross-concerns that are
addressed by them. Hence, the Directory provides information necessary to
evaluate the usefulness of a certain asset as part of the IT infrastructure of
a potential consumer and allows comparison with other assets.

AppHub is not another Sourceforge. The AppHub platform does not store software
source code, documents, binaries, etc. as such, but provides on-top
information on open source assets that cannot be found at different locations.

###  3.1. Structure

The general structure of the AppHub Directory data is based on the notion of a
project as top-level structural element. Projects subsume all types of
organisational units concerned with the production of open source assets: EC
funded projects, enterprises contributing to open source ecosystems,
universities, etc.

Projects are described be the following information:

  * Title (short and full) 

  

  * Start and end date 

  

  * Logo 

  

  * Web page 

  

  * Contact email 

  

  * List of assets 

  

Each project comprises a list of open source assets:

  * Title 

  

  * Description 

  

  * Tags 

  

  * Asset type (software, knowledge, etc.) 

  

  * Open source license 

  

  * Resources (name, description) 

  

  * OIF classification 

  

At the time of writing this document, the OIF is still under development.
Hence, details will be added to future updates of this document.

###  3.2. Data Collection and Quality

Taxonomy data are collected as a collaborative effort between open source
project and members of the AppHub project consortium. The AppHub Directory
provides a comprehensive dialogue to enter data on projects and assets. The
intention is that project managers provide the OIF classification of the
assets produced by their projects by themselves as part of their contribution
to AppHub. The AppHub consortium is available to assist this activity if
required.

Software data produced by the projects and made available in the AppHub
Marketplace will be subject to potential reviews by end users using the
Marketplace review function.

Hence, data quality is achieved by a continuous dialogue between the projects
and institutions contributing to the AppHub marketplace, and the AppHub
consortium (in particular Fraunhofer).

Moreover, the AppHub project also dedicates a whole work package, WP4 “Quality
and compliance”, to the quality of data provided by projects.

#  4\. Data Sharing

Data of the types described above provided by the AppHub Directory are
available for re-use under

The Directory does not contain material that is related to personal data.
Access statistics are collected using the usual mechanism to monitor web page
access for internal evaluation and project progress assessment.

Software data provided by the AppHub Marketplace are available according to
the respective project licenses, which are, by definition, open source. and
benefit from the qualities of open source software in terms of use. Each
software element retains its respective copyright.

Access to project and asset is also provided via REST APIs. The following
table summarizes the main calls. Results are returns in JSON format (to be
documented in a future update of this document).  
  
<table>  
<tr>  
<th>

_http://directory.apphub.eu.com_ _/api/action/organization_list_

List of all projects that are registered in the AppHub directory

</th> </tr>  
<tr>  
<td>

_http://directory.apphub.eu.com_ _/api/search/dataset?q=organization_
_:PROJECT_NAME_

</td> </tr>  
<tr>  
<td>

Information on the project indicated by PROJECT_NAME including asset list.
Project names can be obtained by the call above.

</td> </tr>  
<tr>  
<td>

_http://directory.apphub.eu.com_ _/action/package_show?id=_ _ASSET_ID_

Information on the asset indicated by ASSET_ID. Asset identifiers can be
obtained by the call above.

</td> </tr> </table>

#  5\. Archiving and preservation

During the project duration, copies of the data stored in the AppHub Directory
are taken every week

(complete data base dumps) and stored at file servers of the Fraunhofer FOKUS
IT infrastructure (which in turned is mirrored on secondary storage media on a
daily basis as part of operational procedures). Copies of these data will be
kept for at least two years after the project finalization. Copies of the data
stored in the AppHub Marketplace and Factory will be taken automatically on a
daily basis (snapshots) and stored at file servers of OVH (the company hosting
the AppHub Factory and Marketplace services).

After the project finalisation the AppHub platform will be maintained by OW2
as part of their support infrastructure for open source projects and will
maintain access to project and taxonomy data as described above (with possible
changes regarding access mechanisms, APIs, protocols, etc.). Procedures for
archiving and preservation of data acquired after the time frame of AppHub are
up to

OW2.

#  6\. Publications and Deliverables

Publications produces in the AppHub project and deliverables (with
dissemination level “public”) after the approval by the European Commission
will be published on the AppHub web site as fast as possible. Hence, AppHub
will provide (gold) open access publishing whenever this is possible [EC13b].

#  7\. Updates

Two major updates of this document are planned:

  * An elaboration of the data structure for taxonomy data once the OIF taxonomy has been defined (month 12 in the AppHub project); 

  

  * Updated conditions for data access as part of the transfer of the responsibility of the AppHub platform operation from Fraunhofer/UShareSoft to OW2.