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/3d03c40c-1b83-4793-8902-2523f40af59e | Microsoft Access | optional | 15-1242.00 | model-knowledge | medium | 0 | gemma3:27b (prompt-designed and spot-checked by Claude) | 2026-07-10 |
Microsoft Access — Database Administrator
For a Database Administrator (DBA), 'Microsoft Access' competence isn’t about building production databases – that’s SQL Server, Oracle, PostgreSQL etc.'s domain. It's about rapid prototyping, data analysis for troubleshooting, and providing self-service tools to end-users who need limited database access without impacting core systems. A DBA might quickly build an Access front-end connected to a SQL Server backend to allow business analysts to run specific reports or perform ad-hoc queries without granting them direct SQL Server permissions. They'll also use it for importing/exporting small datasets for testing, validating ETL processes, and occasionally reverse-engineering poorly documented legacy systems.
Weitere Anreicherung
Stage-2 source for future practitioner grounding: arXiv cs.SE (software-engineering preprints).