Is your feature request related to a problem? Please describe.
When a Yoda publication is a restricted access publication, the data is not accessible and only the metadata is shown. The license.txt is part of the data, but as it is a restricted package, it is not viewable (because you can't get to the data where the license.txt resides).
Describe the solution you'd like
Make the license.txtx accessible in either the metadata landing page or separate access to license and data package.
Describe alternatives you've considered
Individuals interested in the license of a restricted package could contact the researcher or support department, but that requires more communication. Another part could be to publish a license openly separately and provide the link to this publication in the restricted access publication metadata (under related resources).
Additional context
Feature request from @DorienHuijser and @NehaMoopen
Is your feature request related to a problem? Please describe.
When a Yoda publication is a restricted access publication, the data is not accessible and only the metadata is shown. The license.txt is part of the data, but as it is a restricted package, it is not viewable (because you can't get to the data where the license.txt resides).
Describe the solution you'd like
Make the license.txtx accessible in either the metadata landing page or separate access to license and data package.
Describe alternatives you've considered
Individuals interested in the license of a restricted package could contact the researcher or support department, but that requires more communication. Another part could be to publish a license openly separately and provide the link to this publication in the restricted access publication metadata (under related resources).
Additional context
Feature request from @DorienHuijser and @NehaMoopen