keyword vocabulary

[dpancic]

In GitLab by @laureD19 on May 20, 2021, 11:07

the keyword property is currently, should be modified to become a concept-based property using the list of values we have at the moment as concepts, but also allowing addition of new concepts.

@vronk is working on a script to collect the values and transform them in skos

[dpancic]

In GitLab by @laureD19 on May 20, 2021, 11:07

added to epic &8

[dpancic]

In GitLab by @laureD19 on May 27, 2021, 15:10

• import in PoolParty - @KlausIllmayer and @vronk
• normalisation and cleaning in PoolParty @martin

[dpancic]

In GitLab by @vronk on May 27, 2021, 15:51

@vronk Current ttl version: https://gitlab.gwdg.de/sshoc/vocabularies/-/blob/feature/keyword_vocabulary/sshoc-keywords/sshoc-keywords.ttl

[dpancic]

In GitLab by @vronk on May 28, 2021, 12:46

Done, needs review: https://gitlab.gwdg.de/sshoc/vocabularies/-/blob/develop/sshoc-keywords/sshoc-keywords.ttl

[dpancic]

In GitLab by @KlausIllmayer on Jun 1, 2021, 18:40

mentioned in issue sshoc-marketplace#66

[dpancic]

In GitLab by @laureD19 on Jul 19, 2021, 17:01

after @aureon249 's curation - thanks a lot for this!! - we now have in PoolParty, 6 top-level concepts to cluster keywords collected so far:

• applications
• country
• disciplines
• language
• organisations
• standards

A few comments after looking at this new list:

• decision needed: when would be the best moment to divert a concept from keyword to another property if we identify a proximity? During the ingest or after ingest via some kind of curation scripts? What about individual creation of item? Could we imagine some kind of suggestion for contributors if they want to suggest a new concept in keyword that already exist in another vocabulary/property? @vronk @KlausIllmayer is there already a dedicated Gitlab issue for that?

• based on the current properties and vocabularies used in the Marketplace (stage instance), concepts clustered under keyword-disciplines, keyword-language and keyword-standards could be mapped and diverted to discipline, language and standards.

• keyword-organisations concepts could be diverted to actors. See also #91

• within keyword-applications, some of the concepts look like actual tools&services items in the Marketplace, so we could use this to suggest relations between items to moderators.

• in general, some values/concepts in keyword seem very close to TaDRIAH concepts and could probably be diverted to activity

All of this would help to further refine the number and the scope of concepts used in keyword.

[dpancic]

In GitLab by @vronk on Sep 2, 2021, 11:24

@KlausIllmayer, Could you reingest the vocabulary, please?

The questions from Laure still need to be discussed. (next meeting on vocabluaries)

[dpancic]

In GitLab by @vronk on Nov 28, 2021, 17:42

marked this issue as related to #17

[dpancic]

In GitLab by @vronk on Jan 31, 2022, 15:14

marked this issue as related to #6

[dpancic]

In GitLab by @laureD19 on Jun 22, 2022, 11:55

spotted by @kreetrapper : "keyword links in the MP (e.g. https://vocabs.dariah.eu/sshoc-keyword/language_resources) currently produce a 404"

@KlausIllmayer I think you are aware of that, but just to keep track of the problem.

[KlausIllmayer]

After quite a long time I managed to move the sshoc-keyword-vocabulary from the wrong place on vocabs.dariah.eu to the correct place on vocabs-common https://vocabs.sshopencloud.eu/browse/sshomp-keyword/

This means, that all of the keywords that can be seen in the vocabulary on vocabs-common can be resolved whereas keywords that were created afterwards are still giving a 404. This is expected, as there is no automatic synchronization between SSHOMP and vocabs-common. The problem is, that it is quite outdated and that we currently have problems when creating an export of the vocabulary form SSHOMP (SSHOC/sshoc-marketplace-backend#396). As long as this issue is not solved - and additionally, it would be good to have the keyword-curation run on production - we can't easily update the vocabulary on vocabs-common.

[KlausIllmayer]

For the record: to move the sshoc-keyword vocabulary from the old namespace to the new namespace it was necessary to process some database queries, as this is a use case that was not foreseen (and usually should not happen). We tested if everything works as expected after doing this database updates on the stage instance and everything seems to work as before. Should there occur errors with the sshoc-keyword vocabulary in the future, it would be necessary to check, if this is connected with the changes in the database:

• changed the entry on sshoc-keyword in the vocabularies-table: changed labels and more important the namespace(s)- and the scheme-uri
• changed the uris of all sshoc-keyword concepts in the concepts-table to the new namespace