S1000D CSDB: Source Data, References, Versions and Publication Control
A Common Source Database (CSDB) is the controlled source-data environment for technical publications. It manages more than XML files: identities, relationships, states, versions, rules and delivery evidence.
What does a CSDB manage?
| Object | Why it matters |
|---|---|
| Data Modules | Reusable technical information with identity, status and content. |
| Media and ICNs | Controlled illustrations, graphics, video, audio and hotspots. |
| BREX and code lists | Business rules and permitted values used during validation. |
| References and PM/DMRef | Links that assemble source objects into a publication. |
| Versions, states and audit records | Evidence of review, approval, change impact and delivery baseline. |
A typical CSDB workflow
- Check out or create a controlled object.
- Author and validate against Schema and business rules.
- Review technical content, references, media and applicability.
- Approve and baseline the required objects.
- Assemble a PM and generate the agreed delivery package.
CSDB selection should be based on object identity, version control, review workflow, permissions, auditability, validation integration, import/export and offline delivery needs.
Related reading: Data Modules, validation and publication applicability.
Scope note: Product features vary. A CSDB capability must be confirmed against the project’s information model, security requirements and acceptance criteria.
Frequently asked questions
Is a CSDB just a folder of XML files?
No. A CSDB also manages identities, relationships, states, versions, rules, permissions, review and publication records.
Does every CSDB use the same database technology?
No. CSDB is a set of technical-publication management capabilities; implementations may use different storage architectures.