-
Notifications
You must be signed in to change notification settings - Fork 8
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
[BUG] RO-Crate export missing MUST fields #472
Comments
There are some available APIs to query against: When searching for license scanning and gitlab this popped up: |
Yes, this can be done in the CI-Pipeline. Can you point me to an example RO-Crate containing a license? |
I think we don't have any example yet, @j-bauer. But as I said I could insert this as an argument in the arc-export tool, so you would only need to provide this when calling the export |
|
Correct, PR #488 changed I guess we should also change |
Yup makes sense to change them to name 👍 Would leave the Assay as is atm, maybe we actually align it more with the study, see nfdi4plants/ARC-specification#86 |
The investigation object in the RO-Crate export does not necessarily have a
license
andname
field, however, they are required by the RO-Crate specification.Could the gitlab CI detect an existing license and insert it into the arc export command? @j-bauer
The text was updated successfully, but these errors were encountered: