***NONE**: Does not export the software artifact in the target, but each software artifact is elaborated without effectively exporting it. It is a dry run.
This JSON contains two properties at the top level:
*``configuration`` : a JSON Object that contains the ``processors`` configuration list mentioned above and a set of properties to be used as default for each artifact;
*``artifacts``: a JSON Array containing the artifact's list to be processed.
In this example, the artifacts property comprises different versions of the same software, but different artifacts can be processed together.
As the reader can notice, a property defined can be used as a variable inside the value of another.
For example
..code-block:: JSON
{
"title": "gCube Catalogue (gCat) Service {{version}}"
}
The ``title`` value will be evaluated while analyzing the artifact.
Please note that there is no right place to define a property.
Please remember that the metadata contained in the global configuration is merged with the artifact's metadata.
If the same property has been defined, the value of the artifact specification is used (it is more specific).
After the merge, the values containing references to other values are replaced.
For this reason, the title for gcat 1.0.0 will be ``gCube Catalogue (gCat) Service 1.0.0``.
As you can see from the example, the Concept DOI of gcat 1.X.X differs from the concept DOI for gcat 2.X.X
This means that Zenodo will have two different concepts, each with different versions.
Moreover, the group for gcat 1.X.X is ``data-publishing`` which differs from the default value coming from the global configuration, which is ``data-catalogue``.
ZenodoExporter
--------------
At the end of the processing phase, the library produces a file containing:
* the configuration (JSON Object);
* the list of software artifacts described by their metadata (JSON Array) with actualized output.
Please note that for each entry there are three braces ``author = {{{author}}}``
The first two are printed as they are because of the bib format, and the third is used as a variable container, as done in values of the JSON properties.