6b3b2abe4f
73 stackexchange-grounded, 516 model-knowledge (ESCO-seeded gemma3), 0 review_needed (calibration caveat documented). Adapters rebuilt with the full competence sets; final REPORT numbers; all verify checks pass. Known gap: engineering-manager lacks an ESCO package counterpart. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PDKeXvpT6tENSvyQGLV1Uq
1.2 KiB
esco_uri, esco_label, relation, onet_soc, source, confidence, qa_count, generator, generated
| esco_uri | esco_label | relation | onet_soc | source | confidence | qa_count | generator | generated |
|---|---|---|---|---|---|---|---|---|
| http://data.europa.eu/esco/skill/ab67fbfb-0ca7-4345-8bf6-af8f59480212 | design database backup specifications | essential | 15-1242.00 | model-knowledge | high | 0 | gemma3:27b (prompt-designed and spot-checked by Claude) | 2026-07-10 |
design database backup specifications — Database Administrator
As a Database Administrator, 'design database backup specifications' isn’t just choosing a backup tool; it's architecting a data safety net tailored to each database's criticality and recovery needs. Daily this means translating business Recovery Point Objectives (RPO - how much data loss is acceptable) and Recovery Time Objectives (RTO - how long can the system be down) into concrete backup strategies. You’ll define things like full, differential, incremental backups – frequency for each, retention periods, where backups are stored (on-site, off-site, cloud), and compression/encryption settings. It's about balancing cost with risk; frequent backups mean faster recovery but higher storage costs.
Weitere Anreicherung
Stage-2 source for future practitioner grounding: arXiv cs.SE (software-engineering preprints).