This preview shows page 1-2-3-4-5-6-7-8-9-10-11-12-13-95-96-97-98-99-100-101-102-103-104-105-106-107-108-190-191-192-193-194-195-196-197-198-199-200-201-202 out of 202 pages.
1 Basic Lessons in *ORAReports2 Belief Report2.1 BELIEFS REPORT2.2 Analysis for the belief network: Agent x belief2.2.1 Most Common Beliefs2.2.2 Most Contentious Beliefs2.2.4 Most Strongly Held Beliefs2.2.5 Most Likely to Change Beliefs2.2.6 Most Opinionated Individuals2.2.7 Most Neutral Individuals3 Capacity Report3.1 Overall Capability and Needs3.2 Highest Requirements3.3 Requirements5 Capacity Report5.1 Overall Capability and Needs5.2 Requirements6 Key Entity Report — Basic6.1 Main Dialog Box6.2 The Reports6.3 Output Options7 Key Entity Report — Other Options7.1 General Transformation7.2 Remove Entities Options7.3 Partition Options7.4 Summary8 Mental Model Reports8.1 Mental Model Reports Bibliography10 Tasks11 Contextual Menus12 Contextual Menus - Multi Files13 Creating a Network from an Excel Spreadsheet13.1.1 NOTE : When creating your spreadsheet, do not add any additional titles, notes, or other headings, which will interfere with the "square" properties of the Network.13.1.2 NOTE : If you don't end up with a diagonal line then your graph is not square.13.1.3 From the drop down menu: File => Save As14 Hovering15 Info Tab - Network16 Info Tab - NodeSet17 Running an Intelligence Report17.1 Who are the critical actors?17.2 INTELLIGENCE REPORT17.3 KEY ACTORS17.4 Emergent Leader (cognitive demand)17.5 In-the-Know (total degree centrality)17.6 Number of Cliques (clique count)17.7 Most Knowledge (row degree centrality)17.8 Most Resources (row degree centrality)17.9 Leader of Strong Clique (eigenvector centrality)17.10 Potentially Influential (betweenness centrality)17.11 Connects Groups (high betweenness and low degree)17.12 Unique Task Assignment (task exclusivity)17.13 Special Expertise (knowledge exclusivity)17.14 Special Capability (resource exclusivity)17.15 Workload (actual based on knowledge and resource)17.16 KEY KNOWLEDGE17.17 KEY RESOURCES17.18 KEY LOCATIONS17.19 III. What do we know about an actor of interest?17.20 1. Visualize information about a selected actor17.21 2. Visualize an actor's sphere of influence17.22 3. Run a Sphere of Influence Report17.23 SPHERE-OF-INFLUENCE REPORT17.24 Sphere of Influence Analysis for agent ahmed_ghailani17.25 Size Statistics17.26 Attributes17.27 Exclusive Connections17.28 Most Similar Node17.29 Top Measures17.30 Measure Value Range17.32 Resource Analysis Section17.33 IV. What are the connections between two actors of interest?17.34 V. What is the immediate impact of a particular agent on the network?17.35 VI. What happens to the network when certain entities are removed?18 Create a New Meta-Network18.1 Delete an existing node18.2 Merge two nodes19 Performing a View Network Over-Time Analysis19.1 Performing the Over-Time Analysis19.1.1.1 From the Menu Bar => Data Visualization => View Network Over-Time19.2 Example Slider Position 119.3 Example Slider Position 219.4 Example Slider Position 319.5 WTC Event Node: Detail 1 - 199619.6 WTC Event Node: Detail 2 - 199719.6.1.1 Notice who how the relationships of this node to the rest of the network has changed from 1996 to 1997.19.6.1.2 Notice that the connections (links) have changed from 1996 to 1997.19.7 Summary of Lesson20 Performing the View Measures Over-Time Analysis20.1 Performing the View Measures Over-Time Analysis20.1.1.1 From the main menu bar: Data Visualization => View Measures Over Time20.2 Interpreting The Results After Performing View Measures Over-Time Analysis20.2.1.1 Graph tab > Congruence, Organization Measure, Knowledge Waste.21 Renaming21.1 Renaming Meta-Networks, Meta-Nodes, and Networks22 Running An Over-Time Analysis22.1 Overview: Over-Time Viewer23 Lessons24 Lesson 1: ORA Overview24.1 Overview of ORA Interface24.2 Loading a meta-network into ORA24.3 The Visualizer 25 Lesson 2: Creating A New Meta-Network25.1 Lesson - 10125.2 lessons - 201-20725.3 lessons - 301+26 101 - Examine Your Data26.1 General Thoughts26.1.1.1 For the purpose of creating the Stargate MetaNetwork the two-episode story arc (Summit / Last Stand) was choosen as the basis for all the nodes, nodesets, and networks. But even though the information was clearly on the tv screen, many intuitive decisions had to be made.26.1.1.2 For the Julius Caesar MetaNetwork both the play and spark notes were used as reference. As with the Stargate MetaNetwork many decisions were made about how to create datasets and what connexions would be required.26.1.1.3 Initially the Stargate MetaNetwork was built with both the allies and the badGuys. This appeared to be the best way and it looked good displayed in the visualizer. But it was discovered that having the badGuys interfered with getting proper information from the reports. It wasn't until after the badGuys were removed that reports began to make more sense. What looks good in the beginning ISN'T necessarily your best option.26.2 What's in a Node Class26.2.1.1 With Stargate the agents were easy. The Stargate personnel, the Tok'ra, and some assorted others. The locations also were easy using scenes form the show. It was the events, knowledge, resources, and tasks which became slightly more difficult to discern. There were multiple false starts (missing some events, unnecessary locations, misplaced knowledge/resources) before I came to a proper conclusion. Initially I created extra Nodesets (like faction & groups). This did nothing but clutter up the MetaNetwork and make finding information much harder.26.2.1.1.1 The Julius Caesar Agent NodeSet was also easy using the cast of characters but it too had it's construction problems. Julius Caesar had limited resources so knowledge and resources were essentially combined into one NodeSet called knowledge.26.2.1.2 Stargate uses attributes to give extra information such as an agent's gender or time of death or the order in which events happened.26.2.1.2.1 Use the Julius Caesar attributes alligence and persuasion as a control mechanism to show the strength which various agents use these attributes.26.3 Agents (Who)26.3.1.1 The Stargate NodeSet contains a mere 16 agents. Originally I plotted both the allies and badGuys but found there was too much clutter and unnecessary nodes. Removing the badGuys helped streamline the NodeSet.26.3.1.1.1 The Julius Caesar NodeSet came in with more than twice as many. Unlike the Stargate NodeSet all of the characters were necessary. Everybody was plotting against everybody else.26.3.1.2 The Stargate (and Julius Caesar) MetaNetworks were fairly easy to construct agent NodeSets and agent by
View Full Document