Slims V9 Db Structure
SLiMS 9 Bulian database structure guide for reading, documenting, tracing, and explaining the SQL schema. Use this skill to understand SLiMS v9 table purposes, follow relationships between bibliography, item, member, circulation, master, OPAC search, and admin tables, map SQL fields to library workflows, or explain schema details from the raw SQL.
Install
$ agentstack add skill-prisma-ddti-skills-slims-v9-db-structure ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
SLiMS v9 DB Structure
Quick Start
- Confirm the target is SLiMS 9 Bulian.
- Read [references/schema-overview.md](references/schema-overview.md) before writing SQL, documentation, or integration notes.
- Switch to
dspace-v6-db-structureif the task is about DSpace, not SLiMS.
Working Rules
- Identify the business area first: catalog, copies, loans, members, settings, search, or admin.
- Find the core table before expanding to bridge and lookup tables (e.g.,
biblio_author,biblio_topic,mst_*). - Treat
senayan.sqlas the authoritative baseline. - Treat table relationships as logical (application-enforced), not database-enforced FK constraints — many tables use
MyISAM. - Separate bibliographic records (
biblio= title/work) from physical copies (item= exemplar). - Decode coded fields via master tables (
mst_*) instead of guessing their meaning. - Prefer structural explanation over speculative business logic. If a column purpose is unclear, say so.
- Check denormalized tables (
search_biblio,loan_history) only after understanding the core transaction tables. - Some fields store serialized values or JSON — note this before proposing direct SQL changes.
Bundled Resource
references/schema-overview.md: Table families, key fields, relationship map, and storage caveats from the officialsenayan.sql.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: prisma-ddti
- Source: prisma-ddti/skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.