Units
The entities whose network structures are modeled and compared, such as people, teams, or documents.
Mission and method
ENA.HK is designed as a clear public entry point to Epistemic Network Analysis, with accurate concepts, transparent scope, and direct paths to primary resources.
An ENA graph is not a self-explanatory picture. Its meaning depends on how the data, units, conversations, codes, and comparison are defined.
The entities whose network structures are modeled and compared, such as people, teams, or documents.
The bounded context in which coded elements may be considered connected.
Theory-informed or empirically developed indicators of meaningful ideas, actions, or practices.
Weighted summaries of code co-occurrence that can be visualized, interpreted, and compared.
Strong ENA work treats modeling choices as part of the argument and returns to the source evidence when explaining a pattern.
Let the research question and conceptual framework guide what relationships should count.
Interpret model outputs with close attention to the data and setting that produced them.
Make units, windows, codes, normalization, rotation, and comparison decisions reviewable.
Use networks as evidence within a design, not as automatic proof of causation or quality.
Researcher × developer co-creation
Public and private-review tracks use one structured proposal and the same scientific, privacy, security, and release gates.
A researcher contributes the problem, method insight, evidence, and limitations; software begins only after a reviewable specification exists.
Product availability, scientific evidence, and engineering assurance are reported independently for every exact plugin version.
A plugin that changes analysis semantics or sends analysis data to an external service requires review beyond its proposer and primary implementer.
Use the official webtool and resource library for software access, data preparation guidance, tutorials, and worked examples.