added development status to the guidelines

mirima2 · Dec 19, 2017 · e455fad · e455fad
1 parent ac18a01
commit e455fad
Show file tree

Hide file tree

Showing 2 changed files with 30 additions and 2 deletions.
diff --git a/docs/source/field_developmentStatus.rst b/docs/source/field_developmentStatus.rst
@@ -0,0 +1,27 @@
+.. _oas:developmentStatus:
+
+23. Distribution form (O)
+====================
+
+``datacite:description``
+
+Description of development status, e.g. Active, inactive, supsended. See `repostatus.org <http://www.repostatus.org/>`_ 
+
+23.1 type (M)
+-------------------
+
+Specifies the kind of information presented in the element (occurrences: 1)
+
+**Usage Instruction**
+
+This element is used to specify the development status of the software. The descriptionType must be set to the OpenAIRE term "DevelopmentStatus".
+
+**Example**
+
+.. code-block:: xml
+   :linenos:
+
+   <description descriptionType="DevelopmentStatus">
+     Suspended 
+   </description>
+
diff --git a/docs/source/introduction.rst b/docs/source/introduction.rst
@@ -13,7 +13,7 @@ Infrastructure for Research in Europe. These guidelines are intended to provide
 The metadata from software archives should be included in the OpenAIRE information space and exposed when:
 
 	* the software is an open source research software, 
-	* the software is related to a publication or a dataset already in OpenAIRE e.g. a software referred by an open access article
+	* the software is related to a publication or a dataset already in OpenAIRE e.g. a software referred by an open access article,
 	* the software is linked to a project. 
 
 By implementing the OpenAIRE Guidelines, software archive managers are facilitating the creation of enhanced publications and building the stepping-stones for a linked data infrastructure for research.
@@ -22,7 +22,7 @@ Exposure and visibility of content from a range of European repositories will be
 
 
 
-The Guidelines take inspiration from DataCite, on the side of citation metadata, and from the `OpenMinTed SHARE-OMTD <https://guidelines.openminted.eu/guidelines_for_providers_of_sw_resources/recommended_schema_for_sw_resources.html>`_ software guidelines
+The Guidelines take inspiration from DataCite, on the side of citation metadata, from the `OpenMinTed SHARE-OMTD <https://guidelines.openminted.eu/guidelines_for_providers_of_sw_resources/recommended_schema_for_sw_resources.html>`_ software guidelines, and from the `Codemeta initiative < https://github.com/codemeta/codemeta/blob/master/crosswalk.csv>`_ 
 
 
 
@@ -34,6 +34,7 @@ Acknowledgements & Contributors
 * Miriam Baglioni (CNR, Italy)
 * Alessia Bardi (CNR, Italy)
 * Paolo Manghi (CNR, Italy)
+* Leo Mack (JISC, UK)
 
 
 **Experts & Reviewers**