Difference between revisions of "Zenodo Publication"
From Gcube Wiki
(→Automatic Metadata Generation) |
(→7. Keywords) |
||
| Line 12: | Line 12: | ||
#keywords=keyword1, keyword 2, key word3, ... | #keywords=keyword1, keyword 2, key word3, ... | ||
</pre> | </pre> | ||
| − | + | ||
| + | If keywords are not found in the component, they are searched in the subsystem and if also in the subsystem are not found, the keywords for the project are used. org.gcube project define these keywords: | ||
| + | <pre> | ||
| + | #keywords=gCube, Java, Data Management System, Hybrid Data Infrastructure | ||
| + | </pre> | ||
| + | |||
== Command line client usage == | == Command line client usage == | ||
TODO | TODO | ||
Revision as of 14:02, 29 November 2016
Contents
Motivation
TODO
Automatic Metadata Generation
7. Keywords
Keywords for each component are stored in ETICS in the the description field of the corresponding ETICS module (not the configuration). For instance, keywords for "Common Authorization" are stored in the description of "org.gcube.common.authorization-common" module. They are encoded as follow:
#keywords=keyword1, keyword 2, key word3, ...
If keywords are not found in the component, they are searched in the subsystem and if also in the subsystem are not found, the keywords for the project are used. org.gcube project define these keywords:
#keywords=gCube, Java, Data Management System, Hybrid Data Infrastructure
Command line client usage
TODO
Possible Improvements
- Add Changelog in the description
- Add links to wiki (parsed from the README)
- Support for a ".zenodo" file in the projet root that override metadata generated automatically
- More metadata can be added:
- Subjects (however Subjects does not appear in Zenodo)
