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.4 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/fbafa41f-cd05-4109-a649-8b44d306d779 | create data models | essential | 15-1242.00 | model-knowledge | high | 0 | gemma3:27b (prompt-designed and spot-checked by Claude) | 2026-07-10 |
create data models — Database Administrator
As a Database Administrator (DBA), 'creating data models' isn’t about abstract theory; it’s directly tied to building and maintaining functional, performant databases. You won't be leading requirements gathering sessions – that's usually a Business Analyst or Data Architect role – but you will translate those requirements into concrete database designs. This means taking conceptual models (often ER diagrams) and refining them into logical models detailing entities, attributes, relationships, and data types. Then, crucially, you’ll create the physical model: specifying table structures, indexes, constraints, storage parameters, and partitioning schemes optimized for your specific Database Management System (DBMS). Daily tasks include reviewing proposed schema changes, designing tables for new application features, and optimizing existing schemas to address performance bottlenecks.
Weitere Anreicherung
Stage-2 source for future practitioner grounding: arXiv cs.SE (software-engineering preprints).