HCL Domino Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
In general not a bad idea. But I am wondering about the use case when you speak about "en masse" import.
What use case do you have in mind?
In general the JSON format isn't that helpful for complex documents. But OTS is mainly designed to bring up your server, create databases from templates. change the ACL etc.
Changing or adding documents is mainly intended for configuration updates, setting up applications.
It's a single JSON file that configures your server. It sounds like you are looking into a bit different use case, where you would need to provde DXL files separately. And this might be better suited in your application setup, which could also run on an existing server and would be called during OTS configuration.
OTS supports signing and running agents for that purpose.
Also I don't see why you need DXL files if you could provide a template/database with those documents.