Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

records: display license information if specified #740

Closed
GraemeWatt opened this issue Dec 11, 2023 · 1 comment · Fixed by #745
Closed

records: display license information if specified #740

GraemeWatt opened this issue Dec 11, 2023 · 1 comment · Fixed by #745
Assignees

Comments

@GraemeWatt
Copy link
Member

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.

@clelange
Copy link

Thanks for following up on this!

CC @lenzip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants