5c03e07ded
Simpler story (slide decks unread -> three-bullet status email), proper Claude-chat look with avatars and bubbles on both sides. Canonical trigger prompt switched to English everywhere (homepage, architecture, both adapter generators rebuilt) - V7 consistency green, all checks pass. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PDKeXvpT6tENSvyQGLV1Uq
1.1 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/fecf8a0d-62c4-4e71-9b03-0f4fc2ad7bf5 | data models | essential | 15-1242.00 | model-knowledge | high | 0 | gemma3:27b (prompt-designed and spot-checked by Claude) | 2026-07-10 |
data models — Database Administrator
As a Database Administrator (DBA), 'data models' isn’t about creating them from scratch – that’s usually the data architect’s job. It’s about deeply understanding existing ones and how they impact everything you do. Daily, this means interpreting Entity-Relationship Diagrams (ERDs) or logical/physical data models to troubleshoot performance issues ('why is this query slow?'), plan schema changes ('how will adding this column affect our reporting?'), and ensure data integrity. You'll be using tools like database documentation platforms (e.g., Dataedo, erwin), SQL Developer/Management Studio’s object explorers, or even just digging through the system catalog to visualize relationships.
Weitere Anreicherung
Stage-2 source for future practitioner grounding: arXiv cs.SE (software-engineering preprints).