Data: Skills and Languages (publicId)

[SharonStrats]

Currently it is required to add a Skill or Language it needs to be found on ESCO. The data is stored with publicId. The publicId comes from ESCO. Here is an example of the data for skills.

schema:skills <#id1776236098985>, <#id1776236098986>, <#id1777178831216>; <#id1776236098985> solid:publicId <skill:19a8293b-8e95-4de3-983f-77484079c389>. <skill:19a8293b-8e95-4de3-983f-77484079c389> schema:name "Java (computer programming)".

With skills specifically, ESCO doesn't include all skills that someone might want to add, for instance React, Vue is not there, generic marketing and others.

Would be good to have a way to either add to the ESCO list perhaps, otherwise be able to enter one that is not on the list.

[SharonStrats]

This was discussed in our meeting for now we will allow users to enter their own values not in the search by creating a blank node for the publicId. This is not ideal but will do for the moment. Some suggestions are to create our own catalog of skills, allow the user to add skills and then add them to our catalog (create our own ids for these). In order to do this we need to publish the catalog so that we can write to it.

Another suggestion is to change the way the data is stored to be able to also have schema:name "React" as well as publicId: <skill:id> <skill:id> schema:name "Javascript".

[bourgeoa]

I think leaving skills open to user set their own values is a good idea.