Thank you, @twier and @diana, for your prompt and insightful responses. We really appreciate the information.
To offer some context on our project structure: we incorporate the CHT as a submodule within our project. During the build process, we apply our custom patches to the CHT code, subsequently creating Docker images or hosting the components via Node.js (on Azure it works a little different, but I’ll get into that on the appropriate thread). We do not perform upgrades through the site; in fact, I believe this is restricted on Nginx. When updating our submodule, we undertake a meticulous patch review process. In theory, the views and indexes we create should persist. For instance, we’ve modified the “contacts_by_freetext” and “contacts_by_type_freetext” views to address issues related to duplicate data capture, as discussed in this thread:
That said, we aim to maintain alignment with the CHT as much as possible and are intrigued by the prospect of uploading indexes through cht-conf.
Due to other pressing commitments, we won’t have the time to delve into this work just yet. As an interim measure, I attempted to create a view to facilitate backend requests with a similar outcome. However, the view did not upload as expected. I added ‘doc_by_id_and_type’ to medicDB/medic/views/, but upon checking Fauxton locally, it appeared that this view was not present in the database. Am I overlooking something in this process?