Closed dpancic closed 1 year ago
In GitLab by @laureD19 on May 19, 2021, 13:02
added to epic &8
In GitLab by @laureD19 on May 27, 2021, 14:14
List is actually available via the API: https://api.eosc-portal.eu/vocabulary/byType/COUNTRY
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/geographical-availability/eosc-geographical-availability.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 May 31, 2021, 18:02
PoolParty checks passed and ingested into MP (devel and stage) as vocabulary eosc-geographical-availability
(did some adaptions on code: adding rdfs:comment
for schema and added -original
in the filename).
I let the issue open until it passed the ingest.
In GitLab by @KlausIllmayer on May 31, 2021, 18:52
Open discussion: how is the namespace on vocabs.dariah.eu: Currently it is declared as https://vocabs.dariah.eu/geographical-availability/
but maybe we should go with https://vocabs.dariah.eu/eosc-geographical-availability/
? What is your opinion @vronk?
We also need more information about creators/license/etc. before we can put it on vocabs.dariah.eu
In GitLab by @vronk on May 31, 2021, 23:16
Indeed, in this case, I agree that it makes sens to mark it as EOSC-specific, given the special regions defined.
In GitLab by @vronk on Jun 1, 2021, 08:25
mentioned in commit 65c6638f4cb180510ecb709976b91a4f05a100b9
In GitLab by @KlausIllmayer on Aug 2, 2021, 11:16
The vocabulary can be found here: https://gitlab.gwdg.de/sshoc/vocabularies/-/tree/master/eosc/geographical-availability
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-geographical-availability
In GitLab by @laureD19 on May 19, 2021, 13:02
the
geographical-availability
property is currently a string, should be modified to become a concept-based property using the following list as concepts: https://eosc-portal.eu/providers-documentation/eosc-provider-portal-resource-profile#Resource%20Geographical%20Availability(nb: I didn't find it the list as vocabulary via the API: https://api.eosc-portal.eu/vocabulary/byType)