Closed dpancic closed 1 year ago
In GitLab by @laureD19 on May 19, 2021, 13:11
added to epic &8
In GitLab by @vronk on May 28, 2021, 12:42
mentioned in commit 2e5199c51119cfb82e8b48c2891759654916a32a
In GitLab by @vronk on May 28, 2021, 12:48
Done, needs review https://gitlab.gwdg.de/sshoc/vocabularies/-/blob/develop/eosc/life-cycle-status/eosc-life-cycle-status.ttl
In GitLab by @KlausIllmayer on May 28, 2021, 14:09
mentioned in commit f9a06c2eeb4811bd9931201ae4bf3ce29aeeb7fb
In GitLab by @vronk on May 31, 2021, 08:59
Reopened, until it is double checked and passes poolparty checks as well
In GitLab by @KlausIllmayer on Jun 10, 2021, 10:31
mentioned in issue sshoc-marketplace#66
In GitLab by @KlausIllmayer on Jun 10, 2021, 12:28
I now have ingested the eosc-life-cycle-status-vocabulary on the stage instance. When looking into it, I was wondering why the concept name has the prefix "life_cycle_status", e.g. https://vocabs.dariah.eu/eosc-life-cycle-status/life_cycle_status-alpha whereas for eosc-geographical-availabilty there is no such prefix, e.g. https://vocabs.dariah.eu/eosc-geographical-availability/ad
Is there a special reason behind this decision? I'm not sure about the best practice here but maybe we should agree on the same approach (be it with or without prefix). What is your opinon?
In GitLab by @vronk on Jun 10, 2021, 13:20
The only reason is that the API provides this information, so https://api.eosc-portal.eu/vocabulary/byType/LIFE_CYCLE_STATUS gives you id="life_cycle_status-alpha"
, etc... And the https://api.eosc-portal.eu/vocabulary/byType/COUNTRY gives only id="AD"
.
In GitLab by @KlausIllmayer on Jun 10, 2021, 13:23
makes sense - then the common approach is to take the values from the api. thanks for feedback
In GitLab by @KlausIllmayer on Aug 2, 2021, 11:22
The vocabulary can be found here: https://gitlab.gwdg.de/sshoc/vocabularies/-/tree/master/eosc/life-cycle-status
It is derived from EOSC website and uses a Python tool from Yoann that transforms the data from there to SKOS. The SKOS is ingested into PoolParty, exported from there and ingested into MP identified by code eosc-life-cycle-status
In GitLab by @laureD19 on May 19, 2021, 13:11
the
life-cycle-status
property is currently a string, should be modified to become a concept-based property using the following list as concepts: https://api.eosc-portal.eu/vocabulary/byType/LIFE_CYCLE_STATUS