Retain Isolates and Audit Core-Periphery Claims
Keep eligible zero-tie actors in the denominator and distinguish observed isolation from missing participation before fitting a core-periphery pattern.
Method sources
By the end of this tutorial
- 1Define isolates and core-periphery structure from an explicit node, tie, boundary, direction, weight, and observation-window specification.
- 2Apply and audit this procedure: Reconcile the roster, display observed isolates, separate no-tie from unknown, fit a stated discrete or continuous core-periphery model, and repeat under plausible missing-edge scenarios.
- 3Interpret the result with a sensitivity check and the following evidence boundary: An isolate may reflect boundary, opportunity, nonresponse, or tie definition; core membership is a model-dependent pattern and not a label of competence or worth.
SNA
Network specification
Analysis scenario
A district advice survey appears to show a tightly connected leadership core and several isolated teachers, but six eligible teachers did not return the survey.
Nodes
Every teacher on the census-date roster, with response, eligibility, and school attributes retained.
Ties
A directed teaching-advice nomination during the previous eight weeks, with nonresponse stored as unknown rather than zero.
Network type
One-mode, directed, binary whole network containing observed isolates, partial respondents, and explicit unknown dyads.
Step-by-step tutorial
Freeze the relational question
Write the decision the analysis must inform, then lock the eligible node roster, tie-generating event, direction, weight, self-tie rule, observation window, and missing-data code. Preserve a read-only source copy and record why this specification represents the stated question.
Checkpoint
A second analyst can reconstruct the same node set and edge table from the written rules without guessing what an absent record means.
Compute the focal structure
Work on a versioned analysis copy and carry out the focal method exactly as specified: Reconcile the roster, display observed isolates, separate no-tie from unknown, fit a stated discrete or continuous core-periphery model, and repeat under plausible missing-edge scenarios. Save software and package versions, every threshold, normalization, seed, and intermediate count needed to reproduce the result.
Checkpoint
The output is tied to one named data version and includes the denominator, parameter settings, and a reproducible calculation record.
Run a structural sensitivity check
Repeat the analysis under at least one defensible alternative boundary, missingness rule, tie threshold, weight transformation, or model setting. Compare membership and substantive conclusions, not only a single coefficient, and investigate every change large enough to alter a decision.
Checkpoint
The audit states which patterns persist, which actors or groups change classification, and which conclusion depends on an analyst choice.
Report for responsible action
Pair the numerical result with a table or structure-preserving visual, document excluded and missing actors, and explain uncertainty in plain language. Convert the finding into a reversible support question, not an automatic ranking, while stating this boundary: An isolate may reflect boundary, opportunity, nonresponse, or tie definition; core membership is a model-dependent pattern and not a label of competence or worth.
Checkpoint
The final note contains the question, specification, result, sensitivity evidence, uncertainty, privacy controls, and a proportionate next step.
Interpret with care
isolates and core-periphery structure describes a property of the specified relation and network boundary. It does not transfer automatically to another relation, time period, class, platform, or population.
An isolate may reflect boundary, opportunity, nonresponse, or tie definition; core membership is a model-dependent pattern and not a label of competence or worth. Compare the result with raw counts, missingness, plausible alternative specifications, and contextual evidence before acting.