We have strange URIs for concepts in the sshoc-keyword vocabulary that do have a space in the label, see e.g. https://marketplace.sshopencloud.eu/tool-or-service/1U5uMh and the keyword "word processing" (which could also have a line break inside, looking at the weird representation in the frontend) whose url is "https://vocabs.dariah.eu/sshoc-keyword/word%20processing". But such concepts are not able to be resolved due to the space character. This was the reason, that when a user adds a new concept which has a space character in the label the url will be camelCased. I'm not sure, why this is not the case for "word processing" - looking at the information contributors it is most probably a problem coming from the ingest pipeline. There are some other concepts that look the same.
Need to find out, how such a URI could have been created. We also like to get rid of them as they do not resolve at our vocabulary server.
We have strange URIs for concepts in the sshoc-keyword vocabulary that do have a space in the label, see e.g. https://marketplace.sshopencloud.eu/tool-or-service/1U5uMh and the keyword "word processing" (which could also have a line break inside, looking at the weird representation in the frontend) whose url is "https://vocabs.dariah.eu/sshoc-keyword/word%20processing". But such concepts are not able to be resolved due to the space character. This was the reason, that when a user adds a new concept which has a space character in the label the url will be camelCased. I'm not sure, why this is not the case for "word processing" - looking at the information contributors it is most probably a problem coming from the ingest pipeline. There are some other concepts that look the same.
Need to find out, how such a URI could have been created. We also like to get rid of them as they do not resolve at our vocabulary server.
(was discovered at the backend issue: https://github.com/SSHOC/sshoc-marketplace-backend/issues/396)