Blocking for now.

Can describe more about how the configuration will work and discuss the pros/cons of the structure map approach. The problem I see with in code is that whether a code approach works is tightly coupled to how the Questionnaires are written, so having this in code does not provide guarantees it will work, it is still the content creators responsibility, i.e. by having this in code we're splitting the responsibility.

Blocking for now.

Can describe more about how the configuration will work and discuss the pros/cons of the structure map approach. The problem I see with in code is that whether a code approach works is tightly coupled to how the Questionnaires are written, so having this in code does not provide guarantees it will work, it is still the content creators responsibility, i.e. by having this in code we're splitting the responsibility.

@pld after our discussion I am updating this ticket to change the acceptance criteria to deliver the following

1. Documentation on how to link locations tied to Entities during the Entity creation (CHW & HF).
   • This includes some sample StructureMaps to generate the Entity and the LIST resource that links the Location to the Entity
2. Documentation on how to create Locations and later link them to the Entities (MIcroPlanning).
   • This includes some sample StructureMaps to generate the Entity and the LIST resource that links the Location to the Entity

@Wambere can pick this up once she is done with her current assignments.

@ellykits this means we do not need to handle the linkage automatically via code.

This sounds good, is it possible to have tooling that checks the location generation structure map you've written aligns with the format we expect for locations and their linking resources?

This sounds good, is it possible to have tooling that checks the location generation structure map you've written aligns with the format we expect for locations and their linking resources?

I think we can. @Wambere thoughts?