Ingest NeMO ActivityType vocabulary

[dpancic]

In GitLab by @vronk on Oct 22, 2019, 14:50

ActivityType taxonomy (available under http://nemo.dcu.gr/index.php?p=navigate# - tab [Type taxonomies] ) is a derivative of TaDIRAH and primary candidate vocabluary for the ActivityType dimension.

It is now available in RDF form under: https://github.com/athenarc/nemo/blob/master/SO_ActivityTypes_v.1.3.owl (strangely not in SKOS) The plan is to ingest it to https://vocabs.dariah.eu (under ACDH-OEAW control), where it would be available via API and as SKOS.

I will exchange with Panos on the further procedure. If the "proper way" (SKOS + vocabs.dariah.eu) should take to long, we can take some shortcut.

(notify: @tparkola, @laureD19, @vronk, @KlausIllmayer, @clara.petitfils, @vronk)

[dpancic]

In GitLab by @vronk on Dec 6, 2019, 15:52

changed due date to November 01, 2019

[dpancic]

In GitLab by @vronk on Oct 22, 2019, 14:50

changed due date to November 01, 2019

[dpancic]

In GitLab by @vronk on Oct 22, 2019, 14:50

marked this issue as related to sshoc-marketplace#31

[dpancic]

In GitLab by @vronk on Oct 22, 2019, 17:54

Could this make the trick?

NemoActivityType.ttl

Is it a requirement to have Dereferenceable URIs for Vocabularies? These could be available through PP API as well.

[dpancic]

In GitLab by @vronk on Oct 23, 2019, 12:59

Yes, this looks good! (though did not validate yet) Did you do a conversion from the OWL to SKOS via PP?

[dpancic]

In GitLab by @vronk on Oct 23, 2019, 13:03

Yes, through a UV pipeline. Tested it with qSKOS and successfully imported on a demo server of PP.

[dpancic]

In GitLab by @vronk on Oct 23, 2019, 13:15

great. is the the demo server available?

As said this would be our primary candidate for ingestion. @tparkola not sure what we agreed upon? Would you accept the RDF/SKOS as input, or shall we use the API to ingest the vocabulary? I.e. have a script (or some component in UV/PP) to read the SKOS and write to MP-API/vocabulary ?

[dpancic]

In GitLab by @tparkola on Oct 24, 2019, 08:07

I think it's a good idea to import vocabularies in SKOS and ttl. We will have order in our vocabularies. I can implement import from this format next week.

API methods for adding/modifying a vocabulary should take such file in http body or in multipart/form-data (uploading a file). I can implement two versions. In case of modification, the whole vocabulary in the system would be created from scratch, if it's possible. If there were references to concepts already assigned to items and these concepts wouldn't be present in the new ttl file, the modification would not succeed.

It's also good to have a method that will read such SKOS and ttl files from configuration at system boot and call the same service used by API for adding vocabularies to system. I will start from it next week.

[dpancic]

In GitLab by @tparkola on Oct 24, 2019, 09:34

mentioned in issue sshoc-marketplace#31

[dpancic]

In GitLab by @tparkola on Nov 20, 2019, 13:37

mentioned in issue sshoc-marketplace-backend#5

[dpancic]

In GitLab by @vronk on Dec 6, 2019, 15:52

moved from sshoc-marketplace#36

[dpancic]

In GitLab by @vronk on Dec 13, 2019, 19:17

There is now also another version of the ActivityType in SKOS/TTL generated by the NeMO people directly (Vicky Dritsou): https://github.com/acdh-oeaw/nemo/blob/master/SO_ActivityTypes_v.1.3(SKOS_version).ttl

it differs from what Sotiris generated: https://github.com/acdh-oeaw/nemo/blob/master/ActivityType_SSHOC_NeMO.diff

(mainly mappings to TaDiRAH are added!) Given that they are the authoritative source and has more information, we should switch to that one.

[dpancic]

In GitLab by @KlausIllmayer on Apr 29, 2020, 11:38

Mapping document of NeMO to TaDiRAH: http://nemo.dcu.gr/material/tadirah-nemo-mapping.pdf

Further mappings are on the NeMO resources webpage http://nemo.dcu.gr/resources/ (section mappings)

[dpancic]

In GitLab by @vronk on Oct 25, 2021, 15:18

We use TaDiRAH2 for activities. We won't ingest NeMO Vocabulary for now.