Agape-Apps: Building Baruch Together

[Jonathan1]

4 hours ago, foghorn said:

(NOTE: from an ex-TO)

1. Think about his accommodations. Several possibilities

 

 

Accommodations

 

I hadn’t fully modeled this yet, but your examples make it clear this should be flexible.

In the Netherlands, the situation is actually much more consistent: the Circuit Overseer has a fixed (home) address, and during a visit, he stays at a hosting family (lodging address).

 

Possible scenarios:

• Circuit apartment (single location)
• Multiple apartments (rare but possible)
• Temporary travel (rural circuits)
• Travel trailer (moving or semi-fixed)
• Staying with different families weekly

This suggests I shouldn’t treat “address” as a single static field, but rather something like:

• current stay / temporary address
• base address (if any)
• possibly even per-week location

Also interesting point about mail handling, hadn’t considered that yet.
 

[Jonathan1]

4 hours ago, foghorn said:

2. Since you seem to want to cover every base, think also about how you would handle a Substitute CO. This seems to be happening more frequently since the CO's are going to more schools, and being used for other functions. In many cases, the substitute is a different brother every time. So the local congregation may just want an easy way to track it during the week he serves. If you are planning a special version for the CO to use, perhaps HE could send the info on the Substitute CO electronically to the congregation involved.

 

Instead of modeling only a single Circuit Overseer, it probably makes more sense to support:

• a temporary replacement (Substitute CO)

• linked to a specific week or visit

Your suggestion is especially interesting: the CO could send substitute info electronically

That fits really well with what I’m building. This functionality will be implemented in a later version.

 

When maintaining a central list of Circuit Overseers, would you expect a Substitute CO to also be included in that same list?

Or would it make more sense to treat a substitute as:

• a temporary role/assignment linked to a specific visit, rather than

• a permanent entry like a regular Circuit Overseer?

 

[Jonathan1]

I’ve been thinking about similar scenarios while designing this.

Recently, we also had a visit where the Circuit Overseer was accompanied by another brother (for example during training or special circumstances).

In such cases, I’m wondering how this is handled in practice:

• Does the accompanying brother also require:

  • lodging arrangements?

  • meal assignments?

  • field service scheduling?

Or is he usually:

• staying with the Circuit Overseer?

• included implicitly in existing arrangements? 

From a design perspective, this raises the question:
Should I support multiple persons attached to a single visit, instead of assuming only:

• one CO

• or one substitute

Curious how this works in real life.

 

[foghorn]

• Does the accompanying brother also require:

  • lodging arrangements? YES, if he lives far away. NO, if he lives nearby

  • meal assignments? Evening: at accommodations. Noon: probably same as CO

  • field service scheduling? Hard to predict, depends on CO

Or is he usually:

• staying with the Circuit Overseer? Possible, but unlikely. He would need separate arrangements

A substitute CO for the week will be selected by the Branch from their list of approved substitutes. He could be selected in several ways. Might depend on availability, need for experience, etc. EXAMPLE: CO is assigned to attend CO school. Multiple subs will be needed, so probably involve numerous different subs. Could be...

• local substitute in same circuit
• substitute in nearby circuit
• substitute from further away circuit