The schema validation is only intend to enforce/validate a schema definition and not populate values.
The server does not have an ability to set default values and we recommend users to set it in their data access application layer or use ODM’s to set those values on the application side.
If you use Atlas you can consider having a trigger on the collection to update every inserted document with a specific filed value.
Just wanted to confirm, this is still accurate. Collection schemas have no mechanism to provide default field values for inference on new records? Instead one can enforce defaults at the client or API level.