The JSON schema defining a HEPData submission has provision for a data_licence (comprising a name, url and optional description) for individual tables. It also supports a license for additional resources. An example of use is given in submission.yaml used in TestHEPSubmission.zip and in the submission documentation. By default, the CC0 license applies, as explained in the HEPData Terms of Use.
The database model defines a License object that is used as file_license in the DataResource object. The data_license and license are parsed from the submission.yaml file and persisted to the database in submission.py.
The license information is written in datacite_data_record.xml and in datacite_resource.xml. However, this information is not rendered on the HEPData web pages. In view of potential future specification of licence information by the CMS experiment (@clelange), it should be displayed with the data table metadata, on the "Additional Publication Resources" widget and on the resource file landing page. Only the name needs to be displayed, linked to the url, with the (optional) description given as a tooltip. To avoid clutter, the default CC0 license does not need to be displayed, unless specified explicitly as data_license or license fields in the submission.yaml file.
The JSON schema defining a HEPData submission has provision for a
data_licence
(comprising aname
,url
and optionaldescription
) for individual tables. It also supports alicense
for additional resources. An example of use is given insubmission.yaml
used inTestHEPSubmission.zip
and in the submission documentation. By default, the CC0 license applies, as explained in the HEPData Terms of Use.The database model defines a
License
object that is used asfile_license
in theDataResource
object. Thedata_license
andlicense
are parsed from thesubmission.yaml
file and persisted to the database insubmission.py
.The license information is written in
datacite_data_record.xml
and indatacite_resource.xml
. However, this information is not rendered on the HEPData web pages. In view of potential future specification of licence information by the CMS experiment (@clelange), it should be displayed with the data table metadata, on the "Additional Publication Resources" widget and on the resource file landing page. Only thename
needs to be displayed, linked to theurl
, with the (optional)description
given as a tooltip. To avoid clutter, the default CC0 license does not need to be displayed, unless specified explicitly asdata_license
orlicense
fields in thesubmission.yaml
file.