Differences

This shows you the differences between two versions of the page.

--- documentation:partb2dmp [2015/03/29 23:39] – jcsuarez
+++ documentation:partb2dmp [2015/03/29 23:46] (current) – jcsuarez
@@ Line 1: / Line 1: @@
+==== Data Management Plan ====
+**2.2.1.3 Data (and workflow and Research Object) management plan.** This section provides a skeleton of the initial data management plan (DMP) to be produced and applied in PERSIA (D1.4, M06). This DMP refers not only to the raw and processed spaced-based and ground-based legacy data or experiment results handled by the involved communities, but also the new scientific data and software documentation created within the project, the contents of the knowledge base and, in summary, any Research Objects constructed in the context of the experiments carried out by the members of PERSIA consortium.
+The types of elements that we are interested in managing are data (from legacy and generated by the consortium), scientific documents (papers, scientific reports, etc.), and software application documentation (for optimum usage by the community and general public). Therefore, we use an extended Data Management Plan, such as to include all these Research Objects (see Table 2.9)
+**Table 2.9: Elements to be considered in the initial Data Management Plan**
+|^Administrative Data ||
+|^Reference |PERSIA   Knowledge Base (DMP) |
+|^Principal   Investigator |Juan Carlos   Suárez |
+|^Related   Policies |Existing Data Management Plans for the data that will be handled by existing portals and VO archives   and by the involved research groups will be respected in PERSIA. This DMP focuses on the   additional PERSIA data that will be generated and will need to be handled and   stored in the knowledge base. |
+|^Data Collection   and Creation ||
+|^Data that will be collected. |Data products generated in the PERSIA project, namely Time series corrected for gaps (WP1); Catalogue of frequencies and amplitudes   (WP1); Catalogue of asteroseismic indices (WP2);Grid of 2D models (WP3); Collection of raw and reduced spectra   (WP6); Catalogue of physical parameters (WP6). In addition to this we will provide links to external datasets of interest for the  project.  |
+|How will the   data be collected? |Data will be   generated by the different working groups. WP5 will supervise the data   generation process to ensure that the data formats and associated metadata   comply with the Virtual Observatory standards and requirements.  |
+|^Documentation,   standards and metadata ||
+|What   documentation, standards and metadata will accompany the data? |Each working   group will properly document the data collections under its responsibility.   Required metadata will be defined by the associated VO data models. In   addition to the web access, VO standard access protocols (SSAP,   ConeSearch,...) will be used to query the PERSIA archive. |
+|How will data   be shared? |The PERSIA   archive will be VO-compliant and it will be included in the VO registries.   This will greatly ease the discovery and access of the PERSIA data   collections. |
+|Are any   restrictions on data sharing required? |During the   operational phase of the project, the access to data collections will be   restricted to PERSIA partners only. After the end of the project, data   collections will become public for the use of the international astronomical   community and the general public. |
+|What is the   long-term preservation plan for the data? |Long-term   preservation of PERSIA data is guaranteed. Data will be archived in the   astronomical data center hosted at Centro de Astrobiología (Madrid, Spain).   This is the largest astronomical data center managed by a Spanish   institution. |
+|How will data   be stored and backed up during the research? |The   archives and data collections available at the CAB Scientific Data Centre   reside in a secure, stable, tested, and well-documented environment. PERSIA   data will be backup on a periodic basis. Monitor services for availability   will be developed to warn about any failure in the systems. In case of   failure, the service’s responsible will be notified by e-mail. Failing   services will be diagnosed, remedial action taken and services restarted. All   such actions will be logged. |
+\\