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
2.5 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/a57a54b6-2f2e-43e4-9621-b52f4a63cb08 | LDAP | optional | 15-1242.00 | model-knowledge | high | 0 | gemma3:27b (prompt-designed and spot-checked by Claude) | 2026-07-10 |
LDAP — Database Administrator
As a Database Administrator, 'LDAP' isn’t about writing LDAP queries as much as it's understanding how databases integrate with directory services like Active Directory or OpenLDAP for authentication and authorization. Daily tasks often involve configuring database connections to use LDAP for user account verification – ensuring only authorized users can access sensitive data. You'll be troubleshooting failed logins stemming from LDAP connectivity issues, verifying group memberships are correctly mapped to database roles (e.g., 'db_datareader', 'db_datawriter'), and potentially scripting updates to LDAP attributes that impact database permissions. Think of it as the gatekeeper before someone even reaches your database.
Typical tools include ldapsearch for basic testing, Active Directory Users and Computers/OpenLDAP management interfaces for attribute inspection, and database-specific connection string configuration panels (e.g., in SQL Server Management Studio or pgAdmin). A common pitfall is misconfigured DNs (Distinguished Names) leading to authentication failures, or incorrect schema mappings between LDAP groups and database roles – resulting in users having either too much or not enough access. Another issue is network connectivity; a simple ping isn't enough - you need to verify DNS resolution and port 389/636 accessibility.
Good LDAP competence for a DBA looks like proactively monitoring LDAP connection health, understanding the implications of changes in the directory service on database security, and being able to quickly diagnose authentication problems. It’s about knowing where to look for issues (LDAP logs, network traces) and how to interpret the errors. It also means collaborating effectively with system administrators who manage the LDAP infrastructure.
Finally, while the ESCO definition focuses on 'query language', DBAs rarely write complex LDAP queries directly. They focus on consuming the information provided by LDAP – leveraging existing tools and configurations to secure database access based on directory service data.
Weitere Anreicherung
Stage-2 source for future practitioner grounding: arXiv cs.SE (software-engineering preprints).