Replies: 4 comments 2 replies
-
@genedan funny you mention it because I actually already implemented the entire PCDM schema with DBML back in March just out of curiosity and exploration. Here's the relevant links:
I agree with how you approached the documentation / observability side of the data model and from past experience with generating many data models and having to clearly document them for a variety of stakeholders (unfortunately all for clients so not shareable). I left some notes outlining my workflow at the bottom of this comment. Notes:
My Data Model Documentation WorkflowI typically document the data model using
I tie it all together with Docker and a root I can sift through my old work projects and find some examples if you think they could be useful. Lastly, I have also implemented a preliminary openapi specification for the model as well using JSONSchema for the components and some demo endpoints to do various insurance related things, but its tough to work with being such a large model (the final compiled openapi specification was like 150,000 lines long in YAML). Let me know if you would be interested in this also. |
Beta Was this translation helpful? Give feedback.
-
Also, I already have an example embedding of the dbdiagram in my online knowledge base here: DbDiagram Embed - PCDM - KaaS - Obsidian Publish. PS: All the information above is from the same Obsidian Vault also. |
Beta Was this translation helpful? Give feedback.
-
This looks so beautiful and well documented for open-source contribution. |
Beta Was this translation helpful? Give feedback.
-
Hey @jimbrig, thanks for the super-informative post, much of this information will be handy. I would like to link to your diagram via the PCDM repo to be the official documentation, instead of the stub docs site I created a while back. It really is what I imaged the documentation to be - interactive with detailed descriptions on what the tables and attributes are. Is this DBML code for your PCDM diagram stored in a repository anywhere? |
Beta Was this translation helpful? Give feedback.
-
I have been thinking about ways to document the FASLR backend database. Using Sphinx seemed simple enough, but it has its drawbacks, like having to rearrange the ER diagrams, manually fill out metadata tables, and lack of interactivity.
I came across this project which led me down the route of looking for third-party solutions:
https://dbdocs.io/jimbrigf0cdc6204e/Actuarial-Database
This was made using dbdocs and it looks pretty slick and you can drag and drop the tables in the ER diagram. The downside is there is no self-hosted solution, but I guess we can keep an eye out if one ever emerges, because I do like how it looks. @jimbrig, I would be curious to hear your thoughts on ease of use and how well it integrates with your project - or if you've encountered other similar tools that might be useful.
A self-hosted solution is desirable for me, since I would like to keep everything as open source as possible and under the same domain name, so I came across schemaspy I gave it a go and here's the resulting page for the db:
https://faslr.com/db/
The resulting diagrams aren't movable but you can visit relevant documentation by clicking on the tables, so it seems good enough for now. I'll have to figure out how to replace the dot notation name with just FASLR as well.
Beta Was this translation helpful? Give feedback.
All reactions