WOW!
Let us take a system to store documents. Replace it with a new product.
Have new product more tightly managed.
Do not get direct table access to database. Have views created.
✅Don't get informed that 4 some reason the _ is not a valid column character anymore.
✅Don't get told they randomly switched the database powering this system to a different database w/o said view created
✅Prod go live target t-13 days
✅Prod database view & database name PENDING
What a brilliant system! #NeedADrink
@crazyuncleharris 25 years working ECM systems here. I'm amazed how everyone seems to try recreate what those systems do every 3-5 years. Wait till you need to do some of the other expensive operations that no one ever plans for.
@butch I'm lucky with what I have to do in regards to these systems.
Dump off files in the pickup folder
And then the "verification job"
@crazyuncleharris 21 CFR Part 11 validation for me.
My normal system is usually a collection of 20 or so subsystems to provide support for repository, metadata IAM , workflow, business intelligence, transient vs permanent storage, hierarchical file storage, content migration, bulk loads, bulk unloads, redaction, rendition, data residency, batch management, compliance, audit, and a few other things
All that to do what most people think they can do with just a windows share on a file server.