SolidOS / SolidOS/profile-pane
Data: Skills and Languages (publicId)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 8
- Forks
- 11
- Avg merge
- 4h 19m
- Merged PRs (30d)
- 11
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the profile pane's skill and language entry flow and how ESCO publicId values are stored. Clarify whether the intended result is extending the ESCO list or allowing non-ESCO entries, then define the supported data and interface behavior before implementation. Done means users can add skills such as React, Vue, or generic marketing without breaking existing ESCO-backed entries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100