Skip to content
programavimas.xyz docs

Skill vocabulary

Keeping the problem archive's list of skills – areas and skills in both languages, order and archiving.

Problems in the archive are classified by skill: what the problem practises, such as Loops › while loops. The skills come from one list for the whole platform, of two levels: areas (Loops, Files, Arrays…) and the skills in each. System administrators keep the list; teachers only choose from it for the problems they edit (see Skills, difficulty and source in the staff guide).

The list is in Administration → Skills, which only system administrators see; for everyone else, including organisation admins, the page doesn’t exist.

The table shows each area with its skills under it (click the arrow to fold an area):

  • the Lithuanian and English names: the app shows each person the one in their interface language;
  • Problems: how many problems have the skill, whoever owns them. The number links to the archive filtered by that skill.

Above the table: how many skills are in use, and how many problems have none yet, with a link to those problems (No skill in the archive). In use and Archived switch between entries in use and archived ones.

Action Where Notes
New area New area in the header Goes to the end of the list.
New skill The area’s ⋯ → New skill in this area… Goes to the end of the area.
Rename an area The area’s ⋯ → Rename…
Rename a skill, or move it to another area The skill’s ⋯ → Edit… A moved skill goes to the end of the new area; problems keep it.
Change the order ⋯ → Move up / Move down Areas among areas, skills within their area. The order is the order of the archive’s filter and of the skill pickers.

Both names are required, up to 80 characters. Two areas, or two skills of one area, can’t share a name in use (in either language, ignoring case).

  • An entry nothing uses can be deleted: a skill no problem has, an area without skills. Use it for mistakes.
  • An entry in use can only be archived. Problems keep an archived skill (marked as archived on the problem page), but it is no longer offered for problems and leaves the archive’s filters. Editors can still take it off a problem.
  • Archiving an area takes all its skills out of use with it.
  • Restore brings an entry back from Archived. A skill of an archived area comes back only with its area.

Each choice explains its effect before you confirm. If a teacher gives a skill to a problem while you are deleting it, the deletion fails and the skill can only be archived.

Every change is recorded in the audit trail (skill.* and skill_area.* events, with ids only).

Problems brought over from the old system arrive already classified: the curriculum’s numbered topic folders became eight areas with eighteen skills, and exam and olympiad folders set the problems’ source. Problems from other folders (contests, and folders without a curriculum number) are left to classify, for example with Skills… and Source… on a selection in the archive.