- we probably have v1 at this moment
- current version: v.1
- goal version: v1.2.1
-
Skill ↔ Skill relations
- ESCO has these:
- broaderSkill
- narrowerSkill
- relatedSkill
- replacedBy
- replaces
- I suggest that it is sufficient to work only with replaced and replaces information - SCKSnapshot.changeType ensures it
- Could relations broaderSkill and narrowerSkill serve for L1-L3 structure?
Versions
- delta files
- only for: v1.0 → v1.1 → v1.2
- not for: v1.1.0 → v1.1.1
- uri remain same - use as originKey
- ESCO use change types: released, deprecated, replacedBy
Import algorithm
- prerequisites
- must be able to receive delta csv files
- delta files contain documenting of every change between versions (skill change, addition, deletion etc.)
- must be able to - described in my external draw.io documentation
- not important - could be able to receive queue of these files and be able to select which delta file will cause the new skills record creation and which are used just for move between versions (can be just final file in queue)
My questions (in terms of implementation):
- how to link SCK with L1-L2.5 and is it necessary to do?
CURRENT STEPS:
- download all delta files ✓
- from SCKToExternalSystem records set uri as SCK originKey ✓
-