|
| 1 | +<!DOCTYPE html> |
| 2 | +<html> |
| 3 | + <head> |
| 4 | + <title>SimpleHTML</title> |
| 5 | + <script src="/scripts/netc-lib.js"></script> |
| 6 | + <script src="https://cdnjs.cloudflare.com/ajax/libs/d3/4.13.0/d3.min.js"></script> |
| 7 | + <script src="/scripts/netc-app.js"></script> |
| 8 | + <link rel="stylesheet" href="/styles/netc-app.css" type="text/css"> |
| 9 | + |
| 10 | + </head> |
| 11 | + <style> |
| 12 | + body { |
| 13 | + padding: 10px; |
| 14 | + } |
| 15 | + </style> |
| 16 | + <body> |
| 17 | + <h2>Basic Network Analysis Vocabulary</h2> |
| 18 | + |
| 19 | +<dl> |
| 20 | + <dt>Network</dt> |
| 21 | + <dd>This is a collection of nodes and the edges between them. </dd> |
| 22 | + |
| 23 | + <dt>Graph</dt> |
| 24 | + <dd>a graphic representation of a network and its components. <em><strong>Similar terms include:</strong> sociogram, visualization</em></dd> |
| 25 | + |
| 26 | + <dt>Node</dt> |
| 27 | + <dd>The thing or <em>entity</em> (shown as circles) that is connected through relationships. This could be individual people, groups of people, institutions (like churches, organizations, schools). One way of thinking about this is that nodes are nouns and edges are verbs - nodes are things that are connected through edges. <em><strong>Similar terms include:</strong> actor, vertex</em></dd> |
| 28 | + <ul> |
| 29 | + <dl> |
| 30 | + <dt>Ego</dt> |
| 31 | + <dd>This refers to the node you are focused on at the moment and the connections that they have. </dd> |
| 32 | + </dl> |
| 33 | + </ul> |
| 34 | + |
| 35 | + <dt>Edge</dt> |
| 36 | + <dd>The relationships between nodes you are considering (shown as lines). Relationships can take on many forms: nodes could be connected through somewhat intangible relationships, such as friendship or not liking one another. Edges can be based on interactions, such as talking to one another or being in conflict. They could also be defined by sharing resources, such as money or information. <em><strong>Similar terms include:</strong> line, tie, arc</em></dd> |
| 37 | + |
| 38 | + <ul><dl> |
| 39 | + <dt>Edge weight</dt> |
| 40 | + <dd>Edges can have a value attached to them. So, for instance, an node could sent $10,000 to another actor. Or, they could share three interactions of the same type with one another. This value is referred to as a weight. <em><strong>Similar terms include:</strong> value</em></dd> |
| 41 | + |
| 42 | + <dt>Directed or undirected edges</dt> |
| 43 | + <dd>Edges can either be directed or undirected. If a relationship is directed, it is being sent from (originating from) one node to another node. Node A may say they are friends with Node B, but Node B does not say Node A does this. Or Node A gives Node B something, such as resources, information, or an illness. However, in some cases, edges are defined as undirected. Two people who share a meal together or are married are both engaged share an undirected edge. <em>Note: in some academic literatures, the term "edge" is reserved for an undirected relationship, while the term "arc" is used to refer to directed ties.</em></dd> |
| 44 | + </dl></ul> |
| 45 | + |
| 46 | + <dt>Attributes</dt> |
| 47 | + <dd>Characteristics of the nodes or edges. A node could be designated by gender, for instance or the amount of wealth they possess. They could also be characteristics you find from the network itself - such as how many ties an node has (degree centrality). </dd> |
| 48 | + |
| 49 | + <dt>Centrality</dt> |
| 50 | + <dd>This is a way of ranking the importance of individuals within a network. There are many different ways to measure importance, such as degree centrality, betweenness centrality, and eigenvector centrality. </dd> |
| 51 | + <ul> <dl> |
| 52 | + |
| 53 | + <dt>Degree Centrality</dt> |
| 54 | + <dd>Degree centrality is a measure of how many connections a node has. An node with many ties that are being sent to them has a high in-degree centrality. In a friendship network, this can be easily recognized as popularity. Nodes sending many outgoing ties (high out-degree centrality) may be thought of as expansive in their relationship.</dd> |
| 55 | + |
| 56 | + <dt>Betweenness Centrality</dt> |
| 57 | + <dd>Nodes with high betweenness centrality serve as connectors between other individuals who wouldn't otherwise be directly connected. They may not be connected to a large number of people (that would be high degree centrality), but they are unique in their connections. If an actor with high betweenness centrality was removed from a network, the network would be more fragmented and less connected. Often researchers are interested in finding actors with high betweenness centrality because they can control whatever flows in the networks. For instance, military analysts often look for nodes with high betweenness in a terrorist network.</dd> |
| 58 | + |
| 59 | + <dt>Eigenvector Centrality</dt> |
| 60 | + <dd>Eigenvector centrality ranks actors based on their connection to other highly central nodes. So, a nodes importance as measured by eigenvector centrality are dependent on the other nodes with whom they share connections. Google's PageRank algorithm was a famous application of a version of this type of centrality, and allowed them to return highly relevant results in search for users.</dd> |
| 61 | + </dl></ul> |
| 62 | + |
| 63 | + <dt>Communities</dt> |
| 64 | + <dd>A community in a network is a way of thinking about grouping, often by finding densely connected sets of nodes. A community within a network that is tightly connected to one another but not to an outside group might be seen as a faction, such as rival political groups. In this case, nodes with high betweenness centrality in a network with multiple factions might be some of the only points of contact between rival groups - a potentially powerful but also difficult position to be in.</dd> |
| 65 | + </dl> |
| 66 | + </body> |
| 67 | + <script> |
| 68 | + require("babel-polyfill"); // enables regenerators for async/await |
| 69 | + console.log('*** SCRIPT IN IFRAME ***'); |
| 70 | + // NOTE: because this simple file runs inside of an IFRAME, |
| 71 | + // the javascript environment is SEPARATE from the one that loaded |
| 72 | + // this page. Thus, most UNISYS NET services aren't available because |
| 73 | + // they rely on the global 'EJSprops' set in index.ejs |
| 74 | + const STORE = require('system/datastore'); |
| 75 | + const UNISYS = require('unisys/client'); |
| 76 | + const $ = require('jquery'); |
| 77 | + //$('body').append('<p>JQUERY ADDED THIS. Now D3 will turn me orange.</p>'); |
| 78 | + // d3 is loaded |
| 79 | + //d3.select("body").style("background-color", "orange"); |
| 80 | + </script> |
| 81 | +</html> |
0 commit comments