Article summary
Split St Helena, Ascension and Tristan da Cunha into three location and phone-evidence queues before interpreting WhatsApp Activity.
Putting St Helena, Ascension and Tristan da Cunha in one title does not mean their data belongs under one phone rule. The combined page must split location and phone-evidence queues before discussing WhatsApp Activity.
The minimum three-queue design
| Queue | Must retain | Prohibited shortcut |
|---|---|---|
| St Helena | Location and phone evidence | Apply another island’s rule |
| Ascension | Independent provenance label | Classify from page title |
| Tristan da Cunha | Specific service record | Merge small-sample identities |
A combined name cannot generate a calling code
Store phone_raw and location_evidence separately and process under the applicable current numbering rule. Rows that cannot be located to an island enter location_unknown.
Split the business market as well
Order or service location assigns the queue. A foreign phone can belong to a real customer, so do not retain only phones that look local.
Activity serves a specific event
Transport, accommodation, project or support actions may use time ordering inside permission. Regional research does not need person-level activity.
Do not profile tiny samples
Island cohorts may be very small. Do not cross avatar, role and time into identifiable cells; lead with absolute counts.
Generate TXT by queue
Each task has a separate batch_id and one phone per line. Returned Excel must not merge islands by row order.
Unknown cannot move between queues
Do not place one island’s unknown into another to complete a chart. Missing location stays unknown; format issues return to the applicable rule.
Expiry follows the service event
valid_until comes from the specific service end. An old Activity observation is not reused automatically for another project.
Why a combined page can still help
It can navigate and compare three queues only when differences remain explicit—not when three places become one reusable template.
