-
Notifications
You must be signed in to change notification settings - Fork 0
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
Curate licenses in tapor data #4
Comments
In GitLab by @vronk on Oct 30, 2019, 14:57 marked this issue as related to sshoc-marketplace#38 |
In GitLab by @vronk on Oct 30, 2019, 14:57 marked this issue as related to sshoc-marketplace#29 |
In GitLab by @laureD19 on Jan 23, 2020, 14:08 removed milestone |
In GitLab by @vronk on Jan 23, 2020, 14:22 Ideally this should already happen as curation task in the application. However if the curation-module implementation takes too, we could do this offline in a separate table. To be clarified what would be the most efficient mode for the curation. |
In GitLab by @KlausIllmayer on Oct 16, 2020, 18:40 @aureon249 created in data-ingestion@33f1fdb451f3c9e0b9ab2b90bb66c45b818b34be a csv-document that maps the licenses of random chosen tools from Tapor to the ones from the vocabulary. It gives also insights about the success rate of finding the precise license |
In GitLab by @egray523 on Feb 24, 2021, 18:03 added to epic &8 |
In GitLab by @laureD19 on May 17, 2021, 19:14 mentioned in issue sshoc-marketplace#84 |
In GitLab by @vronk on Oct 26, 2022, 15:42 moved from sshoc-marketplace#37 |
In GitLab by @vronk on Oct 30, 2019, 14:42
There is a problem with tapor data regarding licensing: they only have information about license type, not the specific license.
We take the information as it is in tapor (in a separate property @license-type@).
However ideally, we need information about the precise license under which given resource is available.
This requires a separate curation work, where we revisit the tools and fill the specific license.
(notify: @laureD19, @vronk, @KlausIllmayer, @vronk, @clara.petitfils, @vronk)
The text was updated successfully, but these errors were encountered: